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.
- depends on
-
WT-11126 Add configuration compilation to speed up WT_SESSION::begin_transaction
-
- Closed
-
- is related to
-
WT-12777 Config compilation API returns invalid default value for a string based configuration
-
- Closed
-
-
-
- Closed
-