MySQL5.6.7-RC tpcc-mysql Benchmark Test Results

MySQL5.6.7RC was released a few days ago, so I decided to use tpcc-mysql to test its performance, including performance and stability. I don't know if it's the RC version.

MySQL 5.6.7 RC was released a few days ago, so I decided to use tpcc-mysql to test its performance, including performance and stability. I don't know if it's the RC version.

MySQL 5.6.7 RC was released a few days ago, so I decided to use tpcc-mysql to test its performance, including performance and stability.

I can't say that my testing process is flawless because I found two bugs:

MySQL 5.6.7 is locked during CREATE INDEX

MySQL 5.6.7-rc crashes when using tpcc-mysql workload Test

I don't know if it is because of the RC version. I submitted some feedback to Oracle later. The following is a detailed test environment:

Test Date: Oct-2012

Objective: To test MySQL 5.6.7 Performance

Hardware change

Software

Operating System: CentOS 6.3

MySQL version: 5.6.7-RC

Test Specification

Different test parameters: use different groups of innodb_buffer_pool_size: 13, 25, 50, 75,100,125 GB, innodb_buffer_pool_instances: 1 and 8, and innodb_log_file_size: 2x4 GB and 2x8 GB.

Test results:

The first result uses 2x4 GB InnoDB log file:

We can see that when innodb_buffer_pool_instances = 8 is very different in the small buffer_pool size, and when large buffer_pool is used, innodb_buffer_pool_instances = 1 is the best performance.

The test results are very stable in large buffer_pool because InnoDB adopts the asynchronous flush mode and the previous problems have been fixed under the new InnoDB flush mechanism. However, Dimitry tells me that a larger InnoDB log file is needed to obtain more stable results.

The following is a comparison of the log file sizes of 2x4 GB vs 2x8 GB innodb:

Obviously, the test results are more stable with larger log files!