Describe the issue or suggestion
https://learn.microsoft.com/en-us/dotnet/core/deploying/single-file/overview?source=recommendations&tabs=cli#compress-assemblies-in-single-file-apps
I was absolutely shocked to discover that a single-file app I was using had a 350 MB private working set segment purely for decompressed R2R code. While the documentation does say there is a "startup overhead", this feels like an outrageous amount of difference that app developers might not be aware of.
I have not done measurements on this, but it does not seem unreasonable to guess that all the point of R2R is basically thrown away entirely by this system. Especially if users have slower disks or higher memory pressure.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
Describe the issue or suggestion
https://learn.microsoft.com/en-us/dotnet/core/deploying/single-file/overview?source=recommendations&tabs=cli#compress-assemblies-in-single-file-apps
I was absolutely shocked to discover that a single-file app I was using had a 350 MB private working set segment purely for decompressed R2R code. While the documentation does say there is a "startup overhead", this feels like an outrageous amount of difference that app developers might not be aware of.
I have not done measurements on this, but it does not seem unreasonable to guess that all the point of R2R is basically thrown away entirely by this system. Especially if users have slower disks or higher memory pressure.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.