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.

Sign up for GitHub

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

Jump to bottom

x/build: coordinator should keep a small pool of ready-to-go GCE buildlets #11107

Open
bradfitz opened this issue Jun 7, 2015 · 1 comment
Open

x/build: coordinator should keep a small pool of ready-to-go GCE buildlets #11107

bradfitz opened this issue Jun 7, 2015 · 1 comment
Labels
Builders x/build issues (builders, bots, dashboards) FeatureRequest Performance
Milestone
Unplanned

Comments

@bradfitz
Copy link
Contributor

bradfitz commented Jun 7, 2015

The coordinator's GCE buildlet pool should always have a few of each type of buildlet ready to go to avoid the start-up latency.

e.g. an idle Plan 9, OpenBSD 32/63, FreeBSD 64 (at least 2x), Linux (probably at least 4x), etc.

Then once we start building them, we also start spinning up the helpers for test sharding.

This will raises costs, but probably shouldn't be too bad. I'll post some math on the cost here later.

/cc @adg
@bradfitz bradfitz added this to the Unplanned milestone Jun 7, 2015
@rsc rsc added the Builders x/build issues (builders, bots, dashboards) label Jun 11, 2015
@bradfitz bradfitz mentioned this issue Dec 15, 2017
Closed
@bradfitz
Copy link
Contributor Author

Related bug that'd probably need to happen about the same time: #19178

@bradfitz bradfitz mentioned this issue Apr 26, 2018
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Builders x/build issues (builders, bots, dashboards) FeatureRequest Performance
Projects
None yet
Milestone
Unplanned
Development

No branches or pull requests
3 participants
@bradfitz @rsc @dmitshur