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

Document how an SUT should be deployed in order to get reliable benchmarking #45

Open
davidkel opened this issue Aug 10, 2022 · 0 comments
Labels
documentation Improvements or additions to documentation

Comments

@davidkel
Copy link
Owner

davidkel commented Aug 10, 2022

If you aren't benchmarking a duplicate setup of your production network to determine it's max TPS for example, then you might be benchmarking an environment to determine things like

  1. chaincode performance changes
  2. fabric configuration changes
  3. fabric code changes

In order to get a fair comparison, the environment that is running hyperledger fabric must be consistent in the resources it has at it's disposal. That means the same amount of CPU power as well as having as much opportunity for disk i/o and network i/o as possible. To ensure this the systems running the hyperledger fabric components must ensure that no other processes are using CPU, interacting with the disk or network, or it needs to be as minimal as possible and for each run the same processes should be running
Linux also does are fair amount of in memory file caching and as that can vary it could influence benchmark results.

Cloud VMs are generally not suitable but would a dedicated environment be suitable so long as the hypervisor config doesn't change ?
Could local VM technology be used to guarantee consistent resources ?

@davidkel davidkel added the documentation Improvements or additions to documentation label Aug 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant