Percona Server 5.1 内存过量消耗分析5
innodb_ibuf_max_size 参数意义
因为这个参数占用了那么多的内存
21474836480/10737418240
2.000000000
9663676416/4831838208
2.000000000发现都正好是 innodb_buffer_pool_size 的一半，于是开始查文档弄清楚 innodb_ibuf_max_size 参数的意义
Mysql的官方手册中没有找到关于这个参数的任何描述信息，其实根本就不存在这个参数
去百度里google一把，总会有收获，这次也不例外
发现，原来 innodb_ibuf_max_size 是 percona 自己加的参数，用来提升 insert 操作性能的
Variable innodb_ibuf_max_size
Item | Value |
|---|---|
Command Line | Yes |
Config File | Yes |
Scope | Global |
Dynamic | No |
Variable Type | Numeric |
Default Value | Half the size of the InnoDB buffer pool |
Range | 0 - Half the size of the InnoDB buffer pool |
Units | Bytes |
This variable specifies the maximum size of the insert buffer. By default the insert buffer is half the size of the buffer pool so if you have a very large buffer pool, the insert buffer will be very large too and you may want to restrict its size with this variable. Setting this variable to 0 is equivalent to disabling the insert buffer. But then all changes to secondary indexes will be performed synchronously which will probably cause performance degradation. Likewise a too small value can hurt performance. If you have very fast storage (ie storage with RAM-level speed, not just a RAID with fast disks), a value of a few MB may be the best choice for maximum performance.
本文系转载，前往查看
如有侵权，请联系?cloudcommunity@tencent.com 删除。
本文系转载，前往查看
如有侵权，请联系?cloudcommunity@tencent.com 删除。