LogBlockManager start-up is slow due to MemTracker atomic contention

I'm looking at startup time on a cluster with lots of data per node. On this cluster, the tablet server takes about 30 seconds to start the LogBlockManager, and appears CPU bound. I grabbed a profile and it seems like most of the CPU is spent in MemTracker::Release and Consume (see attached flame graph).