fabric-test
fabric-test copied to clipboard
Automate configuration of a performance testbed for a Fabric Developer
Automate configuration of a provisioned environment to enable a developer provided fabric to be driven by a caliper workload
- [ ] investigate the suitability for the environment to be all provisioned VMs such that the results are consistent and comparable within the lifetime of those provisioned VMs
- [ ] provide an environment to be able to stand up a fabric network with local dev changes
- [ ] provide capability to be able to extend that environment to include prometheus and grafana servers with a starter set of queries and graphs
- [ ] reference caliper and caliper-benchmarks wrt defining and running a caliper based benchmark to perform comparisons
At this time there is no facilities available to be able to provision systems for this activity. It will therefore be the responsibility of contributors to source their own appropriate systems in order to be able to run benchmarks to test their code changes.
Further, this will initially be a BYOF (Bring Your Own Fabric) environment where the fabric processes are either run natively or using a lightweight container environment such as docker and as such the processes are still cleanly exposed as though they were native and network access is trivial via a single SUT ipaddress. It will be upto the developer to start/stop the fabric processes as well as be able to deploy their own chaincode.
Prototype being developed here https://github.com/davidkel/provision-performance
Checking that provisioned VMs give consistent results. Will bring up test environments and run benchmark 5 times and check that:
- avg cpu remains the same
- max TPS remains the same
- disk i/o rate is consistent
- fabric metrics remain consistent
Done