中文

According to blockchain-performance-metrics, Probe is a web GUI application for Hyperledger Fabric mantianer, user, research. Recently, aims at providing a way to control both SUT and LGC to find the best block config logic for specific chaincode for specific fabric network. Meanwhile has a better understanding of how block config impacts performance.

• Probe provides loop test control for given block parameter arrays.
• Probe provides TPS result review via GUI.
• Probe provides sample chaincode for some test cases.

Long term goal for Probe is a coordinator between Test Harness or LGC, SUT.

• Probe will allow you design shell scripts to schedule SUT and Test Harness.
• Probe will allow you investigate performance matrix with GUI in customer way.

• HowToConfigFabricParameters

As discussed with TWGC performance work group, we found out that different block parameters, networks, chaincode language and chaincode logic having influence final TPS. To answer, the best parameter for specific fabric network and fabric chaincode, this project been created.

• Real time time monitor, for real time tps monitor, pls use Prometheus. (But Probe has demo for it with test network here)
• Auto test framework for Fabric performance, as in probe, we will invoke as byfn or minifab for your network up/down/cleanup.
• Performance test tool for Fabric, for this we using tape.
• GUI for tape, tape focus on once off time performance testing.

1. Install this project npm install

2. Install fabric-sample environment

   curl -vsS https://raw.githubusercontent.com/hyperledger/fabric/master/scripts/bootstrap.sh | bash

   Note

   If the above curl command fails, it may be that the old version of curl cannot handle redirection or cannot be redirected due to network reasons in some countries and regions. At this time, users can download the bootstrap.sh script then run it.

3. Get tape docker pull guoger/tape

4. Apply the bridge file to adjust block parameters for test network cp sample/prepareConfig.sh fabric-samples/test-network

5. npm start

6. Access localhost:3000, click

7. Click

8. Access localhost:3000/result/BatchTimeout to see TPS relationship with BatchTimeout

9. Access localhost:3000/result/MaxMessageCount to see TPS relationship with MaxMessageCount

If your want to contribute Probe with new feature, bug fixing please create a new issue, of course with PR is best.

Also welcome for documentatoin, learning course, etc.

For development, please complete Quick start above.

For Frontend, please use npm run build.

For backend, please develop --DryRun as mock for unit test and adding real cases in CI