Identify peak demands periods for limited resources (specific Chrome OS devices)
Establish underlying reasons for peak demand periods
Identify algorithm/config changes possible to alleviate resource capacity pressures
Drive CQ test planning rule definition and Quota Scheduler config changes
Drive device procurement decisions that will help alleviate some of the capacity bottlenecks
Provide clear guidance on what devices/quantities could be purchases to better support Parallel CQ
Predict the builder fleet capacity needs based on the CL submission rate
Use this to scale the initial build fleet to support initial Parallel CQ launch


Starter design: go/cros-pcq-capacity-analysis