I'm parked on you

Pick an option on each card and press Done; your answer goes straight back to the session. The raiser's pick is marked. "I'm not sure" is a real answer.

1CI runners hit the AWS 320 vCPU on-demand cap; raise it or cap CI concurrency?

In plain terms. CI is launching more machines than AWS lets us run at once. Should we pay for a bigger limit, or make CI wait in line?

Request quota 320→640 Cap concurrent CI shards, no quota changethe raiser's pick I'm not sure — go find out

Why, and what was tried

The session raising this recommends: Cap concurrent CI shards, no quota change
The burst is real (86 fresh on-demand runners in the last hour, no leaked machines), but a higher cap raises the spend ceiling, and spend increases need a human yes. Capping keeps cost flat; runs just queue longer.
Tried first, unsuccessfully: Tried: checked quota (320 on-demand, 1024 spot), counted live runners (266 on-demand vCPUs, all launched today, none orphaned).

0d7db998 is parked on this.

Pick an option above, then press Done.