[SERVER-68110] Investigate apparent regression in classic engine IDHACK Created: 18/Jul/22  Updated: 29/Oct/23  Resolved: 28/Apr/23

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

Type: Task Priority: Major - P3
Reporter: Mihai Andrei Assignee: Colin Stolley
Resolution: Fixed Votes: 0
Labels: query-director-triage
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
Depends
Sub-Tasks:
Key
Summary
Type
Status
Assignee
SERVER-73908 Remove unneeded Lockstats::reset() calls Sub-task Closed Colin Stolley  
SERVER-73909 only call serializeDollarDbInOpDescri... Sub-task Closed Colin Stolley  
SERVER-73910 Streamline index and plan selection f... Sub-task Closed Colin Stolley  
SERVER-73912 avoid copying values in MatchExpressi... Sub-task Closed Colin Stolley  
SERVER-73913 ServerParameter map should be a Strin... Sub-task Closed Colin Stolley  
SERVER-74586 Avoid creating plan cache key for IDH... Sub-task Closed Colin Stolley  
SERVER-76041 Avoid SBE registering slots that aren... Sub-task Closed Colin Stolley  
Assigned Teams:
Query Execution
Backwards Compatibility: Fully Compatible
Sprint: QE 2023-05-15
Participants:
Linked BF Score: 0
Story Points: 10

 Description   

The Queries.IntIdFindOne workload appears to have regressed ~8% between 5.0 and 6.0. This ticket tracks the work to investigate and fix said regression.



 Comments   
Comment by Kyle Suarez [ 28/Sep/22 ]

Removing this from the SBE Performance epic and sending it back to the triage queue.

Comment by Kyle Suarez [ 21/Sep/22 ]

Moving from M3 to M4 since this is the classic engine, not SBE.

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