InnoDB 1.1 for MySQL 5.5 User’s Guide (Early Adopter Release) :: 7 Performance and Scalability Enhancements :: 7.22 Separate Flush List Mutex
Section Navigation [Toggle]
- 7 Performance and Scalability Enhancements
- 7.1 Overview of InnoDB Performance
- 7.2 Faster Locking for Improved Scalability
- 7.3 Using Operating System Memory Allocators
- 7.4 Controlling InnoDB Change Buffering
- 7.5 Controlling Adaptive Hash Indexing
- 7.6 Changes Regarding Thread Concurrency
- 7.7 Changes in the Read-Ahead Algorithm
- 7.8 Multiple Background I/O Threads
- 7.9 Asynchronous I/O on Linux
- 7.10 Group Commit
- 7.11 Controlling the Master Thread I/O Rate
- 7.12 Controlling the Flushing Rate of Dirty Pages
- 7.13 Using the PAUSE instruction in InnoDB spin loops
- 7.14 Control over Spin Lock Polling
- 7.15 Making Buffer Cache Scan Resistant
- 7.16 Improvements to Crash Recovery Performance
- 7.17 Integration with MySQL PERFORMANCE_SCHEMA
- 7.18 Improvements to Performance from Multiple Buffer Pools
- 7.19 Better Scalability with Multiple Rollback Segments
- 7.20 Better Scalability with Improved Purge Scheduling
- 7.21 Improved Log Sys Mutex
- 7.22 Separate Flush List Mutex
Starting with InnoDB storage engine 1.1, concurrent access to the buffer pool is faster. Operations involving the flush list, a data structure related to the buffer pool, are now controlled by a separate mutex and do not block access to the buffer pool. You do not need to configure anything to take advantage of this speedup; it is fully automatic.
This is the User’s Guide for InnoDB storage engine 1.1 for MySQL 5.5, generated on 2010-04-13 (revision: 19994) .
