Scale WiredTiger dhandle limits based on machine size

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Engines, Storage Engines - Server Integration
    • SESI - 2025-09-30
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Customers with larger caches and more CPU resources have room to keep more dhandles open concurrently. We should scale the wiredTigerFileHandleCloseMinimum (close_handle_minimum) based on the size of cache.

      Too low limits cause WT to waste a lot of time attempting to close idle handles, which is not necessary if there is enough memory available.

            Assignee:
            Nick Beckenham
            Reporter:
            Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: