-
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
[release/8.0][wasm] Fix regressed file sizes for blazor #92627
Conversation
.. so that can work even if they get 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 ```
Tagging subscribers to 'arch-wasm': @lewing Issue Details
|
/azp run runtime-wasm |
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
This is size change bit suspicious, because your changes should have no way how to influence that. Edit: oh, your table heading actually said rc1 |
Yeah, it's not comparing exactly the same base commit, because we don't have any runs for 8.0 or 8.0-rc2 branches, so I have to compare against the last run that we have from rc1. Essentially, the difference is that we don't pass |
I can do a manual run on the current HEAD, and then we could compare. |
@pavelsavara @lewing I have updated the results. |
@pavelsavara good catch, I fixed the percentages now. |
@carlossanlop this is ready for merge. |
[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.
Changed sizes for the
minimum blazor template - publish
scenario:Customer impact
Improved download size for the blazor app.
Testing
Sizes confirmed with a
dotnet-runtime-perf
run forblazor_scenarios
. Correctness verified by unit tests.Risk
Low. This is reverting to older behavior to change the symbols being included in the output.
Details
Issue: dotnet/perf-autofiling-issues#20642