Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-76782

emplace the DecorationContainer into Decorable's allocation

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Service Arch
    • 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.

            Assignee:
            backlog-server-servicearch Backlog - Service Architecture
            Reporter:
            billy.donahue@mongodb.com Billy Donahue
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated: