[SERVER-64828] Only check for out-of-order index entries in debug builds 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 each time we call getNext() on a forward index cursor, we'll do an extra check against the key as a workaround for WT-2307. Since that bug has been fixed, this extra comparison is no longer strictly necessary. Removing it from production builds should get us 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 comparison 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-64828 Only check for out-of-order index entries in debug builds
Branch: master
https://github.com/mongodb/mongo/commit/99419b86ee823cf546a2843b9fb6f0b454f14774

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