Timeline for MySQL query suddenly slow down
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 30, 2018 at 16:48 | comment | added | Rick James | @ColeraSu - 250MB Data? Add on the Indexes. If the total is still well under 2GB, then once loaded the data and indexes should live in the buffer_pool. | |
| Apr 30, 2018 at 16:46 | comment | added | Rick James |
5.5 introduced innodb_old_blocks_pct, which mostly eliminates the eviction problem mentioned.
|
|
| Apr 13, 2018 at 0:20 | comment | added | Wilson Hauck | A FLUSH TABLES (direct or possibly result of operations) will cause system to need to read innodb data to put into innodb_buffer_pool again. | |
| Apr 6, 2018 at 17:17 | comment | added | Colera Su | But slowdown still occurs even if no mysqldump was run. Another question: how can data with ~250MB size not fit into a 2G buffer pool? | |
| Apr 1, 2018 at 21:26 | history | answered | dbdemon | CC BY-SA 3.0 |