A common misconception about (auto) vacuum is, that you need to turn it off, to avoid performance problems.
The truth is: you need to make it more aggressive (= run it more frequently) if you have problems with the (additional) I/O load it generates.
@pg-gadfly's link answered it for me:
> VACUUM creates a substantial amount of I/O traffic, which can cause poor performance for other active sessions.
Their wiki is pretty amazing source for postgres's operation: https://www.postgresql.org/docs/12/routine-vacuuming.html
A common misconception about (auto) vacuum is, that you need to turn it off, to avoid performance problems.
The truth is: you need to make it more aggressive (= run it more frequently) if you have problems with the (additional) I/O load it generates.