GET 24/7 LIVE HELP NOW

Announcement

Announcement Module
Collapse
No announcement yet.

How to read tpcc-mysql result

Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • How to read tpcc-mysql result

    I use tpcc-mysql tools to benchmark my mysql db server.

    what does the following mean?

    10, 278(0):0.8, 275(0):0.4, 27(0):0.4, 28(0):1.8, 28(0):1.4
    20, 295(0):0.6, 302(0):0.4, 29(0):0.4, 31(0):1.0, 30(0):1.6
    30, 263(0):0.8, 261(0):0.4, 27(0):0.4, 25(0):1.0, 27(0):1.6
    .....

    It seems like the results in 10 seconds, can i calculate the tpm in every 10 seconds?

    I scan the source code, but still no answer

  • #2
    Have you found an answer yet? I don't know myself, and would have to research it.

    Comment


    • #3
      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[0] + l[0] - prev_s[0] - prev_l[0] ), ( l[0] - prev_l[0] ), rt90[0], ( s[1] + l[1] - prev_s[1] - prev_l[1] ), ( l[1] - prev_l[1] ), rt90[1], ( s[2] + l[2] - prev_s[2] - prev_l[2] ), ( l[2] - prev_l[2] ), rt90[2], ( s[3] + l[3] - prev_s[3] - prev_l[3] ), ( l[3] - prev_l[3] ), rt90[3], ( s[4] + l[4] - prev_s[4] - prev_l[4] ), ( l[4] - prev_l[4] ), rt90[4] );

      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(C), 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.

      Comment


      • #4
        Still helpful after 3 years

        Comment


        • #5
          10, 278(0):0.8, 275(0):0.4, 27(0):0.4, 28(0):1.8, 28(0):1.4
          20, 295(0):0.6, 302(0):0.4, 29(0):0.4, 31(0):1.0, 30(0):1.6
          30, 263(0):0.8, 261(0):0.4, 27(0):0.4, 25(0):1.0, 27(0):1.6

          it means:

          0-10 sec -> 278 transactions per this time range
          10-20 sec -> 295 transactions per this time range
          20-30 sec -> 263 transactions per this time range

          Comment

          Working...
          X