Skip to content

Users benefit from faster runtime startup due to reductions in runtime startup overhead #44598

Closed

Description

@stephentoub

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

Activity

  1. added
    User StoryA single user-facing feature. Can be grouped under an epic.
    Priority:1Work that is critical for the release, but we could probably ship without
    Cost:MWork that requires one engineer up to 2 weeks
    on Nov 12, 2020
  2. added this to the 6.0.0 milestone on Nov 12, 2020
  3. self-assigned this
    on Nov 12, 2020
  4. Dotnet-GitSync-Bot commented on Nov 12, 2020

    @Dotnet-GitSync-Bot
    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.

  5. iSazonov commented on Nov 26, 2020

    @iSazonov
    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

  6. jkotas commented on Nov 26, 2020

    @jkotas
    Member

    @iSazonov This is tracked by #44545

  7. removed
    untriagedNew issue has not been triaged by the area owner
    on Nov 27, 2020
  8. 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[/+] on Nov 29, 2020
  9. stephentoub commented on Jul 6, 2021

    @stephentoub
    MemberAuthor

    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.

  10. ghost locked as resolved and limited conversation to collaborators on Aug 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Cost:MWork that requires one engineer up to 2 weeksPriority:1Work that is critical for the release, but we could probably ship withoutTeam:RuntimeUser StoryA single user-facing feature. Can be grouped under an epic.area-Metatenet-performancePerformance related issue

Type

No type

Projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions