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

performance regression with encrypted InnoDB log

    XMLWordPrintable

Details

    • Related to performance
    • The option innodb_encrypt_log=ON was reimplemented to be more performant. A downgrade to an earlier point release is only possible if the newer server was running innodb_encrypt_log=OFF at the time it was shut down.
    • Q4/2025 Server Maintenance

    Description

      MDEV-14425 introduced piecewise encryption of the InnoDB redo log. This causes a performance regression for workloads which create a lot of redo log, i.e. INSERT. The cause of the regression are repeated calls to MyCTX::init(). We need a different implementation that creates the AES context only once.

      Attachments

        Issue Links

          is caused by

          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
          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-34388 mariadb-backup segfault on 10.4.8 and 11.4.2, under Alpine 3.20, 3.21 and 3.22

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-37553 Assertion failure lsn - get_flushed_lsn(std::memory_order_relaxed) < capacity()

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

          Activity

            People

              marko Marko Mäkelä
              axel Axel Schwenke
              Marko Mäkelä Marko Mäkelä
              Vladislav Lesin Vladislav Lesin
              Matthias Leich Matthias Leich
              Votes:
              1 Vote for this issue
              Watchers:
              11 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.