This repository contains sample benchmarks that may be used by Caliper, a blockchain performance benchmark framework. For more information on Caliper, please see the Caliper main repository
Associated performance reports, based on running these benchmarks, are published to the repository github pages.
This repository has three branches:
- main. Contains sample benchmarks
- reports. Contains md files that are built and published to the
gh-pages
branch - gh-pages. Contains the build output from the
reports
branch
The benchmarks contained within the master branch are split into three directories:
- benchmarks. Comprises the test configuration and callback files. The test configuration files describe the benchmark test parameters and also reference the callback files that are executed by Caliper clients during the benchmark. The Benchmark folder contains the following subfolders:
- api Tests directed towards the API of a single target blockchain.
- samples Tests directed towards the native samples provided by target blockchain platforms.
- scenario Generic scenarios that are valid for all (supported) target blockchain platforms
- networks. Comprises sample blockchain networks that may be used as target systems under test (SUT) for benchmarking purposes.
- src. Comprises the source smart contract files that are deployed to the SUT and interacted with via the test callbacks located within the benchmarks folder. Each smart contract is held within its own folder, under the blockchain technology that the smart contract corresponds to.
To run any of the benchmarks present in this repository, it is required to have installed Hyperledger Caliper, which is the intended consumer of all the contained files.
In general the steps are:
- Install the Caliper CLI - for details please see the Caliper main repository
- Clone this repository
- Run a Caliper CLI command that targets one of the contained benchmarks.
For detailed information about using this repo with hyperledger fabric see Hyperledger Fabric Networks
For detailed information about using this repo with hyperledger besu see Hyperledger Besu Networks
The documented reports are built automatically from the reports
branch of this repository and subsequently hosted on the gh-pages
branch; pull requests must be target the reports
branch in order for any modifications to be built.