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
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
The text was updated successfully, but these errors were encountered:
Related bug that'd probably need to happen about the same time: #19178
Sorry, something went wrong.
No branches or pull requests
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
The text was updated successfully, but these errors were encountered: