-
Notifications
You must be signed in to change notification settings - Fork 5k
.NET 8 per-preview performance overview #77490
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
Comments
cc @artl93 @stevisok @jeffschwMSFT |
The .NET 9 issues have been moved to #98209. This issue will be closed after remaining regressions are addressed. |
@DrewScoggins @kotlarmilos why aren't the wasm interpreter runs being labeled as interpreter runs and being tracked in #98209 ? |
They are tracked separately in #96444. |
@matouskozak Do we plan to triage tracked issues? |
I took a look at some MonoAOT ones, closed the ones that are no-longer regressed in .NET 9. We should align on what to do with the rest. Let's sync on Wednesday call and decide. |
All issues have been transferred/resolved to .NET 9+. |
Uh oh!
There was an error while loading. Please reload this page.
Description
This issue provides an overview of the all performance regressions from microbenchmark automated runs in WASM, Mono AOT, and Interpreter during the timeframe of .NET 8 preview releases. WASM regressions are tracked separately at dotnet/perf-autofiling-issues#9652.
List of queries for autofilling issues:
Mono AOT
Within the .NET 8 timeframe about 100 microbenchmarks regressed more than 10%. Summary of the most impactful issues to be resolved:
Details
RC2
RC 1
Preview 7
Preview 6
Preview 5
Preview 4
Preview 3
Preview 2
.NET 7 / Preview 1
Mono Interpreter
Within the .NET 8 timeframe about 250 microbenchmarks regressed more than 10%. Summary of the most impactful issues to be resolved:
Details
RC2
Preview 7
Preview 6
Preview 5
Preview 4
Preview 3
Preview 2
.NET 7 / Preview 1
Mono On Disk Size - iOS
Details
.NET 8
The text was updated successfully, but these errors were encountered: