We have been using tpcc-mysql benchmark for long time, and there many results published in our blog, but that’s just single workload. That’s why we are looking into different benchmarks, and one
of them is TPCE. Yasufumi made some efforts to make TPCE working with MySQL, and we are making it available for public consideration.
You can download it from our Lauchpad Percona-tools project, it’s
|
1 |
bzr branch lp:~percona-dev/perconatools/tpcemysql |
Important DISCLAIMER:
Using this package you should agree with TPC-E License Agreement,
which in human words is:
And we are not going to do anything from that, your primary goals is XtraDB/InnoDB performance research and/or compare with available Storage Engines for MySQL.
The workload in tpce is quite different from tpcc. Tpcc is write intensive, while tpce
is read oriented.
To give more details, there is stats for 10 seconds:
|
1 2 3 4 5 |
| Com_select | 46272 | | Com_update | 5214 | | Com_delete | 385 | | Com_insert | 3468 | | Com_commit | 5404 | |
The result is quite chatty,
|
1 2 3 4 5 6 7 8 |
| | [MEE] | [DM] | [CE] | sec. | TR, MF | DM | BV, CP, MW, SD, TL, TO, TS, TU | MEEThreads, ReqQueue (1st line: count, 2nd line: 90%ile response [msec.]) 260 | 402, 39, 0, 195, 532, 749, 588, 342, 415, 816, 88 | 30, 0 20, 60, 0, 30, 20, 20, 20, 50, 20, 310, 60 270 | 395, 40, 0, 201, 608, 842, 608, 358, 449, 833, 89 | 30, 0 30, 40, 0, 30, 20, 20, 20, 50, 20, 300, 50 |
but it allows you to see count of 11 different transactions per 10 secs and 90% response time.
and final result
|
1 2 3 4 5 6 7 |
[TradeResult(TR) transaction] Succeed: 150243 Lated: 0 Retried: 3 Failed: 0 41.7342 TpsE |
where you can see count of successful TR (TradeResult) transactions, and
the summary result in TpsE (transactions per seconds).
Expect our results soon!