Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
10.6.3, 10.6
-
None
Description
- In 10.6, trx_rseg_t mutex was ported to use latch. As part of this porting profiling of the patch was removed. This patch reenables it given that the said latch continues to occupy the top slots in the contention list
When I applied the said patch and enabled profiling trx_rseg_latch_key was 2nd hottest instrument from the InnoDB SE perspective.
wait/synch/cond/threadpool/worker_cond | 46351983.3024 | 167603 |
wait/synch/mutex/innodb/log_sys_mutex | 8716632.1922 | 122968738 |
wait/synch/cond/mysys/COND_timer | 1516437.4227 | 5397 |
wait/synch/cond/threadpool/timer_cond | 1515688.2689 | 3025 |
wait/synch/cond/aria/SERVICE_THREAD_CONTROL::COND_control | 1501997.0416 | 50 |
wait/synch/rwlock/innodb/trx_rseg_latch_key | 342616.7699 | 98834024 |
Attachments
Issue Links
- causes
-
MDEV-28049 Error on compiling of trx0purge.cc
- Closed
- is caused by
-
MDEV-25062 InnoDB read-write workload hits contention arising from rollback segment mutex
- Closed