[MDEV-25342] autosize innodb_buffer_pool_chunk_size Created: 2021-04-06  Updated: 2022-06-13  Resolved: 2022-01-18

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Fix Version/s: 10.8.1

Type: Task Priority: Minor
Reporter: Daniel Black Assignee: Daniel Black
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Problem/Incident
causes MDEV-27891 Delayed SIGSEGV in buf_pool_t::resize... Closed
Relates
relates to MDEV-24670 avoid OOM by linux kernel co-operativ... Closed
relates to MDEV-25340 Server startup with large innodb_buff... Open
relates to MDEV-25341 innodb buffer pool soft decommit of m... Closed
relates to MDEV-27461 Server hangs when the bufferpool is s... Closed
relates to MDEV-28803 ERROR 1206 (HY000): The total number ... Open
relates to MDEV-28805 SET GLOBAL innodb_buffer_pool_size=12... Confirmed

 Description   

With MDEV-25340, MDEV-25341 and MDEV-24670 it would be good to ensure that the changes aren't frequently triggered and have a moderately substantial impact.

The current default innodb_buffer_pool_chunk_size of 128M results in 1024 segments for 128G RAM.

As the chunk size is designed around buffer pool resizing maybe 128 equating to just under 1% would be more appropriate.

So I'm thinking MAX(128M, buffer_pool_size / 128), then round down to a multiple of the next smallest large page size if large_pages are enabled, or a multiple of the OS page size otherwise.

Sound acceptable marko

 Comments   
Comment by Daniel Black [ 2021-04-08 ]

autosize of innodb variables in storage/innobase/handler/ha_innodb.cc:innodb_init_params
large pages sizes iteration - mysys/my_largepage.c:my_next_large_page_size

Generated at Thu Feb 08 09:36:58 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.