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

optimize windows service startup #1806

Merged
merged 3 commits into from
Jul 29, 2024
Merged

Conversation

zackattack01
Copy link
Contributor

See inline comments for additional technical context

We are seeing issues with windows devices timing out before launcher is able to start in certain environments. This typically coincides with significant resource contention/high activity during boot up. One bit of logic that stood out as possibly dragging things out is our registry and service manager interactions (to perform runtime service configuration).

Moving these checks into the Execute function, after our Running status update should help to make startup faster, or at least more responsive to service control manager

Copy link
Contributor

@directionless directionless left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice. As separate work, is it interesting to add spans or timing data to this critical section?

@zackattack01
Copy link
Contributor Author

regarding the spans - I will check that out next!

@zackattack01 zackattack01 added this pull request to the merge queue Jul 29, 2024
Merged via the queue into main with commit b58122e Jul 29, 2024
29 checks passed
@zackattack01 zackattack01 deleted the zack/optimize_windows_startup branch July 29, 2024 13:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants