[SERVER-72681] Investigate perf of new optimizer plans which contain multiple EvaluationNodes Created: 10/Jan/23 Updated: 31/Aug/23 Resolved: 31/Aug/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Hana Pearlman | Assignee: | Backlog - Query Optimization |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | M2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query Optimization
|
||||||||
| Participants: | |||||||||
| Description |
|
Currently, EvaluationNodes are only set up to produce one new binding each, and a chain of EvaluationNodes is lowered to a chain of SBE ProjectStages. There is some concern about how these decisions will affect the performance of plans which contain many EvaluationNodes. This ticket is to investigate the performance of these decisions and determine if any improvement work needs to be done. |