[MDEV-34431] More fine grained control of spin loops could be useful - Jira

XML

Word

Printable

Details

Type: Bug
Status: Stalled (View Workflow)
Priority: Critical
Resolution: Unresolved
Affects Version/s: 10.6, 10.11, 11.4
Fix Version/s: 10.6, 10.11, 11.4
Component/s: Storage Engine - InnoDB
Labels:
- performance

Description

In an attempt to address ~~MDEV-34178~~, I enabled spin loops on dict_index_t::lock. This helps in some workloads and causes performance degradation in others, especially when there are large numbers of concurrent connections.

It could make sense to enable spin loops on a case-by-case basis, or to introduce a configuration parameter for choosing when index tree latch acquisition should include spin loops.

Attachments

Issue Links

is blocked by

MDEV-34515 Contention between secondary index UPDATE and purge due to large innodb_purge_batch_size

Closed

MDEV-34759 buf_page_get_low() is unnecessarily acquiring exclusive latch on secondary index pages

Closed

MDEV-34791 Redundant page lookups hurt performance

Closed

relates to

MDEV-34178 Performance regression with IO-bound insert benchmark

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-06-20 11:07

Updated:: 2024-10-13 17:07

Git Integration

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