Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-25342

autosize innodb_buffer_pool_chunk_size

Details

    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

      Attachments

        Issue Links

          Activity

            danblack Daniel Black added a comment -

            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

            danblack Daniel Black added a comment - 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

            People

              danblack Daniel Black
              danblack Daniel Black
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.