Timeline for How to identify if my innodb buffer pool is choking ? (and should i increase it ?)
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Dec 8, 2022 at 17:04 | vote | accept | Harshit | ||
| S Dec 8, 2022 at 17:04 | vote | accept | Harshit | ||
| S Dec 8, 2022 at 17:04 | |||||
| Dec 8, 2022 at 17:03 | vote | accept | Harshit | ||
| S Dec 8, 2022 at 17:04 | |||||
| Dec 7, 2022 at 19:49 | comment | added | Bill Karwin | Or graduate to a column store instead of doing OLAP queries in MySQL. MySQL is an OLTP database, big scans and aggregations are not its strength. | |
| Dec 7, 2022 at 19:30 | comment | added | Rick James | Reading 35GB will clearly thrash a 1.5GB buffer_pool. Doing it every few minutes? Let's discuss Summary Tables to eliminate the need for the big scans. My point is that you may be able to use 1.5G much more efficiently, and not worry so much about "big scans". | |
| Dec 7, 2022 at 15:57 | history | edited | RolandoMySQLDBA |
edited tags
|
|
| Dec 7, 2022 at 15:49 | answer | added | RolandoMySQLDBA | timeline score: 1 | |
| Dec 7, 2022 at 14:10 | answer | added | Phani Kiran Mullapudi | timeline score: 2 | |
| Dec 7, 2022 at 13:41 | history | migrated | from stackoverflow.com (revisions) | ||
| Dec 7, 2022 at 6:03 | comment | added | danblack |
innodb_buffer_pool_read_requests (needs a page) vs innodb_buffer_pool_reads (from disk)
|
|
| Dec 7, 2022 at 5:57 | history | asked | Harshit | CC BY-SA 4.0 |