[SERVER-13685] refactor fast-path for _id queries to not create a CanonicalQuery Created: 22/Apr/14 Updated: 06/Dec/22 Resolved: 05/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Performance, Querying |
| Affects Version/s: | 2.6.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | hari.khalsa@10gen.com | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Won't Do | Votes: | 1 |
| Labels: | query-44-grooming | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Assigned Teams: |
Query
|
||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
We should be using the idhack more aggressively in .find()s. When possible we should also avoid creating the CanonicalQuery for idhack .find() queries. |
| Comments |
| Comment by David Storch [ 05/Jul/19 ] |
|
This is an old idea for improving the performance of find-by-_id queries that I don't see a reason to pursue right now. From an internal engineering perspective, it's better if all queries are represented by a CanonicalQuery rather than skipping this part of the code path. Closing this ticket as Won't Do. |
| Comment by David Storch [ 25/Apr/14 ] |
|
Splitting this into two tickets. This one will be for not creating a CanonicalQuery in the idhack path. Re-enabling projection for the idhack will be covered by |