Changing BatchTimeout, MaxMessageCount, AbsoluteMaxBytes, and PreferredMaxBytes doe not impact results

[nimaafraz]

Which Caliper version are you using?

2.4

Which Node.JS version are you using?

12

Which operating system are you using?

Ubuntu 20

Please provide some context for your error. For example, when did the error occur? What were you trying to achieve, and how?

Hi,

I am changing BatchTimeout, MaxMessageCount, AbsoluteMaxBytes, and PreferredMaxBytes values and generating the artifacts again but this make no difference to the latency and throughput results I get for Fabric.

What was the observed incorrect behavior?

I also tried to delete the volumes and containers after each change but still the same.

Please provide the error logs and their surroundings.

No errors

Please provide your benchmark configuration file content, if possible.

Please provide your network configuration file content, if possible.

Please provide your workload module content, if possible.

Please provide any additional information you deem relevant to the error.

No response

[davidkel]

Not sure what issue you are trying to say caliper has. I would suggest you try reading the fabric documentation on performance tuning and if you want assistance with fabric performance you need to talk to the fabric community. Be aware that doing proper benchmarking requires using more than just a workload generator such as caliper. Fabric provides ways to measure it's activity, you will also need to measure system usage for both systems running Fabric as well as the Systems running Caliper to make sure you aren't bottlenecking your systems running Fabric or the workload generator.

[nimaafraz]

Thanks @davidkel, would you suggest running the workload generator on a separate container?

[davidkel]

@nimaafraz For me I would run the workload generator on it's own dedicated set of machines, never on the machines running hyperledger fabric.