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

Set innodb_log_files_in_group=1 by default

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

          Activity

            In MariaDB Server 10.5.1, the option was deprecated and ignored. That is, MariaDB 10.5 will only support innodb_log_files_in_group=1 and a single redo log file, ib_logfile0.

            marko Marko Mäkelä added a comment - In MariaDB Server 10.5.1, the option was deprecated and ignored. That is, MariaDB 10.5 will only support innodb_log_files_in_group=1 and a single redo log file, ib_logfile0 .

            As part of MDEV-14425 preparations, MariaDB 10.5.1 deprecated the parameter innodb_log_files_in_group and hard-coded the value to 1. The deprecation logic was improved in MDEV-21990.

            marko Marko Mäkelä added a comment - As part of MDEV-14425 preparations, MariaDB 10.5.1 deprecated the parameter innodb_log_files_in_group and hard-coded the value to 1. The deprecation logic was improved in MDEV-21990 .

            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.