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

HASH_SEARCH() is duplicating effort before HASH_INSERT() or HASH_DELETE()

    XMLWordPrintable

Details

    Description

      The InnoDB hash table implementation defines the macros HASH_SEARCH, HASH_INSERT, and HASH_DELETE. Often, a HASH_SEARCH operation would already navigate to the correct hash bucket and to the correct position for a subsequent insert or delete operation. This effort will be wasted, because there is no way for HASH_INSERT or HASH_DELETE to refer to that position.

      Similar to what was done to buf_pool.page_hash in MDEV-26826, we had better replace these macros with something more efficient, basically passing some kind of "iterator" from a search operation to the insert or delete operations.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-35247 ut_fold_ull() is a waste on 64-bit systems

          • Major - Major loss of function.
          • In Review

          Task - A task that needs to be done. MDEV-35049 fix innodb-adaptive-hash-index scalability with multiple threads

          • Major - Major loss of function.
          • In Progress

          Bug - A problem which impairs or prevents the functions of the product. MDEV-35189 Updating cache for INFORMATION_SCHEMA.INNODB_LOCKS et al is suboptimal

          • Major - Major loss of function.
          • In Review

          Activity

            People

              debarun Debarun Banerjee
              marko Marko Mäkelä
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

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