Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ja_JP] Introduction #897

Open
shimos opened this issue Sep 28, 2023 · 0 comments
Open

[ja_JP] Introduction #897

shimos opened this issue Sep 28, 2023 · 0 comments
Labels
jaJP-docs-ongoing Japanese Documentation ongoing

Comments

@shimos
Copy link
Contributor

shimos commented Sep 28, 2023

Original HTML: https://hyperledger-fabric.readthedocs.io/en/release-2.5/whatis.html
Original Source: https://github.com/hyperledger/fabric/blob/e1e8e2e52aa4fc543360d245fe6554a0eaf81183/docs/source/whatis.md

diff --git a/docs/source/whatis.md b/docs/source/whatis.md
index a38cce640..b37a1c3ae 100644
--- a/docs/source/whatis.md
+++ b/docs/source/whatis.md
@@ -297,12 +297,7 @@ requirements.
 ## Performance and Scalability
 
 Performance of a blockchain platform can be affected by many variables such as
-transaction size, block size, network size, as well as limits of the hardware,
-etc. The Hyperledger Fabric [Performance and Scale working group](https://wiki.hyperledger.org/display/PSWG/Performance+and+Scale+Working+Group)
-currently works on a benchmarking framework called [Hyperledger Caliper](https://wiki.hyperledger.org/projects/caliper).
-
-Several research papers have been published studying and testing the performance
-capabilities of Hyperledger Fabric. The latest [scaled Fabric to 20,000 transactions per second](https://arxiv.org/abs/1901.00910).
+transaction size, block size, network size, as well as available hardware resources such as CPU, Memory, Disk Space, Disk and network I/O.
 
 ## Conclusion
 
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
jaJP-docs-ongoing Japanese Documentation ongoing
Projects
Development

No branches or pull requests

1 participant