[SERVER-66435] Always use classic engine for IDhack plans Created: 12/May/22  Updated: 29/Oct/23  Resolved: 20/Oct/22

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

Type: Task Priority: Major - P3
Reporter: Anton Korshunov Assignee: Anna Wawrzyniak
Resolution: Fixed Votes: 0
Labels: pm2697-m3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Problem/Incident
Related
is related to SERVER-66437 Improve performance of IDhack plans i... Open
Backwards Compatibility: Fully Compatible
Backport Requested:
v6.0
Sprint: QO 2022-05-16, QO 2022-05-30, QE 2022-10-17, QE 2022-10-31
Participants:
Linked BF Score: 35

 Description   

As part of the SBE Plan Cache project we tried various optimization to improve the performance of the IDhack queries but were not able to catch up with the classic cache which has a special fast path for generating IDhack plans, which are very simple and very cheap to generate performance wise. To recover the query latency for IDhack plans with the SBE engine turned on as the default we decided to reply on the fall back mechanism and execute these queries with the classic engine. In the future we should revisit this issue and find a proper solution for how to reduce query latency for IDhack queries in SBE.



 Comments   
Comment by Githook User [ 12/Oct/22 ]

Author:

{'name': 'Anna Wawrzyniak', 'email': 'anna.wawrzyniak@mongodb.com', 'username': 'anna-wawrzyniak'}

Message: SERVER-66435 Always use classic engine for IDhack plans
Branch: master
https://github.com/mongodb/mongo/commit/2e51cfe597385fadd4d7610ada1111b00dccb14f

Comment by David Storch [ 13/May/22 ]

I am removing the "6.0 Required" fixVersion due to SERVER-66445.

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