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 how slaves are assigned builds. #19

Closed
wants to merge 1 commit into from

Conversation

dinatale2
Copy link
Contributor

It is preferable to assign a build to a slave who is
idle (already spun up and waiting) over a slave that has yet
to be started or a busy one. If there are no idle slaves,
and there is one that can be spun up, then spin one up.
Otherwise, randomly choose among our busy slaves.

Signed-off-by: Giuseppe Di Natale dinatale2@llnl.gov

It is preferable to assign a build to a slave who is
idle (already spun up and waiting) over a slave that has yet
to be started or a busy one. If there are no idle slaves,
and there is one that can be spun up, then spin one up.
Otherwise, randomly choose among our busy slaves.

Signed-off-by: Giuseppe Di Natale <dinatale2@llnl.gov>
@behlendorf
Copy link
Contributor

Nice, I see this change depends on isIdle() which is fine but be aware it's a function we've added to our slightly patched version of buildbot. This LGTM I'll see about rolling it out when the buildbot's next idle.

@behlendorf
Copy link
Contributor

Merged as:

ea3ffad Optimize how slaves are assigned builds.

@behlendorf behlendorf closed this Feb 4, 2016
@dinatale2 dinatale2 deleted the optimize_nextslave branch February 5, 2016 19:51
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.

None yet

2 participants