Timeline for Tuning innoDB for a write-intensive machine
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 8, 2021 at 23:23 | comment | added | Googlebot |
It's a single-user database. There's no read when I write. The reads are not frequent but heavy, JOINs of millions of rows from tables with billions of rows. Or reading millions of rows with mediumtext.
|
|
| Oct 8, 2021 at 23:17 | comment | added | Rick James | @Googlebot - Allowing dirty pages to pile up in the buffer_pool benefits reads. It is essentially a way to do "delayed" writes. How much data in the entire database? How many reads per second -- both when busy with writes and when not? | |
| Oct 8, 2021 at 23:12 | comment | added | Googlebot |
By writes/s, I was referring to the FILE I/O section of SHOW ENGINE INNODB STATUS \G. I don't see any benefit for dirty pages in a write-intensive system. It is beneficial to avoid unnecessary high I/O affecting reads. But when only writing, it is better to empty the buffer pool for the subsequent operations.
|
|
| Oct 8, 2021 at 20:38 | history | answered | Rick James | CC BY-SA 4.0 |