I know this thread is hella old, but I need to know this, too, so let’s put it somewhere Google will find it!
From the source:
printf("%4d, %d(%d):%.1f, %d(%d):%.1f, %d(%d):%.1f, %d(%d):%.1f, %d(%d):%.1f\n", time_count, ( s + l - prev_s - prev_l ), ( l - prev_l ), rt90, ( s + l - prev_s - prev_l ), ( l - prev_l ), rt90, ( s + l - prev_s - prev_l ), ( l - prev_l ), rt90, ( s + l - prev_s - prev_l ), ( l - prev_l ), rt90, ( s + l - prev_s - prev_l ), ( l - prev_l ), rt90 );
The Array indices are defined a couple lines earlier: New Orders, Payments, Order-Status, Delivery, and Stock-Level transactions. The line prints out every 10s and records these numbers for each of the above types: number of transactions processed successfully (plain printed), number of transactions that responded late (enclosed in parens ()), the 90th percentile response time for those transactions (after the colon : ).
So the output is something sort of like:
A, B©:D, E(F):G, H(I):J, K(L):M, N(O):PWhere:A = time elapsed in secondsB = New Orders processedC = New Orders processed too lateD = 90th percentile response time for New Orders (in seconds)…
repeat for Payments (E-G), then Order-Status (H-J), Delivery (K-M), and finally Stock-Level (N-P)
I read somewhere the TPCC benchmark’s metric is the number of new orders processed, so it isn’t exactly correct to draw conclusions based on the sum of the rows… but w/e I don’t really understand it either.