[SERVER-65157] BatchedDeleteStage makes an unnecessary fetch for each document Created: 01/Apr/22 Updated: 29/Oct/23 Resolved: 13/Apr/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Haley Connelly | Assignee: | Haley Connelly |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-2227-M3 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Execution Team 2022-04-04, Execution Team 2022-04-18 |
| Participants: |
| Description |
|
The current BatchedDeleteStage
One solution is to hold the WorkingSetMembers in memory and only free them once the deletes are committed |
| Comments |
| Comment by Githook User [ 13/Apr/22 ] |
|
Author: {'name': 'Haley Connelly', 'email': 'haley.connelly@mongodb.com', 'username': 'haleyConnelly'}Message: |