Setting completionPortThreads with runtimeconfig.json

[bartosz-jarmuz]

Type of issue

Other (describe below)

Description

Issue description

Hello,
The documentation for setting the ThreadPool MinThreads (https://learn.microsoft.com/en-us/dotnet/core/runtime-config/threading) mentions it's equivalent to ThreadPool.SetMinThreads method https://learn.microsoft.com/en-us/dotnet/api/system.threading.threadpool.setminthreads?view=net-7.0

This method has two parameters - int workerThreads, int completionPortThreads.

Is it possible to set the completionPortThreads with the runtime config? If so, how?

Alternatively, if the completionPortThreads setting does not matter in the new implementations of .NET, could the documents be updated with a remark about this parameter?

Target framework

• .NET Core
• .NET Framework
• .NET Standard

Page URL

https://learn.microsoft.com/en-us/dotnet/core/runtime-config/threading

Content source URL

https://github.com/dotnet/docs/blob/live/docs/core/runtime-config/threading.md

Document Version Independent Id

609c4ded-92cf-873b-26f0-a6f654e3728c

Article author

@gewarren

Metadata

• ID: dfd449c7-1c94-8e2b-7cdf-01e448d6cac3
• Service: dotnet-fundamentals

[gewarren]

@kouvel Could you help with this question?

[kouvel]

Is it possible to set the completionPortThreads with the runtime config? If so, how?

There hasn't been a config option to set this value. In .NET 7, the value passed to the API is not effective on Windows, as there isn't a separate IO completion thread pool. On Unixes there has never been a separate IO completion thread pool.

Alternatively, if the completionPortThreads setting does not matter in the new implementations of .NET, could the documents be updated with a remark about this parameter?

Yes probably the docs should be updated. In .NET 7 there was a config option to revert to the previous behavior, the config option has already been removed in main for .NET 8.

[bartosz-jarmuz]

Hello @kouvel,
Could you provide a bit more details about "the value passed to the API is not effective on Windows, as there isn't a separate IO completion thread pool."