[SERVER-85828] Optimize CurOpStack construction and destruction Created: 27/Jan/24 Updated: 06/Feb/24 |
|
| Status: | In Progress |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Patrick Freed | Assignee: | Dominic Hernandez |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Service Arch
|
||||||||||||
| Sprint: | Service Arch 2024-02-19 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
CurOpStack is by far the most expensive decoration on OperationContext, both in construction time and destruction time. We should investigate any possible way to optimize construction and destruction of CurOp and CurOpStack, as this would provide a performance benefit for all operations. For details, see |