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

        1. MDEV-36024_vs_MDEV-14425.pdf
          18 kB
          Axel Schwenke
        2. MDEV-36024.pdf
          18 kB
          Axel Schwenke
        3. Overhead_Table.png
          20 kB
          Rahul Raj

        Issue Links

          Activity

            People

              marko Marko Mäkelä
              axel Axel Schwenke
              Marko Mäkelä Marko Mäkelä
              Vladislav Lesin Vladislav Lesin (Inactive)
              Matthias Leich Matthias Leich
              Votes:
              1 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 2.7d Original Estimate - 2.7d
                  2.7d
                  Remaining:
                  Remaining Estimate - 0d
                  0d
                  Logged:
                  Time Spent - 16.75d
                  16.75d

                  Git Integration

                    Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.