-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.NET 6 target support #1909
Comments
We may indeed do a few of these things, at the moment there's another appealing option which is to default to the shared thread pool implementation of the pipe scheduler specifically on net6.0 which has some counter and action changes around sync-over-async blocking which was one of the core reasons our custom threadpool remains today. We're going to try in the alpha changing this and looking at behavior to better scale to various size applications and core counts :) |
I've got a PR for .NET 6 in #1939, but I'm not sure about the usages in the issue here - there's a code quality tradeoff because all of them are |
Heads up: this is being reverted in #1992 due to thread pool issues so no release changes planned at this point. I'll be tracking some things down there with the .NET team. |
I'm going to close this out to tidy up - after trying these things out and more importantly how .NET 6 thread pool behaves (specifically not tying into |
Any plan for adding .NET 6 target? We could get benefits from some new API introduced in .NET 6.
WaitAsync
forTimeoutAfter
extensionsRandom.Shared
forRandom
usagePeriodicTimer
forTimer
usagemaybe more ...
The text was updated successfully, but these errors were encountered: