Open performanceautofiler[bot] opened 2 years ago
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.
Tagging subscribers to 'arch-wasm': @lewing See info in area-owners.md if you want to be subscribed.
Author: | performanceautofiler[bot] |
---|---|
Assignees: | lewing |
Labels: | `arch-wasm`, `tenet-performance`, `untriaged` |
Milestone: | - |
/ cc @radical
Tagging subscribers to 'size-reduction': @eerhardt, @SamMonoRT, @marek-safar See info in area-owners.md if you want to be subscribed.
Author: | performanceautofiler[bot] |
---|---|
Assignees: | lewing |
Labels: | `arch-wasm`, `tenet-performance`, `area-Codegen-AOT-mono`, `size-reduction` |
Milestone: | 6.0.0 |
cc @tarekgh - seems like your change https://github.com/dotnet/runtime/pull/57078 is in the diff range for when the size regression was observed.
@radical is looking into this other PR https://github.com/dotnet/runtime/pull/57113 ruling out any build issue.
My change is just depending on a couple of ICU APIs which we didn't use before. I am not sure why using such ICU APIs cause that big regression. @lewing can we get more info about that. The new ICU APIs I used shouldn't be that big to cause such regression.
@tarekgh referencing new symbols tends to pull in a surprising amount of new code. What sort of information would be helpful?
Talked offline with @lewing and will wait his reply about the size increase investigation to decide about the next step here.
Run Information
Regressions in SOD - Pizza App - Publish
Repro
Run Information
Regressions in SOD - New Blazor Template - Publish
Repro