Dave Kelsey

Some things to point out first 1. Caliper 0.3 is not supported anymore 2. Fabric 1.4 is not supported anymore 3. node 8.9, go 1.13.5 are not supported anymore You...

@pertualfeast fabric 2.2 still supports Kafka, you can also use caliper 0.5 to benchmark a fabric 1.4 system. The problem looks to be an issue with how you installed node.js....

Looks like you are using an old version of caliper benchmarks as the 1node network has since been removed. There is a general issue with ethereum at the moment but...

add and get have been added in #187 to the contract version of fixed-asset

Of course this will have an impact on the performance of the chaincode so we should perhaps create a separate fixed-asset version of this again not based on the contract...

It looks as though the ethereum setup in caliper-benchmarks is broken. The setup of the docker image is broken and the following changes need to be made File: networks/ethereum/1node-clique/caliper-ethereum-clique.Dockerfile change...

Load balancing in the fabric-gateway connector is covered here #1210 In a multi-org network could we have a workload that submits the same thing to all the orgs ? This...

Caliper like any other hyperledger fabric client that interacts with chaincode has no knowledge of what the chaincode does internally so the issue here is not about caliper not being...

Looks like you are running test network, and I assume that caliper and test-network are running on the same machine given the reference to localhost The message ``` Error: error...

see https://stackoverflow.com/questions/71648747/peer-cant-load-ledger-on-init-due-couchdb-document-too-large