-
Notifications
You must be signed in to change notification settings - Fork 24
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
Upgrade to dotnet 7 #215
Comments
Potentially related issue dotnet/runtime#78127 |
@tpill90 curious if you ever tracked this one down. The issue you noted above looks to be fixed in .NET 8 (the fix will first show up in Preview 4, likely available sometime in May). But the change you noticed may be caused by something else. |
I haven't looked at this recently, not since I initially made this issue. I did some profiling then with both Visual Studio and dotTrace, but wasn't able to find anything obvious in my code that seemed to be the issue. There certainly was an increase in resource consumption, but I couldn't tell where it was my code versus the framework. I'll come back around to this in May and see if anything changes. I'll let you know the results either way. Thanks for checking in! |
Released in v2.3.0 |
@AndyAyersMS Looks like this is no longer an issue in .NET 8. Tested on both .NET 6 and .NET 8 and they have the same throughput and CPU consumption. |
Tasks
The text was updated successfully, but these errors were encountered: