Bug #113776 optimize for btr_insert_into_right_sibling

• Submitted: 26 Jan 2024 12:20
• Modified: 26 Jan 2024 13:24
• Reporter: alex xing (OCA)
• Status: Verified
• Category: MySQL Server: InnoDB storage engine
• Severity: S5 (Performance)
• Version: 8.0.32
• OS: Any
• CPU Architecture: Any
• Tags: Contribution

[26 Jan 2024 12:20] alex xing

Description:
Optimization term:
1. compute the value of max_size only when realy needs
2. execute btr_page_get_father after rec is judged

How to repeat:
just read the code

Suggested fix:
optimize as the below patch

[26 Jan 2024 12:21] alex xing

a simple patch to describe the optimization based on 8.0.32

(*) I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it.

Contribution: optimize.patch (text/plain), 1.46 KiB.

[26 Jan 2024 13:24] MySQL Verification Team

Hello Alex Xing,

Thank you for the report and contribution.

regards,
umesh