Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-64829

Do not materialize key twice in WiredTigerIndexCursorBase::seek

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 6.0.0-rc0
    • None
    • None
    • None
    • Fully Compatible
    • QO 2022-04-04

    Description

      Currently we materialize the key in the internal call to seekForKeyString(...), discard the result, and materialize the key again using curr(...). A simple refactoring would allow us not to duplicate work. This should lead to a modest, but non-trivial performance improvement, at least for workloads where the index fits in memory. If the index entries need to be read from disk, then the cost of the extra materialization is rendered trivial.

      Attachments

        Activity

          People

            dan.larkin-york@mongodb.com Dan Larkin-York
            dan.larkin-york@mongodb.com Dan Larkin-York
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: