-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Server Programmability
-
Service Arch 2023-05-15, Service Arch 2023-05-29, Service Arch 2023-06-12, Service Arch 2023-06-26, Service Arch 2023-07-10, Service Arch 2023-07-24, Service Arch 2023-08-07
Perhaps Decorable can share a single allocation with its associated DecorationContainer.
This would save an alloc/dealloc in every Decorable (I'm looking at you, OperationContext, and make accessing the decorations more cache-friendly.
This could be done perhaps by defining overloads for its new & delete operators.
- depends on
-
SERVER-78390 Decorable subsystem refactoring
- Closed
- is related to
-
SERVER-79956 benchmark Decorations
- Backlog