MySQL Bugs: #113564: write-only mode performance decreases by 15% in heavy workload

Bug #113564	write-only mode performance decreases by 15% in heavy workload
Submitted:	5 Jan 2024 10:49	Modified:	11 Jun 2024 5:32
Reporter:	holmer deng	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S5 (Performance)
Version:	8.0	OS:	Any (>= glibc 2.25 )
Assigned to:		CPU Architecture:	Any
Tags:	glibc pthread_mutex_cond_lock pthread_cond_wait

File:	Maximum allowed size is 50MB.
Description:
Privacy:

If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.

To split a large file:

On *nix platforms use the split command e.g. split -b 50MB <my_large_archive> <my_split_archive_prefix>
On windows use WinZip or a similar utility to split the large file

rebuild mysql version in 8.0.35 with flags(-fno-omit-frame-pointer)

Attachment: 8.0.35_glibc2.31_with_dwarf.tar (application/x-tar, text), 2.10 MiB.

__pthread_mutex_cond_lock no "unknow" calls

Attachment: 8.0.35_glibc2.31_dwarf_new.svg (image/svg+xml, text), 794.65 KiB.

mysql8.0.18 vs mysql8.0.19 flame graphs

Attachment: mysql8.0.18 vs mysql8.0.19 flame graphs.tar (application/x-tar, text), 2.27 MiB.

machine infos

Attachment: mysql 8.0.18 vs 8.0.36 slowdown.tar (application/x-tar, text), 2.46 MiB.