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

fix for MDEV-24670 causes a performance regression

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Blocker
    • Resolution: Cannot Reproduce
    • N/A
    • N/A
    • N/A

    Description

      The regression test suite found a regression for the t_threadpool* tests. It turned out to be a regression for sorting rows. Further analysis in TODO-4510 traced it to commit a057a6e41f2 for MDEV-24670.

      The regression gets bigger when more rows have to be sorted and is in the order of 3% for 1000 rows. Additionally the execution times for queries fluctuate more than normal.

      Attachments

        1. 25c627885a2-good.svg
          129 kB
        2. a057a6e41f2-bad.svg
          127 kB
        3. big_ranges_tp_off.png
          big_ranges_tp_off.png
          7 kB
        4. big_ranges_tp_off2.png
          big_ranges_tp_off2.png
          7 kB
        5. big_ranges_tp_on.png
          big_ranges_tp_on.png
          7 kB
        6. big_ranges_tp_on2.png
          big_ranges_tp_on2.png
          6 kB
        7. errlog-bad.txt
          3 kB
        8. errlog-good.txt
          3 kB
        9. pmp_raw_1706708923.txt.gz
          12 kB
        10. report.txt.gz
          38 kB
        11. report-no-children.txt.gz
          15 kB

        Issue Links

          is caused by

          Task - A task that needs to be done. MDEV-24670 avoid OOM by linux kernel co-operative memory management

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

          Activity

            People

              Unassigned Unassigned
              axel Axel Schwenke
              Votes:
              1 Vote for this issue
              Watchers:
              8 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.