-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
[wasm] Fix regressed file sizes for blazor #92664
Conversation
.. so that can work even if it gets renamed during minimization.
The earlier change was done in 678fd6a, which changed to pass `-g` to the link step also. But that resulted in increased native file sizes. Changed sizes for the `minimum blazor template - publish` scenario: ``` | Last rc1 run | With the change ----------------------------------------------------------|----------------- |------------------ SOD - Minimum Blazor Template - Publish |8590723.000 bytes |7889806.000 bytes Total Uncompressed _framework |4304274.000 bytes |4202273.000 bytes pub/wwwroot/_framework/dotnet.js |35722.000 bytes |35838.000 bytes pub/wwwroot/_framework/dotnet.native.8.0.0-VERSION.js |239307.000 bytes |134566.000 bytes pub/wwwroot/_framework/dotnet.native.wasm |1174394.000 bytes |1148841.000 bytes pub/wwwroot/_framework/dotnet.runtime.8.0.0-VERSION.js |221356.000 bytes |221712.000 bytes ``` (cherry picked from commit ae93e81)
(cherry picked from commit 0207d60)
(cherry picked from commit 91379dd)
Tagging subscribers to 'arch-wasm': @lewing Issue Details
|
/azp run runtime-wasm-perf |
Azure Pipelines successfully started running 1 pipeline(s). |
After the change to move
log. |
I guess I put it in both places because it was actually necessary, and I forgot :-) |
This reverts commit 68e954d. This caused tests to fail with: ``` fail: [out of order message from the browser]: http://127.0.0.1:36071/_framework/dotnet.runtime.js 2:12344 "MONO_WASM: onRuntimeInitializedAsync() failed" TypeError: t.getWasmIndirectFunctionTable is not a function at br (http://127.0.0.1:36071/_framework/dotnet.runtime.js:3:55253) at zr (http://127.0.0.1:36071/_framework/dotnet.runtime.js:3:60544) at http://127.0.0.1:36071/_framework/dotnet.runtime.js:3:214955 fail: [out of order message from the browser]: http://127.0.0.1:36071/_framework/dotnet.js 2:917 "MONO_WASM: TypeError: t.getWasmIndirectFunctionTable is not a function\n at br (http://127.0.0.1:36071/_framework/dotnet.runtime.js:3:55253)\n at zr (http://127.0.0.1:36071/_framework/dotnet.runtime.js:3:60544)\n at http://127.0.0.1:36071/_framework/dotnet.runtime.js:3:214955" ```
need help ? |
Any suggestions on a fix? The alternative would be to disable the failing tests which are essentially for Debug+AOT, and Debug+relink. We could ignore But this PR will help the sizes. |
Still this, right ?
|
Yes |
I have this untested theory: I think this is not about AOT, but about It fails in We have this un-mangling logic in |
Printing full list of |
Relink/aot with an optimization level and -g . This happens only for debug config. Dunno about the details that you mentioned. |
#95613 seems to have fixed the failures! Thanks @kg, @pavelsavara! |
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
@microsoft-github-policy-service rerun |
Failures are known issues. |
@microsoft-github-policy-service rerun |
@dotnet-github-policy-service rerun |
@dotnet-policy-service rerun |
Blazor size regression was fixed by: ``` commit ec31705 Author: Ankit Jain <[email protected]> Date: Wed Dec 6 05:36:59 2023 -0500 [wasm] Fix regressed file sizes for blazor (dotnet#92664) ``` .. but a subsequent PR created close to that undid some of the changes: ``` commit a128c15 Author: Ankit Jain <[email protected]> Date: Mon Dec 11 15:45:58 2023 -0500 [wasm/wasi] Consolidate build targets (dotnet#95775) ``` Essentially, `-g` was being passed to the link, and compile-bc steps. Found in dotnet/perf-autofiling-issues#25891 .
* [wasm/wasi] Fix size regression Blazor size regression was fixed by: ``` commit ec31705 Author: Ankit Jain <[email protected]> Date: Wed Dec 6 05:36:59 2023 -0500 [wasm] Fix regressed file sizes for blazor (#92664) ``` .. but a subsequent PR created close to that undid some of the changes: ``` commit a128c15 Author: Ankit Jain <[email protected]> Date: Mon Dec 11 15:45:58 2023 -0500 [wasm/wasi] Consolidate build targets (#95775) ``` Essentially, `-g` was being passed to the link, and compile-bc steps. Found in dotnet/perf-autofiling-issues#25891 . * [wasm] Add flag missed in the consolidate PR
[wasm] build: Revert to older behavior for WasmNativeStrip
The earlier change was done in 26ae097,
which changed to pass
-g
to the link step also. But that resulted inincreased native file sizes.
Issue: Issue: dotnet/perf-autofiling-issues#20642