[MDEV-21925] Redo log mutex competition is serious Created: 2020-03-12  Updated: 2020-04-05  Resolved: 2020-04-05

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.5.1
Fix Version/s: 10.5.2

Type: Bug Priority: Critical
Reporter: peng Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: innodb

Issue Links:
Relates
relates to MDEV-21534 improve locking/waiting in log_write_... Closed
relates to MDEV-21923 Write redo log concurrently without lock Open

 Description   

In the high concurrent write scenario, the redo log mutex takes up a lot of CPU time。
In order to solve this problem,MySQL #WL10310 optimizes the redo log(unlock and write concurrently)。
Does MariaDB have any improvement plans？

 Comments   
Comment by Marko Mäkelä [ 2020-03-12 ]

MDEV-21534, which was implemented recently in 10.5, should reduce the mutex contention.

You filed MDEV-21923 for a very similar question, which I answered there by linking to existing tickets.

Comment by Vladislav Vaintroub [ 2020-03-12 ]

yaojiapeng, this is exactly what MDEV-21534 was for. You won't see as much log_write_up_to() CPU use after this.
Also, high concurrency scenario is much more improved.

Generated at Thu Feb 08 09:10:52 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.