You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AOT related issues dotnet/perf-autofiling-issues#14019 223 regressions, probably AOT and generics dotnet/perf-autofiling-issues#13755 23 regressions, might show opportunities for SIMD improvements dotnet/perf-autofiling-issues#19230 3 regressions, utf16 widening code change. It now uses Vector128.Widen instead of 2 calls to WidenLower and WidenUpper. This should result in theory in the same code as Widen is calling these too and returning pair. There might be something like additional store in the emitted code. To chase further, try to compare before and after emitted code of the WidenAsciiToUtf16 method.
dotnet/perf-autofiling-issues#19230 3 regressions, utf16 widening code change. It now uses Vector128.Widen instead of 2 calls to WidenLower and WidenUpper. This should result in theory in the same code as Widen is calling these too and returning pair. There might be something like additional store in the emitted code. To chase further, try to compare before and after emitted code of the WidenAsciiToUtf16 method.
Issues to look at (most important at top):
AOT related issues
dotnet/perf-autofiling-issues#14019 223 regressions, probably AOT and generics
dotnet/perf-autofiling-issues#13755 23 regressions, might show opportunities for SIMD improvements
dotnet/perf-autofiling-issues#19230 3 regressions, utf16 widening code change. It now uses
Vector128.Widen
instead of 2 calls toWidenLower
andWidenUpper
. This should result in theory in the same code as Widen is calling these too and returning pair. There might be something like additional store in the emitted code. To chase further, try to compare before and after emitted code of theWidenAsciiToUtf16
method.NET8 Preview1-Preview6 comparison - choose previews branches, NET8 p1 and p6 in our case, and one of wasm RunConfig's
https://msit.powerbi.com/groups/me/apps/54e0e83f-07bc-45bf-87b7-a7677ff3af2a/reports/b7f22b49-2eb8-4608-933a-13305cc8fab6/ReportSection587f36b937cea0cbe025?experience=power-bi
interpreter
only few regressions, overall the performance is improved
AOT
there are 200+ regressions from dotnet/perf-autofiling-issues#14019
still mostly improvements in AOT as well
Blazor size regression
The text was updated successfully, but these errors were encountered: