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

ResultTracker exhibits high contention under non-batched write workload

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 1.0.0
    • 1.2.0
    • perf, rpc
    • None

    Description

      I am running a YCSB workload with non-batched writes, and I see ResultCache among the highest CPU consumers (>15% of the CPU). There's a lot of lock contention on the result cache map. We should consider a more concurrent data structure and/or finer-grained locking.

      Attachments

        1. pprof13384.0.svg
          105 kB
          Todd Lipcon
        2. fg.svg
          910 kB
          Todd Lipcon

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: