Repository navigation
Performance regression testing and issue triage in dotnet/runtime #137560
Unanswered
alex-namely
asked this question in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I've been following several .NET 11 performance reports, especially those involving the thread pool. Some concern previews and release candidates, while others were reported against the final .NET 11.0.0 release.
Examples
Performance regression coverage
What worries me isn't any single regression, but the number of substantial slowdowns reported across different workloads and stages of the release. They may have different causes, but together they make me question whether performance checks for thread-pool changes cover enough real-world scenarios.
Issue triage and ownership
I also have two concerns about how performance issues are handled:
Given these regressions, do you think the current testing and triage processes need improvement?
Thanks to everyone working on the runtime.
P.S. I used AI to help phrase this post. The concerns and questions are my own.
All reactions