Bug #62675 | innodb_lru_scan_depth needs a description | ||
---|---|---|---|
Submitted: | 11 Oct 2011 0:39 | Modified: | 26 Nov 2011 16:14 |
Reporter: | Mark Callaghan | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | 5.6.3 | OS: | Any |
Assigned to: | John Russell | CPU Architecture: | Any |
[11 Oct 2011 0:39]
Mark Callaghan
[11 Oct 2011 3:53]
Valeriy Kravchuk
Thank you for the bug report.
[26 Nov 2011 16:14]
John Russell
Description added to the documentation: A parameter that influences the algorithms and heuristics for the flush operation for the InnoDB buffer pool. Primarily of interest to performance experts tuning I/O-intensive workloads. It specifies how far down the buffer pool LRU list the page_cleaner thread scans looking for dirty pages to flush. This is a background operation performed once a second. If you have spare I/O capacity under a typical workload, increase the value. If a write-intensive workload saturates your I/O capacity, decrease the value, especially if you have a large buffer pool.