[KUDU-1450] LogBlockManager start-up is slow due to MemTracker atomic contention

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.8.0
• Fix Version/s: 0.9.0
• Component/s: fs, perf
• Target Version/s: 0.9.0
• Assignee: Todd Lipcon
• Reporter: Todd Lipcon
• Created: 12/May/16 02:06
• Updated: 17/May/16 04:53
• Resolved: 17/May/16 04:53

Description

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).