I read through a bunch of Issues and PR comments releated to this question but I'm unsure what the actual state is and whats planned, hence I'm creating this isssue.
I use .NET Core 3.1 (SDK version 3.1.401). The applications are deployed self contained as container to OpenShift.
By default the following CPU ressources are configured:
- Request: 100 milicores
- Limit: 500 milicores
This results in a Enviornment.ProcessorCount of 1 and hence in a ThreadPool min thread count of 1 as well.
This leads often to threadpool starvation sympthoms.
I know that the Enviornment.ProcessorCount can be adjusted by rising the limit but I'm unsure if this is the way to go with .NET Core 3.1 and also whats planned for .NET 5 (or later versions).
Releated
People active in these issues
Maybe one of you can easily answer this question.
I read through a bunch of Issues and PR comments releated to this question but I'm unsure what the actual state is and whats planned, hence I'm creating this isssue.
I use .NET Core 3.1 (SDK version 3.1.401). The applications are deployed self contained as container to OpenShift.
By default the following CPU ressources are configured:
This results in a Enviornment.ProcessorCount of 1 and hence in a ThreadPool min thread count of 1 as well.
This leads often to threadpool starvation sympthoms.
I know that the Enviornment.ProcessorCount can be adjusted by rising the limit but I'm unsure if this is the way to go with .NET Core 3.1 and also whats planned for .NET 5 (or later versions).
Releated
--cpusto Docker CLI coreclr#23398People active in these issues
Maybe one of you can easily answer this question.