Avoid config string parsing when setting cursor bounds

XMLWordPrintableJSON

    • Storage Engines
    • 2024-03-05 - Claronald, 2024-03-19 - PacificOcean, 2024-04-02 - GreatMugshot, 나비 (nabi) - 2024-04-16
    • 8
    • v8.0

      The current bound already does pretty minimal string parsing, but it does still show up in perf. If we want to use the cursor bounds API, we should aim to eliminate config string parsing entirely.

      One option would be to create specific APIs for set_lower_bound, set_upper_bound, with a boolean "inclusive" argument. Or we could consider an API like WT-11126.

      This isn't a huge perf issue at the moment, but it would further speed up our cursor-seeking performance.

              Assignee:
              Luke Pearson
              Reporter:
              Louis Williams
              Clarisse Cheah, Jie Chen
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: