Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.5, 10.6, 10.7(EOL), 10.8(EOL), 10.9(EOL), 10.10(EOL), 10.11, 11.0(EOL), 11.1(EOL)
-
None
Description
For I/O intensive workloads, the mutexes protecting read_slots and write_slots could potentially become congestion points. This has been under the radar, because there is no PERFORMANCE_SCHEMA instrumentation for them.
Let us add wait/synch/mutex/innodb/tpool_cache_mutex for tracking them.
Attachments
Issue Links
- relates to
-
MDEV-16264 Implement a common work queue for InnoDB background tasks
- Closed
-
MDEV-26827 Make page flushing even faster
- Closed