Timeline for InnoDB buffer getting higher every day. How to flush the buffer pool?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 26, 2022 at 13:53 | vote | accept | Jose M Martin | ||
| May 25, 2022 at 15:00 | history | tweeted | twitter.com/StackDBAs/status/1529477387922165762 | ||
| May 25, 2022 at 14:04 | comment | added | Wilson Hauck | Flushing the buffer pool (with your high usage) will cause a flurry of READ activity from your tables until the active rows are once again in the buffer pool. You should expect several minutes or an hour until all the heavily used tables have data back into the pool. If you monitor in the same manner and 'paper log' the usage every 5 minutes, you will see the effect of filling the buffer pool back up. If you also track SHOW GLOBAL STATUS LIKE 'innodb%reads%'; each 5 minutes, you will see the slowing of cumulative reads as time goes on which is a good thing. | |
| May 25, 2022 at 13:30 | comment | added | Wilson Hauck | Additional information request, please. RAM size, # cores, any SSD or NVME devices on MySQL Host server? Post on pastebin.com and share the links. From your SSH login root, Text results of: A) SELECT COUNT(*) FROM information_schema.tables; B) SHOW GLOBAL STATUS; after minimum 24 hours UPTIME C) SHOW GLOBAL VARIABLES; D) SHOW FULL PROCESSLIST; AND very helpful OS information, includes - htop OR top for most active apps, ulimit -a for list of limits, iostat -xm 5 3 for IOPS by device & core/cpu count, for server workload tuning analysis to provide suggestions. | |
| May 24, 2022 at 21:17 | answer | added | Rick James | timeline score: 2 | |
| S May 24, 2022 at 6:44 | review | First questions | |||
| May 24, 2022 at 9:01 | |||||
| S May 24, 2022 at 6:44 | history | asked | Jose M Martin | CC BY-SA 4.0 |