-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Query Execution
-
None
-
3
-
TBD
-
None
-
None
-
None
-
None
-
None
-
None
-
0
For an update-by-id run through the express executor, we actually create and seek two WT cursors on the record store, not one. That is, we find the _id in the index, then seek to the corresponding RecordId a first time here, and then a second time when calling collection_internal::updateDocumentWithDamages (same for updateDocument()).
It should be possible to avoid creating the second cursor here and re-using the existing one.
Note that even if we re-use the cursor, WT will internally re-seek the cursor, though we should look into changing that as well.
As part of this ticket we should also investigate whether a similar improvement is possible for deletes.
- is depended on by
-
-
- Needs Scheduling
-
- is related to
-
WT-14651 __wt_btcur_modify calls btcur_search even if the cursor is already positioned
-
- Needs Scheduling
-
- related to
-
-
- Needs Scheduling
-