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

New InnoDB Buffer Pool autosize feature not so optimal implemented

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.11.12, 11.4.6, 11.8.2
    • None
    • Storage Engine - InnoDB
    • None
    • Linux, n.a.

    Description

      In LTS Release series you have introduced an absolutely new feature/behaviour of the database. Which is a bad thing by itself and an absolute no-go and breaks all the rules...

      And the implementation is not so optimal IMHO.

      innodb_buffer_pool_size_max defaults to innodb_buffer_pool_size defaults to 128M

      In case I forgot to size this parameter properly or in case I did some how a miss-configuration. I cannot increase this value any more! So the whole feature of dynamically up-sizing BP is gone.

      So either follow the worklog MDEV-36197 were it was stated by Marko: "default: 0 to disable the logic" which is OK for me. Or set innodb_buffer_pool_size_max to for example 75% of RAM like innodb_dedicated_server does...

      Attachments

        Activity

          People

            Unassigned Unassigned
            oli Oli Sennhauser
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:

              Git Integration

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