Configuration

This report was generated using the following Hyperledger Fabric component levels:

  • Fabric images: 1.4.0
  • Fabric chaincode:1.4.0
  • Fabric SDK Node: 1.4.0

Machine Configuration

Hyperledger Caliper at commit level 4156c4da7105fd1c2b848573a9943bfc9900becb was used.

The report was generated on an IBM Cloud Softlayer machine with the following configuration:

  • OS: Ubuntu 16.04-64
  • RAM: 2x16GB Micron 16GB DDR4 2Rx8
  • Processor: 3.8GHz Intel Xeon-KabyLake (E3-1270-V6-Quadcore)
  • Motherboard: Lenovo Systemx3250-M6
  • Firmaware: M3E124G 2.10 10-12-2017
  • Network Card: Silicom PE310G4i40-T
  • HDD: 960GB SanDisk CloudSpeed 1000 SSD
  • Architecture: x86_64
  • CPU op-mode(s): 32-bit, 64-bit
  • Byte Order: Little Endian
  • CPU(s): 8
  • On-line CPU(s) list: 0-7
  • Thread(s) per core: 2
  • Core(s) per socket: 4
  • Socket(s): 1

Notes

The performance information is obtained by measuring the transaction throughput for different types of smart contract transactions. The term “transaction” is used in a generic sense, and refers to any interaction with a smart contract, regardless of the complexity of the subsequent interaction(s) with the blockchain platform.

Measuring transaction throughput demonstrates potential transaction rates, and the impact of the relative cost of different Hyperledger Fabric Stub API calls.

The data contained in the reports was measured in a controlled environment, results obtained in other environments might vary. For more details on the environments used, see the resources at the end of this report.

The performance data cannot be compared across versions of Hyperledger Fabric, as testing hardware and environments may have changed significantly. The testing contents and processing methodologies may have also changed between performance reports, and so cannot be compared.