We have experienced huge IOPS on Knot resolver instances in production. Is it probable, that the reason is the lmdb cache persistence? Can we lower the impact on the hdd somehow, e.g with writeback in exchange for having the cache synchronized in realtime?
If the cache doesn't fit into RAM, the latency will likely be too high anyway. The file mainly provides persistence across daemon restarts and it simplifies sharing among otherwise independent processes.