TPCC test for MySQL 5.7

TPCC test for MySQL 5.7

Mysq5.7.7-rc

System info:
System | Dell Inc.; PowerEdge R620; vNot Specified (Rack Mount Chassis)
Service Tag | JX47Z42
Platform | Linux
Release | CentOS release 6.6 (Final)
Kernel | 2.6.32-431.23.3.el6.x86 _ 64
Architecture | CPU = 64-bit, OS = 64-bit
Threading | NPTL 2.12
SELinux | Disabled
Virtualized | No virtualization detected
# Processor ###################################### ############
Processors | physical = 2, cores = 12, virtual = 24, hyperthreading = yes
Speeds | 24x2599.949
Models | 24 xIntel (R) Xeon (R) CPU E5-2630 v2 @ 2.60 GHz
Caches | 24x15360 KB
# Memory ###################################### ###############
Total | 126.0 GB
Free | 20.8 GB
Used | physical = 105.2G, swap allocated = 15.6G, swap used = 4.3 M, virtual = 105.2G
Buffers | 499.9 M
Caches | 55.2G
Dirty | 88 kB
UsedRSS | 46.4 GB
Swappiness | 0
DirtyPolicy | 20, 10
DirtyStatus | 0, 0

Innodb_buffer_pool_size = 10G
11892.600 TpmC
After the buffer pool is modified to 20 GB, Tpmc drops to + 2000 because the memory is not fully loaded. We can observe the second column of cat/proc/MYSQLPID/statm. The value is RSS, that is, the amount of memory pages actually allocated to the city (4 K on one page ).
As tpcc_start runs over and over again, the RSS value increases from 1758027 to 2941444, and continues to increase. Tpmc also increased to 8473.
Because the size of the tpcc database is around 11 GB, and the size of the database is 2941444*4 k = 11.22 GB, it is close to that of the database. Therefore, the size of the Tpmc database should be no less than the value tested earlier.

This article permanently updates the link address: