mysql.innodb.buffer_pool_read_requests
The number of logical read requests.Dimensions:None
Related Insights (2)
Working Set Exceeding Memory Causing Disk Thrashingcritical
When the database's active working set (frequently accessed data and indexes) exceeds available RAM (InnoDB buffer pool), the instance must fetch pages from disk repeatedly. This causes ReadIOPS to spike, ReadLatency to climb, and overall query performance to degrade as disk I/O becomes the bottleneck.
▸
InnoDB Buffer Pool Thrashingwarning
Working set exceeds available buffer pool memory, forcing excessive disk reads. Buffer pool efficiency drops as pages are constantly evicted and reloaded, causing disk I/O saturation and query latency increases.
▸