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

Make innodb_purge_threads settable without server restart

    XMLWordPrintable

Details

    Description

      To enable better control of the InnoDB purge subsystem, it would be good if the maximum number of purge tasks were settable by the user while the server is running:

      SET GLOBAL innodb_purge_threads=1;
      		 
      # run a heavy workload
      		 
      # let the history be discarded faster while the server is less busy
      		 
      SET GLOBAL innodb_purge_threads=32;

      Independently of this, MDEV-16260 or MDEV-26356 may improve the way how the purge threads are scheduled. This task would only make the maximum number of concurrent purge tasks configurable.

      Attachments

        1. MDEV-26520.test
          1.0 kB
          Matthias Leich
        2. output.txt
          97 kB
          Matthias Leich

        Issue Links

          is duplicated by

          Task - A task that needs to be done. MDEV-11024 Make number of purge threads variable dynamic

          • Major - Major loss of function.
          • Closed
          relates to

          New Feature - A new feature of the product, which has yet to be developed. MDEV-16260 Scale the purge effort according to the workload

          • Major - Major loss of function.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. MDEV-26356 Performance regression after dict_sys.mutex removal

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

          Activity

            People

              wlad Vladislav Vaintroub
              marko Marko Mäkelä
              Votes:
              0 Vote for this issue
              Watchers:
              6 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.