-
Notifications
You must be signed in to change notification settings - Fork 5.2k
[release/6.0][wasm] Change dotnet.wasm link optimization #60632
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
[release/6.0][wasm] Change dotnet.wasm link optimization #60632
Conversation
Context: dotnet#60349 When we switched to Emscripten 2.0.21, we stopped using deprecated `--llvm-opts 2` option. This caused unwanted performance degradation. Switching to `-O2` get us similar performance as with `--llvm-opts`. Blazor wasm test app `Time to first UI` benchmark times: branch/commit link option time dotnet.wasm size --------------------+------------+--------+----------------- release/6.0 92ff02 -Oz 491ms 2,430,639 release/6.0 92ff02 -O2 457ms 2,474,518 release/6.0 92ff02 -O3 444ms 2,555,824
|
we're going to let this bake for a bit before we take it in servicing |
|
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsContext: #60349 When we switched to Emscripten 2.0.21, we stopped using deprecated Blazor wasm test app
|
|
@marek-safar @radical can you review this one ? |
radical
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. but I would also wait for an approval from @lewing
Context: #60349
When we switched to Emscripten 2.0.21, we stopped using deprecated
--llvm-opts 2option. This caused unwanted performance degradation.Switching to
-O2get us similar performance as with--llvm-opts.Blazor wasm test app
Time to first UIbenchmark times:Customer Impact
Fixes a startup time regression for blazorwasm between .NET 5 an .NET 6 by a reverting compiler option change that was accidentally introduced as part of other build changes.
Testing
Manual and Automated
Regression
Yes, startup time regression.
Risk
Low, switch to compiler options we're using in main.