[ https://issues.apache.org/jira/browse/KUDU-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Grant Henke updated KUDU-1502: ------------------------------ Target Version/s: (was: 1.5.0) > Block cache with churn burns lots of CPU in MemTracker consume and release > -------------------------------------------------------------------------- > > Key: KUDU-1502 > URL: https://issues.apache.org/jira/browse/KUDU-1502 > Project: Kudu > Issue Type: Bug > Components: perf, util > Affects Versions: 0.9.0 > Reporter: Todd Lipcon > Priority: Major > Attachments: fg-memtracker-commented-out.svg, fg.svg > > > 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. -- This message was sent by Atlassian JIRA (v7.6.3#76005)