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

Set innodb_log_files_in_group=1 by default

    XMLWordPrintable

Details

    Description

      Historically, InnoDB split the redo log into at least 2 files. MDEV-12061 allowed the minimum to be innodb_log_files_in_group=1, but it kept the default at innodb_log_files_in_group=2.

      Because performance seems to be slightly better with only one log file, and because implementing an append-only variant of the log would require a single file, let us define the default to be 1, and have innodb_log_file_size=96M, to retain the same default total size of 2×48MiB.

      Note that this variable will be deleted by MDEV-14425!

      Attachments

        Issue Links

          blocks

          Task - A task that needs to be done. MDEV-14425 Change the InnoDB redo log format to reduce write amplification

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed
          is blocked by

          Task - A task that needs to be done. MDEV-12061 Allow innodb_log_files_in_group=1

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

          Task - A task that needs to be done. MDEV-21990 Issue a message on changing deprecated innodb_log_files_in_group

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-33503 innodb_log_files_in_group is quietly ignored

          • Major - Major loss of function.
          • Open

          Activity

            People

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