[
https://issues.apache.org/jira/browse/KUDU-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated KUDU-1502:
------------------------------
Attachment: fg-memtracker-commented-out.svg
flame graph with memtracker calls commented out of the block cache. Block cache
still takes ~14% CPU but much more reasonable
> 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
> 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
(v6.3.4#6332)
