3 ms·
I’m not up to date on the recent changes, but problems we had with vacuum were more computation and iops related than memory related. Basically in a database w
by ses1984 2y ago
I’m not up to date on the recent changes, but problems we had with vacuum were more computation and iops related than memory related.
Basically in a database with a lot of creation/deletion, database activity can outrun the vacuum, leading to out of storage errors, lock contention, etc
In order to keep throughput up, we had to throttle things manually on the input side, to allow vacuum to complete. Otherwise throughput would eventually drop to zero.
- sgarland 2y agoYou can also tune various [auto]vacuum settings that can dramatically increase the amount of work done in each cycle. I’m not discounting your experience as anything is possible, but I’ve never had to throttle writes, even on large clusters with hundreds of thousands of QPS.