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

AliSQL: [perf] Issue#31 OPTIMIZE CHECK/GRANT OF INNODB TABLE LOCK

    XMLWordPrintable

Details

    Description

      Description:
      ------------
      Since most workload in production environment is normal DML/SELECT
      (this should be very common on most OLTP workload).
      So for InnoDB table lock:
      1. most time there's only LOCK_IX/LOCK_IS table lock
      2. LOCK_S/LOCK_X rarely happen
       
      This patch adds some counters to identify if LOCK_S/LOCK_X is granted
      and quickly exit function lock_table_other_has_incompatible().
      This will improve the performance especially when all DML focused on
      the same table.
       
      For more deatail, please refer: http://bugs.mysql.com/bug.php?id=72948.
       
      This patch also fixes bug#68647 which reduce the overhead of
      'SHOW ENGINE INNODB STATUS' and removes some complier warinings.
      

      https://github.com/alibaba/AliSQL/commit/52d847305f4df21b6f7a67f789a1b46223d591ce

      Attachments

        Issue Links

          Activity

            People

              marko Marko Mäkelä
              svoj Sergey Vojtovich
              Votes:
              0 Vote for this issue
              Watchers:
              4 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.