-
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
Users benefit from faster runtime startup due to reductions in runtime startup overhead #44598
Comments
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. |
Consider the serverless functions scenarios as well; people still use cold startup perf to chose a particular language over the other. |
I measured PowerShell startup. It seems there are delays in hostpolicy on realpath() and GetFileAttributesExW(). |
All planned work for .NET 6 has been done here, with some nice improvements on startup. I'm going to close this; there can still be further opportunistic work for the release. |
.NET processes are spun up repeatedly as part of a developer's inner loop development process, including for the app itself being debugged. We want to drive down the overheads across all tools employed as part of inner loop, and that includes reducing runtime startup costs wherever possible.
Issues:
The text was updated successfully, but these errors were encountered: