[MDEV-37619] The forced use of THD accessor functions hurts InnoDB performance - Jira

XML

Word

Printable

Details

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

Bug Category:
Related to performance
Sprint:
Q4/2025 Server Maintenance

Description

The testing that was conducted in MDEV-37152 proves that making class THD opaque for InnoDB is costing a significant amount of performance. Applying this 10.11 based change would improve the throughput under one test setting by 1.25%. For another branch that includes further performance fixes, a performance gain of 2.43% was measured.

Exposing the internals of THD to InnoDB would also allow add debug assertions to document and enforce some metadata locking rules; examples include MDEV-37365 and MDEV-35895.

In the past, serg has been against exposing server internals to more storage engines. They are already being exposed to some storage engines.

Attachments

Issue Links

blocks

MDEV-37152 buf_page_get_gen -> buf_pool->stat.n_page_gets++ high cpu utilisation

In Progress

relates to

MDEV-35895 purge_sys_t::close_and_reopen() can busy loop for a long time

Open

MDEV-37365 Crash when ALTER TABLE on parent runs concurrently with INSERT on child

Confirmed

Activity

People

Assignee:: Sergei Golubchik

Reporter:: Marko Mäkelä

Assigned for Implementation:: Marko Mäkelä

Assigned for Testing:: Saahil Alam

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Dates

Created:: 3 days ago 11:14

Updated:: Yesterday 07:21

Git Integration

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