Bug #105043 no need to maintain max_size for some scenarios in btr_insert_into_right_sibling

Submitted: 26 Sep 2021 14:32 Modified: 27 Sep 2021 12:34
Reporter: alex xing (OCA) Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S5 (Performance)
Version:8.0 OS:Any
Assigned to: CPU Architecture:Any

[26 Sep 2021 14:32] alex xing 
Description:
in btr_insert_into_right_sibling, max_size is used to maintain ibuf,but some scenarios need not maintain it.So we can add judgment logic, reduce unnecessary calculations, which may cause a bit consumption of cpu

How to repeat:
just read the code

Suggested fix:
add judgment logic, just as below patch
[26 Sep 2021 14:33] alex xing 
a simple patch to describe the optimization

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

Contribution: commit.patch (text/plain), 1.16 KiB.
[27 Sep 2021 12:34] MySQL Verification Team 
Hi Mr. xing,

Thank you for your bug report.

We have analysed your patch and the original code and concluded that your contribution has merit.

Thank you, especially, for your patch.

Verified as reported.

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.038 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.