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 created issue -
            danblack Daniel Black made changes -
            Field Original Value New Value
            Assignee Daniel Black [ danblack ]
            danblack Daniel Black made changes -
            danblack Daniel Black made changes -
            danblack Daniel Black made changes -
            danblack Daniel Black made changes -
            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 large page size if large_pages are enabled, or the OS page size otherwise.

            Sound acceptable [~marko]
            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]
            serg Sergei Golubchik made changes -
            Fix Version/s 10.7 [ 24805 ]
            Fix Version/s 10.6 [ 24028 ]
            ralf.gebhardt Ralf Gebhardt made changes -
            Fix Version/s 10.8 [ 26121 ]
            Fix Version/s 10.7 [ 24805 ]
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 120761 ] MariaDB v4 [ 131477 ]
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            Fix Version/s 10.8.1 [ 26815 ]
            Fix Version/s 10.8 [ 26121 ]
            Resolution Fixed [ 1 ]
            Status Open [ 1 ] Closed [ 6 ]
            marko Marko Mäkelä made changes -
            danblack Daniel Black made changes -
            Roel Roel Van de Paar made changes -
            rob.schwyzer@mariadb.com Rob Schwyzer (Inactive) made changes -
            rob.schwyzer@mariadb.com Rob Schwyzer (Inactive) made changes -

            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.