You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kudu.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2016/06/24 05:47:16 UTC

[jira] [Created] (KUDU-1502) Block cache with churn burns lots of CPU in MemTracker consume and release

Todd Lipcon created KUDU-1502:
---------------------------------

             Summary: 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


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)