txn/s for no of client > 1 is wrong about py-tpcc HOT 4 OPEN

As far as i understand the specification http://www.tpc.org/tpc_documents_current_versions/pdf/tpc-c_v5.11.0.pdf, it's much simpler:
The specification says in 5.4 'The reported MQTh is the total number of completed New -Order transactions (see Clause 5.1.2), ...
divided by the elapsed time of the interval. ....
In your test this simply means 'txn_cnt / duration'
Or am i getting something wrong?

from py-tpcc.

@scjoe I haven't worked on this code in almost a decade. Can you provide the line numbers for what you want me to look at?

Also, you are correct that the TPC-C spec says to report NewOrders per minute. Academic papers typically report the total throughput for all five txn types.

The TPC-C spec also says that there is supposed to be a wait time and terminal output, but nobody implements those parts either.

from py-tpcc.

In results.py line 120 the rate per second is calculated. The txn_time is the total of all measurements for a transaction type, e.g. 'new orders'. But because these transactions runs in parallel (at least with more than one client), the calculated rate is not the number of processed transactions per second.

from py-tpcc.

Actually, technically it's correct, even if it's not useful. It's txn per second per thread so of course it'll be lower for multiple threads than for one thread.

from py-tpcc.