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

Server startup with large innodb_buffer_pool_size takes a long time

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Critical
    • Resolution: Unresolved
    • 10.1(EOL), 10.2(EOL), 10.3(EOL), 10.4(EOL), 10.5, 10.6, 10.7(EOL), 10.8(EOL), 10.9(EOL), 10.10(EOL), 10.11, 11.0(EOL), 11.1(EOL), 11.2
    • 10.6, 10.11, 11.2
    • Storage Engine - InnoDB

    Description

      The initialization of innodb buffer pool chunks/blocks on allocation has a number of consequences.

      • on very large memory systems this can take significant time
      • the initialization of data in the allocated memory forces this to paged into the process resulting in a real allocation out of the available OS space.

      The second becomes a problem when a large number of processes are on the system, potentially a large number of mariadb instances all competing for memory. A claim on use approach leaves more RAM available for other processes if mariadb doesn't end up using it.

      Sizing innodb buffer pool is a hard task so lets try to make it easier, or just less consequences if its wrong.

      The proposal is buf_pool_t::chunk_t::create removed the initialization (buf_block_init) and this becomes detected when blocks/chunks are used and then initialized there.

      Attachments

        Issue Links

          blocks

          Task - A task that needs to be done. MDEV-29445 reorganise innodb buffer pool (and remove buffer pool chunks)

          • Critical - Crashes, loss of data, severe memory leak.
          • Stalled
          relates to

          Task - A task that needs to be done. MDEV-25341 innodb buffer pool soft decommit of memory

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-33279 Disable transparent huge pages after page buffers has been allocated

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Task - A task that needs to be done. MDEV-24670 avoid OOM by linux kernel co-operative memory management

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Task - A task that needs to be done. MDEV-25342 autosize innodb_buffer_pool_chunk_size

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          DOCS-5414 Loading...

          Activity

            People

              danblack Daniel Black
              danblack Daniel Black
              Votes:
              0 Vote for this issue
              Watchers:
              8 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.