[MDEV-35190] HASH_SEARCH() is duplicating effort before HASH_INSERT() or HASH_DELETE() - Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Fixed
Affects Version/s: 10.5, 10.6, 10.11, 11.4
Fix Version/s: 10.6.21, 10.11.11, 11.4.5
Component/s: Storage Engine - InnoDB
Labels:
- performance

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

MDEV-35247 ut_fold_ull() and ut_hash_ulint() are a waste

Closed

MDEV-35484 InnoDB hash_table_t::array is not aligned to cache line size

Open

MDEV-35049 fix innodb-adaptive-hash-index scalability with multiple threads

In Testing

MDEV-35189 Updating cache for INFORMATION_SCHEMA.INNODB_LOCKS et al is suboptimal

Closed

Activity

People

Assignee:: Marko Mäkelä

Reporter:: Marko Mäkelä

Votes:: 1 Vote for this issue

Watchers:: 5 Start watching this issue

Dates

Created:: 2024-10-17 08:43

Updated:: 2024-11-22 11:57

Resolved:: 2024-11-21 10:15

Git Integration

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