Thread pool should reap threads in a reasonable amount of time after spikes

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Server Programmability
    • ALL
    • SP Prioritized List
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We reset _lastFullUtilizationDate every time we reap, meaning we get to wait another maxIdleThreadAge before we reap another thread. This gives us a maximum thread reap rate of 120/hour with our current defaults. When deailing with thousands of threads or more, this. is painfully slow.

            Assignee:
            Unassigned
            Reporter:
            Ronald Steinke (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: