Bug #78952 tuning the log_lock contention for IO_THREAD and SQL_THREAD in rpl_slave.cc

• Submitted: 24 Oct 2015 10:47
• Modified: 23 Jun 2016 13:11
• Reporter: Fangxin Flou (OCA)
• Status: No Feedback
• Category: MySQL Server: Replication
• Severity: S5 (Performance)
• Version: 5.7.9
• OS: Any
• CPU Architecture: Any
• Tags: binlog, replication

[24 Oct 2015 10:47] Fangxin Flou

Description:
SQL Relay slowly when proceeding on the current relay log file.

Optimize the log lock of SQL thread, the SQL relay performance can be improved by 30% or more.

How to repeat:
Testing write operation on master side, and check the slave side SQL relay performance.

Speed on the current relay log file is much slower than the history relay log file.

Suggested fix:
Optimize the log_lock contention in SQL thread.

Please check the attachment, I wrote a new next_event function.

[24 Oct 2015 10:49] Fangxin Flou

Patch file for slave SQL thread log_lock optimization.

Attachment: onesql-5.7.9-core01-patch.txt (text/plain), 26.88 KiB.

[23 May 2016 13:11] MySQL Verification Team

In order to submit contributions you must first sign the Oracle
Contribution Agreement (OCA). For additional information please check
http://www.oracle.com/technetwork/community/oca-486395.html

If you have any questions, please contact the MySQL community team at
http://www.mysql.com/about/contact/?topic=community

[23 May 2016 13:12] MySQL Verification Team

Hi,

In addition to the OCA, do you have any "perf" output or some other profiling to show the improvement with/without the patch?

[24 Jun 2016 1:00] Bugs System

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".