Dynamically allocate WT_SESSIONs internally for session_max

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Not Applicable
    • None
    • Storage Engines, Storage Engines - Foundations
    • None
    • None

      The internal structures for WT_SESSIONs are allocated upfront based on session_max. The default is 33k, which roughly requires 50-70MB of memory. Realistically, most users don't use more than 1,000 sessions at any given time. As a benefit, this would pave the way to allow us to modify the session_max at runtime when we're approaching the limit. 

            Assignee:
            [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            Gregory Wlodarek
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: