[SERVER-64829] Do not materialize key twice in WiredTigerIndexCursorBase::seek Created: 23/Mar/22  Updated: 29/Oct/23  Resolved: 29/Mar/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.0.0-rc0

Type: Task Priority: Major - P3
Reporter: Dan Larkin-York Assignee: Dan Larkin-York
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: QO 2022-04-04
Participants:

 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.



 Comments   
Comment by Githook User [ 29/Mar/22 ]

Author:

{'name': 'Dan Larkin-York', 'email': 'dan.larkin-york@mongodb.com', 'username': 'dhly-etc'}

Message: SERVER-64829 Do not materialize key twice in WiredTigerIndexCursorBase::seek
Branch: master
https://github.com/mongodb/mongo/commit/eb383f01d48617138db88493a22999471c4e218d

Generated at Thu Feb 08 06:01:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.