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

Consider utilising a pool based memory allocator

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • WiredTiger
    • None
    • Storage Execution

    Description

      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.

      Attachments

        Activity

          People

            backlog-server-execution Backlog - Storage Execution Team
            alexander.gorrod@mongodb.com Alexander Gorrod
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: