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

Consider utilising a pool based memory allocator

XMLWordPrintableJSON

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

      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:
            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            alexander.gorrod@mongodb.com Alexander Gorrod
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: