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

MariaDB:performance seems to be limited when the value of parameter innodb_thread_concurrency is not zero

Details

    Description

      We operate performance testing of select statments on MariaDB Gelara cluster by jmeter whose concurrency is 30 . The results tell that QPS is about 20 when the value of parameter innodb_thread_concurrency is not zero (e.g. ),and QPS rises to 200 when the value of parameter innodb_thread_concurrency sets to zero.
      It seems the various values of parameter innodb_thread_concurrency have no effects on QPS,that does not make senses.

      CPUCores Concurrency innodb_thread_concurrency QPS
      144 30 32 20
      144 30 0 200
      144 30 128 20
      144 30 144 20
      144 30 500 20

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-23379 Deprecate and ignore options for InnoDB concurrency throttling

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Task - A task that needs to be done. MDEV-23397 Remove deprecated InnoDB options in 10.6

          • Major - Major loss of function.
          • Closed

          Activity

            Transition Time In Source Status Execution Times
            Sergei Golubchik made transition -
            Open Closed
            		28d 6h 2m 1

            People

              Unassigned Unassigned
              jjs Wenwen Jing
              Votes:
              0 Vote for this issue
              Watchers:
              3 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.