[SERVER-66785] Performance tuning for number of fields being covered Created: 26/May/22 Updated: 14/Apr/23 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Svilen Mihaylov (Inactive) | Assignee: | Backlog - Query Optimization |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Optimization
|
| Participants: |
| Description |
|
If we have a collection scan generated from a Sargable node, probably should not cover too many fields (e.g. > 5). Also consider avoiding too many fields if there are filters (no need to retrieve a field which we do not need) |