Tpcc-mysql Series II: Conduct TPCC test

1: Start testing

Tpcc_start-h server_host-p port-d database_name-u mysql_user-  p mysql_password-w warehouses-c connections-r War Mup_time-  l running_time-i report_interval-f report_file

　　

-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

　　

tpcc_start-hlocalhost-d tpcc1000-u tpcc_user-p "Tpcc_password"-  w 1000-c 32-r 120-l 3600-  F tpcc_mysql_2014 The 0921.log >> Tpcc_casex_20140921.log 2>&1 simulates 1000 warehouse sizes, tests with 16 threads, has a warm-up time of 60 seconds, and has a 1-hour pressure test time.

In real test scenarios, it is recommended that the preheating time is not less than 5 minutes and the duration of continuous pressure measurement is not less than 30 minutes, otherwise the test data may not be of reference significance.

　　

2:TPCC Test Results:

Launch test:./tpcc_start-h 1.2.3.4-p 3306-d tpcc10-u tpcc-p tpcc-w 10-c 64-r 30-l 120-f Tpcclog_201409211538_64_threa DS.log >> tpcc_noaid_2_20140921_64.log 2>&1 test result output is as follows:--some basic information of TPCC pressure measurement in this round ******************************* # # #easy # # Tpc-c Load Generator ******************************************option h with value ' 1.2.3.4 '--Main             Machine option P with value ' 3306 '--port option D with value ' TPCC10 '--database option U with value ' TPCC ' --account option p with value ' TPCC '--Password option W with value ' 10 '--Number of warehouses option C with value ' 64 '--Number of concurrent threads option R with value ' 30 '--long option L with value ' 120 '--voltage when data is preheated  Time-tested long option F with value ' tpcclog_20140921_64_threads.res '--Output report log file [Server]: 1.2.3.4 [port]: 3306 [DBname]: TPCC10 [user]: TPCC [pass]: TPCC [Warehouse]: [Connection]: [Rampup]: (sec.) [Measure]: 120 (sec.) Ramp-up time. (sec.) --Pre-Hot end, start of pressure measurement measuring start.--output voltage test every 10 seconds Data 10, 8376 (0): 2.744|3.211, 8374 (0): 0.523|1.626, 838 (0): 0.250|0.305, 837 (0) : 3.241|3.518, 839 (0): 9.086|10.676 20, 8294 (0): 2.175|2.327, 8292 (0): 0.420|0.495, 829 (0): 0.206|0.243, 827 (0): 2.489| 2.593, 827 (0): 7.214|7.646 110, 8800 (0): 2.149|2.458, 8792 (0): 0.424|0.710, 879 (0): 0.207|0.244, 878 (0): 2.461|2.556, 878 (0): 7.042|7.341 120, 8819 (0 ): 2.147|2.327, 8820 (0): 0.424|0.568, 882 (0): 0.208|0.237, 881 (0): 2.483|2.561, 883 (0): 7.025|7.405--comma-delimited, total 6 columns-first column, Nth 10 second-second column, number of times the new Order was successfully executed (the number of times the test was postponed): 90% Transaction Response Time | 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 effective transactions-the third column, the number of successful executions of payment operations The response time of the transaction | The maximum response time of this test-the fourth column, the order status business results, the next several meanings ibid--fifth column, the logistics delivery business results, the next several meanings ibid--sixth column, inventory warehousing business results, the next several meanings ibid--end of stopping THREADS ... ..... ... .... ... .... ... .... .... ..... .... ..... ..... ......., ..., ... and .... ............--First-time results statistics [0] sc:100589 lt:0 rt:0 fl:0-    -New-order, New Order business Success (success, abbreviated SC) Number of times, delay (late, abbreviated LT) Number of times, retry (retry, abbreviated RT) Number of times, failed (failure, abbreviated FL) Number of times [1] sc:100552 lt:0 rt:0 fl:0 --Payment, payment business statistics, other ibid. [2] sc:10059 lt:0 RT:0 fl:0-Order-status, order status business statistics, other ibid. [3] sc:10057 lt:0 rt:0 fl:0--Delivery, shipping business statistics, other ibid. [4] sc:10058 lt:0 R    t:0 fl:0--Stock-level, inventory business statistics, other than in the SEC.   -second statistic results, other ibid. [0] sc:100590 lt:0 rt:0 fl:0   [1] sc:100582 lt:0 rt:0 fl:0   [2] sc:10059 lt:0 rt:0 fl:0   [3] sc:10057 lt:0 rt:0 fl:0  [4] sc:10059 lt:0 rt:0 fl:0 (All must is [OK])--All business logic results below must be OK [transaction percentage] payment:43.47% (>=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.35% (>= 4%) [OK]-order status, other ibid delivery:4.35% (>= 4%) [OK]--delivery, other ibid. stock-level:4.35% (>= 4%)              [OK]--stock, other ibid. [Response time (at least 90% passed)]--response duration indicator must exceed 90% pass only new-order:100.00% [OK]    --The following response time-consuming indicators all 100% through payment:100.00% [OK] order-status:100.00% [OK] delivery:100.00% [OK]                stock-level:100.00% [OK] 50294.500 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: 100589/2 = 50294.500) 

　　

Because the test time is longer. This blog reference Ye Jinlong Teacher's.

Tpcc-mysql Series II: Conduct TPCC test