Support returning unowned KeyStrings from SortedDataInterface

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • 1
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      During the investigation of a performance regression BF-29842, I find that the classic engine uses WriedTigerIndexCursorBase::curr  which consumes 0.5% CPU, but the new SBE engine uses WriedTigerIndexCursorBase::getKeyStringEntry  which consumes 5.75% CPU. 

      The profiler shows a large amount of CPU on memory allocation in KeyString copy, but not for curr(). The curr() version avoids returning full BSON object in some cases, we should do some optimization on the keyString version.

              Assignee:
              Wei Hu
              Reporter:
              Zixuan Zhuang
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: