Question : dotnet counters ThreadPool Thread Count and ThreadPool.SetMinThread

[mamdos]

I moved this issue from microsoft/dotnet to this repo.

Hello
I set ThreadPool.SetMinThread to 200 but ThreadPool Thread Count in dotnet counters shows less than 200.
Does ThreadPool Thread Count show just in use thread?
please explain.

[mamdos]

issue link : microsoft/dotnet#1460

[dotnet-policy-service]

Tagging subscribers to this area: @mangod9
See info in area-owners.md if you want to be subscribed.

[stephentoub]

ThreadPool.SetMinThreads doesn't force that number of threads into existence if there's not enough work available for them to do. Rather, it sets the min threshold up to which point the pool will ensure there are threads available if there's work available. For example, let's say you set the min to 10. You queue a work item, there are currently zero threads available to process that work item, so the pool will immediately inject a thread. Now you queue another 9 work items. There are no threads available to process those work items (the previous one is still busy with the previous work item), so the pool will immediately inject another 9 threads to handle those work items. Now you queue 2 more work items. You've reached the minimum you set of 10 threads, so the pool will no longer immediately inject additional threads and will instead prefer to wait for one of the existing threads to finish processing the previously queued work items so that it may handle one of the newly queued ones.

[mamdos]

Thank you for the response