"
I had the same things, and tons and tons of I/O during it.
Turned out my hosts.db-wal was very large.
On every run it would read for 10s of seconds and re-create hosts.db-shm that each time grew to 100s of mbytes.
-rw-r--r-- 1 hostd hostd 4.0M Mar 2 17:14 hosts.db
-rw-r--r-- 1 hostd hostd 197M Mar 2 17:13 hosts.db-shm
-rw-r--r-- 1 hostd hostd 99G Mar 2 17:14 hosts.db-wal
After executing a checkpoint with truncate and vacuuming it now runs pretty normal again, still keeping an eye on it.
(Not sure if that was a safe action to do, but current state was not sustainable).
Turned out my hosts.db-wal was very large.
On every run it would read for 10s of seconds and re-create hosts.db-shm that each time grew to 100s of mbytes.
-rw-r--r-- 1 hostd hostd 4.0M Mar 2 17:14 hosts.db
-rw-r--r-- 1 hostd hostd 197M Mar 2 17:13 hosts.db-shm
-rw-r--r-- 1 hostd hostd 99G Mar 2 17:14 hosts.db-wal
After executing a checkpoint with truncate and vacuuming it now runs pretty normal again, still keeping an eye on it.
(Not sure if that was a safe action to do, but current state was not sustainable).
