Skip to content
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

Closed
30 of 36 tasks
Tracked by #5876
stephentoub opened this issue Nov 12, 2020 · 5 comments
Closed
30 of 36 tasks
Tracked by #5876
Assignees
Labels
area-Meta Cost:M Work that requires one engineer up to 2 weeks Priority:1 Work that is critical for the release, but we could probably ship without Team:Runtime tenet-performance Performance related issue User Story A single user-facing feature. Can be grouped under an epic.
Milestone

Comments

@stephentoub
Copy link
Member

stephentoub commented Nov 12, 2020

.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:

@stephentoub stephentoub added tenet-performance Performance related issue User Story A single user-facing feature. Can be grouped under an epic. Priority:1 Work that is critical for the release, but we could probably ship without Cost:M Work that requires one engineer up to 2 weeks labels Nov 12, 2020
@stephentoub stephentoub added this to the 6.0.0 milestone Nov 12, 2020
@stephentoub stephentoub self-assigned this Nov 12, 2020
@Dotnet-GitSync-Bot
Copy link
Collaborator

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.

@ghost
Copy link

ghost commented Nov 14, 2020

Consider the serverless functions scenarios as well; people still use cold startup perf to chose a particular language over the other.

@iSazonov
Copy link
Contributor

I measured PowerShell startup. It seems there are delays in hostpolicy on realpath() and GetFileAttributesExW().
I hope performance improvements could be made there. (Is it really necessary to check for the existence of files?)
PerfView trace https://ru.files.fm/u/n2hqqsr7z
image
image

@jkotas
Copy link
Member

jkotas commented Nov 26, 2020

@iSazonov This is tracked by #44545

@marek-safar marek-safar removed the untriaged New issue has not been triaged by the area owner label Nov 27, 2020
@danmoseley danmoseley changed the title Reduce the overhead incurred when starting up the runtime Users benefit from faster runtime startup due to reductions in runtime startup overhead Nov 29, 2020
@stephentoub
Copy link
Member Author

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.

@ghost ghost locked as resolved and limited conversation to collaborators Aug 20, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-Meta Cost:M Work that requires one engineer up to 2 weeks Priority:1 Work that is critical for the release, but we could probably ship without Team:Runtime tenet-performance Performance related issue User Story A single user-facing feature. Can be grouped under an epic.
Projects
No open projects
Development

No branches or pull requests

6 participants