MySQL 5.7的TPCC测试


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 | 24xIntel(R) Xeon(R) CPU E5-2630 v2 @ 2.60GHz
      Caches | 24x15360 KB
# Memory #####################################################
      Total | 126.0G
        Free | 20.8G
        Used | physical = 105.2G, swap allocated = 15.6G, swap used = 4.3M, virtual = 105.2G
    Buffers | 499.9M
      Caches | 55.2G
      Dirty | 88 kB
    UsedRSS | 46.4G
  Swappiness | 0
 DirtyPolicy | 20, 10
 DirtyStatus | 0, 0

innodb_buffer_pool_size=10G
11892.600 TpmC
修改buffer pool到20G后,Tpmc降到+2000,是因为内存尚未加载满。我们可以观察 cat /proc/MYSQLPID/statm的第二列,这个值是RSS,就是进城实际分配的内存页数量(一页是4k大小)。
随着tpcc_start的一遍一遍地跑,RSS值从1758027增加到2941444,并且还在继续增加。Tpmc也增加到8473。
因为tpcc数据库大小在11GB左右,而2941444*4k=11.22GB,已经接近了,所以Tpmc应该能不小于前面测试的数值。

本文永久更新链接地址

相关内容