Skip to content

queue-runner: release machine reservation while copying outputs #1469

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

Merged
merged 1 commit into from
Apr 7, 2025

Conversation

Ericson2314
Copy link
Member

This allows for better builder usage when the queue runner is busy. To avoid running into uncontrollable imbalances between builder/queue runner, we only release the machine reservation after the local throttler has found a slot to start copying the outputs for that build.

As opposed to asserting uniqueness to understand resource utilization, we just switch to using std::unique_ptr.

This allows for better builder usage when the queue runner is busy. To
avoid running into uncontrollable imbalances between builder/queue
runner, we only release the machine reservation after the local
throttler has found a slot to start copying the outputs for that build.

As opposed to asserting uniqueness to understand resource utilization,
we just switch to using `std::unique_ptr`.
@Ericson2314 Ericson2314 enabled auto-merge April 7, 2025 18:02
@Ericson2314
Copy link
Member Author

CC @Mic92 I combined @delroth's original and null pointer fix, and then reworked using std::unique_ptr to remove asserts (now statically known) and double indirections.

@Ericson2314 Ericson2314 added this pull request to the merge queue Apr 7, 2025
Merged via the queue into master with commit 8350f96 Apr 7, 2025
1 check passed
@Ericson2314 Ericson2314 deleted the release-reservations branch April 7, 2025 18:36
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.

2 participants