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

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

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.9.0
    • Fix Version/s: 1.8.0
    • Component/s: perf, util
    • Labels:
      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

        1. fg.svg
          818 kB
          Todd Lipcon
        2. fg-memtracker-commented-out.svg
          946 kB
          Todd Lipcon

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: