MySQL Bugs: #116026: Improving Binlog Group Commit Scalability

Bug #116026	Improving Binlog Group Commit Scalability
Submitted:	6 Sep 2024 11:15	Modified:	25 Sep 2024 10:50
Reporter:	Bin Wang (OCA)	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Server: Optimizer	Severity:	S4 (Feature request)
Version:	all versions	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	Group Commit，performance

Description:
Threads that should not be activated are being triggered, leading to unnecessary context switches with each activation. For detailed explanations, refer to: https://advancedmysql.github.io/blogs/binlog_group.html.

How to repeat:
Under high concurrency, the _pthread_mutex_con_lock bottleneck is exposed in Sysbench and BenchmarkSQL's TPC-C tests.

Hi,

Nice write-up, and interesting idea to use mysql bugs database to promote your blog but you need to put here the way to reproduce the problem

I wish more blogs like this were promoted here (and elsewhere). It is technical and informative.

The blog helps people better understand the optimization mechanisms. Originally, the blog didn’t exist; it was created specifically to report bugs.

There are still many questions to raise; I have prepared them in advance.

Performance issues are also a type of bug, known as performance bugs.

This performance issue is a highly challenging one, and I am certain it is a problem. It has been two years since I first discovered this issue.

If this is not a bug, it can be considered a feature request.

Verified as Feature Request

OP changed location of blog.
For those of you looking for it, I was able to find it here.

https://github.com/enhancedformysql/blogs/blob/main/binlog_group.md