Description
I am running a random-write workload where the bloom filters don't fit in the block cache (but do fit in page cache) which causes a lot of block cache churn. I'm seeing MemTracker::Release and MemTracker::Consume take the majority of CPU on the system.
It seems like this is low-hanging fruit – we don't need exactly up-to-date accounting here so should be pretty easy to optimize.