[SERVER-85411] Evaluate the benefits of making `OpCtx` decorations role-specific Created: 18/Jan/24 Updated: 23/Jan/24 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Amirsaman Memaripour | Assignee: | Backlog - Service Architecture |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Service Arch
|
||||||||
| Participants: | |||||||||
| Description |
|
Measure the performance benefits of splitting OperationContext decorations, in particular making them role-specific. This translates into only constructing decorations that are needed to perform tasks for the router or shard-server role. Upon completion of this work, we can decide if the performance benefits of making decorations role-specific is worth the effort. |
| Comments |
| Comment by Phoebe Du [ 23/Jan/24 ] |
|
Re-triage once Server-85325 is finished |
| Comment by Amirsaman Memaripour [ 23/Jan/24 ] |
|
Linking it to another server ticket that is classifying decorations on OperationContext. We can use the findings from that work to estimate the cost savings of making decorations role-specific. |