2 ms·
One of the reasons we didn't go with buildjet was their concurrency limits (https://buildjet.com/for-github-actions/docs/about/pricing#concurrency-limits https:
by public_void 3y ago
One of the reasons we didn't go with buildjet was their concurrency limits (https://buildjet.com/for-github-actions/docs/about/pricing#concurrency-limits https://buildjet.com/for-github-actions/docs/about/pricing#c...) and the pricing on extending those limits.
We are a small company but our autoscaling cluster for GitHub actions on aws will scale up to >500vcpus during the work day when there are a lot of prs going in.
I don't see it documented anywhere, what are your concurrency limits on accounts?
- suryao 3y agoWe don't enforce concurrency limits. It is not something that we want our users to think about. I'd hate to worry about it too. In general, we should be able to deal with spiky workloads of that scale without issue in a couple of minutes. I'd love for you to try us out.