I've already optimized the related queries using the performance analyzer. There's not much left to work with in that regard, the confirmation process has been reduced almost entirely to pure disk reads, like 90% of it initially. So the process accelerates as the RAM starts to fill (from a cold start), and is eventually screaming (over 100 blocks per second) with no disk reads and 90% RAM full.