Calculate the whole proc about caliper HOT 6 CLOSED

sorry, i can't fully get your point.
The send rate indicates how many transactions are sent per second, and the throughput indicates how many transactions are actually committed on the ledger per second.

from caliper.

Does the 100 tps is calculated by (Succ+Fail )/time ？besides the cli processProposal successfully every request.

from caliper.

Caliper will record the submitting time and committing time (the time when the tx is committed on the ledger or when the failure occurred) for each tx.
So the send rate is calculated by (Succ+Fail) / (last submitting time - first submitting time).
The throughput is calculated by Succ/(last committing time - first submitting time), here only successful committed txs will be calculated.

from caliper.

1.nodejs has one thread in the lifecycle, the submitting process is in one thread, while goland has goroutine ,java have the multiple thread,
2.When to record committing time? Is the eventhub receives the blockevent from the block?
3.From my table, 100 tps 200 tps ... ,they are different , but how to control or adjust the send rate ?

from caliper.

1. Although nodejs process is in one thread actually, the submitting process is in asynchronous mode. Meanwhile, we are using multiple child processes to improve the capability.
2. That's the case for fabric.
3. You can find the 'ratecontrol' property in config file, which defines how to control the sending rate.

from caliper.

You are so kind, thank you very much !

from caliper.