Repository navigation
.NET 7 RC1 blazor WASM size regression #44060
Description
Is there an existing issue for this?
- I have searched the existing issues
Describe the bug
I try to update .NET 6 prototype to .NET 7 RC1 and i notice significant size increase is that expected with .NET 7?
dotnet.wasm.br went from ~786.9 KiB to ~952.9 KiB
System.Private.CoreLib.dll.br 403.9 KiB -> 510.6 KiB
_framework/icudt_EFIGS.dat.br 145.7 KiB -> 194.6 KiB
Overall increase from 3,672 KiB -> 4,325 KiB
Also I notice that --blazor-load-percentage is added to HTML tag and it seems base on build in browser profiler that is cause "Recalculate style" several times during loading. This isnt issue when it is standard WASM app but with prerendering enable its add some delay (correct me if I am wrong).
Expected Behavior
I expect that new version of .NET improve both performance and size of the app.
Steps To Reproduce
No response
Exceptions (if any)
No response
.NET Version
7.0.100-rc.1.22431.12
Anything else?
No response
Activity
mkArtakMSFT commentedon Sep 19, 2022
Thanks for contacting us. There are two things involved here.
For the size regression that you mentioned, we are aware of an issue causing it and it's being worked on already: dotnet/sdk#27659
As for the load percentage, it is expected for the styles to be recalculated. We think 17ms is an acceptable time. If we get more customer feedback about this being an issue, we will consider doing something about it.
jirisykora83 commentedon Sep 19, 2022
Thank you for more information about size regression I glad it will be solved.
For style recalculations it is not 17ms it is 17ms for each time the property is updated what is in my (still "smaller" app 12x times).
Also that time is with last desktop i7 with older laptop its seems as it take 2x more (still with compounding of 12 calls during cold startup). And also with relatively small DOM (just ~280 elements). I expect it will be more for more common bigger page.
I am not frontend dev so I do not know if this is actually count as part of "Total Blocking Time" or "Time to Interactive".
this is from run on laptop (8550u). from that 270ms is about 200ms updating
--blazor-load-percentagewith small DOM and okish laptop for older phone it should be more in absolute term (in percentage still about ~5%).