MicrosoftHi Matt,
We see that the minium worker threads are reset to the default value after a while without known reason
I read your blog post below during my research on how the threadpool works.
We are forced to call the ThreadPool.SetMinThread(x,y) method where we set the x, the minimum number of workter threads, to a high enough number.
However, and this is causing my hair to turn gray, after some time it is rest back to the default which is 1 thread per logical processor right.
What is causing this minimum to reset? The appdomain and application pool aren't recylced as far as I can tell.
Sometimes it happens after a few minutes and sometimes a few hours.
Is there a process/mechanism that resets the threadpool minimum number of threads that you know of?
The only trace on the internet that mentions this problem is at stackoverflow
https://stackoverflow.com/questions/14821874/why-is-threadpool-setminthreads-not-changing-the-minimum-value
We call the ThreadPool.SetMinThread method in the Application_Start of a web application.
I hope you can offer a clue as to what is going on because I have been hunting this for already more than a week and I still cannot explain it
Kind Regards, Tom
Modifying the .NET CLR ThreadPool Settings for ASP.NET 4.x
https://techcommunity.microsoft.com/t5/iis-support-blog/modifying-the-net-clr-threadpool-settings-for-asp-net-4-x/ba-p/357985
