User Story: WebAssembly developers want smaller published output to speed up their apps load time #44317
Labels
area-Meta
Cost:L
Work that requires one engineer up to 4 weeks
needs-further-triage
Issue has been initially triaged, but needs deeper consideration or reconsideration
Priority:1
Work that is critical for the release, but we could probably ship without
size-reduction
Issues impacting final app size primary for size sensitive workloads
User Story
A single user-facing feature. Can be grouped under an epic.
Milestone
In the .NET 5 release, we established a baseline of 2.2 MB for the fully compressed output of the default Blazor template running with .NET Core setup. For .NET 6 version, we are aiming to reduce that size by at least 20% for the same template to address size regression compare to .NET Core 3.x where the default template size was 1.7 MB. This is an ambitious goal, and will likely require numerous aggressive approaches to achieve it, including the removal of numerous non-essential features.
The only concern here is the wire size with full compression (at the moment, Brotli). The size or the required computation on either end is unimportant.
There is a dashboard available for historical size tracking at https://aka.ms/dotnetperfstatus. The case we care about is file type
.br
,.NET 6
. Of particular note is the currently largest files: dotnet.wasm at 0.9 MB, System.Private.CoreLib.dll at 0.4 MB, and icudt.dat at 0.3 MB. No other file is above 0.1 MB, but combined they are around 0.6 MB.Work Items
Add option to disable logging in sample Blazor app Add option to disable logging in sample Blazor app aspnetcore#27721The text was updated successfully, but these errors were encountered: