content_image/742053.jpg content_image/742054.jpg
innodb_buffer_pool_size  to ensure that the resulting buffer pool size is acceptable. 

To avoid potential performance issues, the number of chunks ( innodb_buffer_pool_size  / innodb_buffer_pool_chunk_size ) should not exceed 1000. 

The innodb_buffer_pool_size  variable is dynamic, which permits resizing the buffer pool while the server is online. However, the buffer pool size must be equal to or a multiple of innodb_buffer_pool_chunk_size  * innodb_buffer_pool_instances , and changing either of those variable settings requires restarting the server. 

See Section 15.8.3.1, “Configuring InnoDB Buffer Pool Size”  for more information. 

• innodb_buffer_pool_debug 

<img src='content_image/742053.jpg'>

Enabling this option permits multiple buffer pool instances when the buffer pool is less than 1GB in size, ignoring the 1GB minimum buffer pool size constraint imposed on innodb_buffer_pool_instances . The innodb_buffer_pool_debug  option is only available if debugging support is compiled in using the WITH_DEBUG CMake  option. 

• innodb_buffer_pool_dump_at_shutdown 

<img src='content_image/742054.jpg'>

Specifies whether to record the pages cached in the InnoDB  buffer pool when the MySQL server is shut down, to shorten the warmup process at the next restart. Typically used in combination with innodb_buffer_pool_load_at_startup . The innodb_buffer_pool_dump_pct  option defines the percentage of most recently used buffer pool pages to dump. 

Both innodb_buffer_pool_dump_at_shutdown  and innodb_buffer_pool_load_at_startup are enabled by default. 

For more information, see Section 15.8.3.6, “Saving and Restoring the Buffer Pool State” . 

