Consider utilising a pool based memory allocator

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: WiredTiger
    • None
    • Storage Execution
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      There are known issues with memory fragmentation in the MongoDB 3.2 release when running certain workloads (tracked in SERVER-20306).

      One way we may be able to reduce the amount of fragmentation would be to use separate allocator pools for different allocations. Especially within WiredTiger, where there is some knowledge about the expected lifespan of different allocations.

              Assignee:
              [DO NOT USE] Backlog - Storage Execution Team
              Reporter:
              Alexander Gorrod
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: