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

Major performance regression with 10.6.11

Details

    Description

      After upgrading part of our systems to 10.6.11 the MariaDB server uses much more CPU compared to 10.6.10.

      We were upgrading to 10.6.11 for the fix to MDEV-29843, but started to roll back due to load issues with that version.

      Server config is the same as on MDEV-29843;
      ~8 MariaDB instances per server, issue is worse on systems with a higher number of queries, where it's using 100% cpu, with notocable repsonsiveness of the system

      Attachments

        Issue Links

          is blocked by

          Task - A task that needs to be done. MCOL-5361 prepare/execute : accomodate latest changes in server 10.6.11

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-16128 Server crash in Item_func::print_op on 2nd execution of PS

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-30096 Memory leak 10.3.37 and 10.6.11

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-30114 prepared statements spend a lot of time in cleanup

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-30116 Executing prepared statements may get slower over time

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-30274 Massive trigger performance drop after update

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-30848 Memory leak in MariaDB 10.6

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-30889 Memory leak issues with MariaDB 10.6.12 and OOM Crashes

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-30355 set names effects performance significantly when compiling function

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            View 7 older comments
            FK F K added a comment -

            Would this bug cause the innodb_buffer to fill faster and be larger than needed?

            FK F K added a comment - Would this bug cause the innodb_buffer to fill faster and be larger than needed?
            serg Sergei Golubchik added a comment -

            No, this bug cannot cause that

            serg Sergei Golubchik added a comment - No, this bug cannot cause that
            chungonn Cheong Chung Onn added a comment -

            We upgraded our customer production database this week, and we experienced major performance regression since we upgraded from 10.3 to 10.6.11. We have to tuned our a quite a few of our queries to achieve satisfactory performance.

            chungonn Cheong Chung Onn added a comment - We upgraded our customer production database this week, and we experienced major performance regression since we upgraded from 10.3 to 10.6.11. We have to tuned our a quite a few of our queries to achieve satisfactory performance.
            Lachman Miroslav Lachman added a comment -

            Just "we too" comment.
            We see very bad behaviors of 10.6 after upgrade from 10.3, namely tested versions 10.6.10 and 10.6.11. Both leaking memory like crazy. MariaDB is configured to use no more than 9GB of memory for maximum number of possible connections but it eats all (30GB RAM + 13GB swap) on one connection with project import and then crashes - killed by the OS because it is Out Of Memory. Details mentioned in MDEV-30096

            Lachman Miroslav Lachman added a comment - Just "we too" comment. We see very bad behaviors of 10.6 after upgrade from 10.3, namely tested versions 10.6.10 and 10.6.11. Both leaking memory like crazy. MariaDB is configured to use no more than 9GB of memory for maximum number of possible connections but it eats all (30GB RAM + 13GB swap) on one connection with project import and then crashes - killed by the OS because it is Out Of Memory. Details mentioned in MDEV-30096
            marko Marko Mäkelä added a comment -

            For the record, my attempt to merge the fixes to 10.4 would cause incorrect evaluation of many WHERE conditions. I think that complex changes have to be tested in all relevant major branches before being pushed to any main branch.

            marko Marko Mäkelä added a comment - For the record, my attempt to merge the fixes to 10.4 would cause incorrect evaluation of many WHERE conditions. I think that complex changes have to be tested in all relevant major branches before being pushed to any main branch.

            People

              serg Sergei Golubchik
              njehle Nico Jehle
              Votes:
              4 Vote for this issue
              Watchers:
              28 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.