You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently benchmarking our HF 2.5 network with Caliper 0.5.
We have 4 peer organizations, each has 1 peer, each peer is an anchor peer and they use LevelDB as state database.
Further we have 3 orderer organizations, each with 1 orderer.
They are joined to one channel, where the orderers use Raft.
The endorsement policy is set to a majority:
They are deployed on 7 Debian VMs with 2 vCPUs, 4 peer VMs and 3 orderer VMs.
Our chaincodes are written in Go.
Now during the benchmark, where we target peers through the gateway functionality, we often encounter high latency, resulting in the following errors:
I tried to reduce the maximum message amount from 500 to 10,
reduce the batch timeout from 2.5s to 1.0s and to add more peers s.t. higher block count peers would take over as endorsing peers.
But we still encounter such issues.
It's independent of the chaincode method, every method sometimes works with about 200 TPS and on other occasions results in the unfinished transactions seen in the second image and in most cases end up in deadline exceeded errors seen in the first image.
The first and second image are from the same workload.
Did someone encounter such problems and knows how to resolve this?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm currently benchmarking our HF 2.5 network with Caliper 0.5.
We have 4 peer organizations, each has 1 peer, each peer is an anchor peer and they use LevelDB as state database.
Further we have 3 orderer organizations, each with 1 orderer.
They are joined to one channel, where the orderers use Raft.
The endorsement policy is set to a majority:
Channel/Orderer settings
They are deployed on 7 Debian VMs with 2 vCPUs, 4 peer VMs and 3 orderer VMs.
Our chaincodes are written in Go.
Now during the benchmark, where we target peers through the gateway functionality, we often encounter high latency, resulting in the following errors:
I tried to reduce the maximum message amount from 500 to 10,
reduce the batch timeout from 2.5s to 1.0s and to add more peers s.t. higher block count peers would take over as endorsing peers.
But we still encounter such issues.
It's independent of the chaincode method, every method sometimes works with about 200 TPS and on other occasions results in the unfinished transactions seen in the second image and in most cases end up in deadline exceeded errors seen in the first image.
The first and second image are from the same workload.
Did someone encounter such problems and knows how to resolve this?
Beta Was this translation helpful? Give feedback.
All reactions