Uploaded image for project: 'Kudu'
  1. Kudu
  2. KUDU-1502

Block cache with churn burns lots of CPU in MemTracker consume and release

Agile BoardAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 0.9.0
    • 1.8.0
    • perf, util
    • None

    Description

      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.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            tlipcon Todd Lipcon
            tlipcon Todd Lipcon
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment