TPCC on MySQL performance pressure measurement

Software Download:

wget http://imysql.com/wp-content/uploads/2014/09/tpcc-mysql-src.tgz
Installation dependencies:
Yum Install-y mysql-devel
Unzip the installation:

Tar XF Tpcc-mysql-src.tar
Make

Prepare before testing:

[Root Tpcc-mysql] $mysql-uroot-p123456-s/data/mysql-5.5/mysql.sock-e "CREATE Database Tpcctest" [Root tpcc-mysql]$ Mys  Ql-uroot-p123456-s/data/mysql-5.5/mysql.sock tpcctest <./create_table.sql [root tpcc-mysql]$ mysql-uroot-p123456 -s/data/mysql-5.5/mysql.sock-e "Show tables from  tpcctest"
Load data:

Once the initialization is complete, you can start loading the test data.

Tpcc_load usage is as follows:

[Root tpcc-mysql]$./tpcc_load 127.0.0.1:3308 tpcctest Root 123456 10

Perform database pressure test:
./tpcc_start

-W Specify number of warehouses-C specify number of concurrent connections-R specifies the time to warmup before starting the test, and after preheating, the test effect is better-l specifies the test duration-  ---Specifies the report file name generated when the report interval is generated

The results show:

# # #easy # # tpc-c Load Generator **************************************** **option h with value ' 127.0.0.1 ' option P with value ' 3308 ' option D with value ' tpcctest ' option U with value ' root ' option P with value ' 123456 ' option W with value ' option C with value ' option R with value ' + ' option L with value ' &lt ' ; parameters> [Server]: 127.0.0.1--host [port]: 3308--Port [DBname]: tpcctest--measured data library [user]: root--account [pass]: 123456--Password [warehouse]: 10--Number of warehouses [connection]: 10--Number of concurrent threads [Rampup]: (sec.)--Data warm-up time [measure]: (SEC)--ramp-up time for pressure measurement.       (sec.)              --Preheat end measuring START. --Start pressure test 10, 27 (0): 3.829|7.321, 26 (0): 1.854|4.399, 3 (0): 1.503|1.670, 3 (0): 4.467|5.559, 3 (0): 14.525|20.229-- Output voltage measurement every 10 seconds data 20, 31 (0): 3.153|3.247, 29 (0): 0.861|1.202, 3 (0): 0.400|0.475, 3 (0): 4.471|4.980, 0 (0): 0.000|0.000 30, 28 (0) : 3.559|3.943, 27 (0): 0.807|0.838, 2 (0): 0.285|0.379, 2 (0): 3.273|3.628, 3 (0): 13.534|13.577 40, 26 (0): 3.643|4.040, 32 (0): 0. 676|0.686, 4 (0): 0.337|0.393, 4 (0): 4.397|5.081, 6 (0): 13.890|16.757 50, 32 (1): 4.377|5.695, 30 (0): 0.749|0.813, 2 (0): 0. 254|0.309, 3 (0): 3.418|4.066, 2 (0): 11.356|12.581 60, 32 (0): 3.561|3.602, 33 (0): 1.024|1.645, 4 (0): 0.318|0.413, 3 (0) : 3.446|3.542, 5 (0): 11.772|12.417 70, 41 (0): 3.228|3.415, 39 (0): 0.956|1.296, 4 (0): 0.394|0.396, 5 (0): 3.671|3.925, 1 (0): 0 .000|13.920 80, 35 (1): 4.096|6.454, 35 (0): 0.727|0.877, 3 (0): 0.344|0.410, 3 (0): 3.100|3.961, 4 (0): 11.251|11.489 90, 27 (0) : 2.787|3.505, 25 (0): 0.945|1.093, 2 (0): 0.394|0.423, 2 (0): 2.804|5.293, 3 (0): 11.637|12.463 100, 31 (2): 5.050|5.467, 31 (0) : 0.835|0.884, 4 (0): 0.334|0.363, 4 (0): 3.094|3.738, 2 (0): 11.853|11.885 110, 32 (0): 3.101|3.968, 33 (0): 0.606|1.503, 3 (0) : 0.255|0.347, 3 (0): 3.007|3.427, 5 (0): 11.685|12.653 120, 34 (0): 3.359|3.713, 33 (0): 0.730|0.844, 3 (0): 0.319|0.504, 3 (0) : 3.092|3.502, 2 (0): 8.187|10.347--comma-delimited, total 6 columns-first column, nth time 10 second-second column, New OrderNumber of times the work is executed (the number of times the test is delayed): 90% response time for the transaction | The maximum response time for this round of testing, the number of new order transactions is also considered to be the indicator of the total number of active transactions-the third column, the number of successful executions of the payment business (number of deferred executions): 90% Transaction response Time The fourth column, the order status business results, the next several meanings ibid--fifth column, the Logistics shipping business results, the next several meanings ibid--sixth column, inventory warehousing business results, the subsequent meaning ibid stopping THREADS ...--end the pressure test &lt ; Raw results>--First statistical results [0] sc:372 lt:4 rt:0 fl:0-New-order, New Order business Success (success, abbreviated SC), delay Number of times (late, abbreviated LT), retries (retry, abbreviated RT), failed (failure, abbreviated FL) Number of times [1] sc:373 lt:0 rt:0 fl:0--Payment, payment business statistics, other ibid. [2] sc:37 L  t:0 rt:0 fl:0--order-status, order status business statistics, other ibid. [3] sc:38 lt:0 rt:0 fl:0--Delivery, shipping business statistics, other ibid. [4] Sc:36 lt:0 rt:0 fl:0-Stock-level, Inventory business statistics, other ibid. in Sec.<raw Results2 (Sum ver.)   >-Second statistical result, other ibid. [0] sc:372 lt:4 rt:0 fl:0   [1] sc:373 lt:0 rt:0 fl:0   [2] sc:37 lt:0 rt:0 fl:0   [3] sc:38 lt:0 rt:0 fl:0 [4] sc:36 lt:0 rt:0 fl:0 <constraint check> (all must is [OK])--All business logic results below must be OK [transaction Percentag E] payment:43.37% (>=43.0%) [OK]--the number of payment successes (SC + LT) must be greater than 43%, otherwise the result is Ng, not OK order-status:4.30% (>= 4%) [OK]-order status, other ibid delivery:4.42% (>= 4%) [OK]--delivery, other ibid. stock-level:4.19% (>= 4%)             [OK]--stock, other ibid. [Response time (at least 90% passed)]--response duration indicator must exceed 90% pass only new-order:98.94% [OK] --The following response time-consuming indicators all 100% through payment:100.00% [OK] order-status:100.00% [OK] delivery:100.00% [OK] Stoc k-level:100.00% [ok]<tpmc> 188.000 tpmc--tpmc result value (number of transactions per minute, which is the number of new order transactions in the first statistic divided by the total elapsed minutes, for example in this case: 372/2 =186)

　　

TPCC on MySQL performance pressure measurement