[SERVER-60608] Avoid re-materializing the entire document between filter/project/sort/limit/skip and group in common cases Created: 11/Oct/21 Updated: 06/Dec/22 Resolved: 18/Jan/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Yoon Soo Kim | Assignee: | Backlog - Query Execution |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | sbe | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Execution
|
| Participants: |
| Description |
|
We should be able to eliminate mkbson stage(s) to avoid unnecessary materialization when multiple pipeline stages are pushed down together to SBE. As of now, we were able to avoid mkbson stage on the direct top of a collection scan ( We need to generalize the idea so that it can be applied to other plan shape too. Ian's thought on a project stage:
Update at 3pm GMT 10/12/2021: |
| Comments |
| Comment by Ethan Zhang (Inactive) [ 18/Jan/22 ] |
|
This was removed from PM-2267. |
| Comment by Ian Boros [ 12/Oct/21 ] |
|
yoonsoo.kim Ah, I meant my comment was written at the same time you were updating the description. I didn't touch the description myself. |
| Comment by Yoon Soo Kim [ 12/Oct/21 ] |
|
ian.boros, I don't see and didn't see your updates. Could you update the description if there's another missing information? |
| Comment by Yoon Soo Kim [ 11/Oct/21 ] |
|
In response to svilen.mihaylov and pawel.terlecki's opinions, changed the status to "needs scheduling" |
| Comment by Pawel Terlecki [ 11/Oct/21 ] |
|
+1 i feel we want to keep the effort relatively small even if we cannot get all the performance. The query optimizer will help with that. |