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

x/build: make GCE buildlet pool quota accounting smarter #10704

bradfitz opened this issue May 5, 2015 · 0 comments


Copy link

commented May 5, 2015

The GCE implementation of BuildletPool's quota accounting is way too dumb & conservative.

If it counted better, it could push our quota limits a lot harder.

In fact, it could push things as hard as possible until it hit limits, learn the limits, and then count from there.

Or it could poll quotas? (is there an API?)

Currently we have quota for 200 CPUs (and N RAM and disk, etc) but we limit ourselves to 60 builds at once, just because we haven't done the work to count how much of resource $X each build uses.

/cc @adg @crawshaw

@ianlancetaylor ianlancetaylor added this to the Unreleased milestone Jun 3, 2015
@rsc rsc added the Builders label Jun 11, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
3 participants
You can’t perform that action at this time.