---
uaa_instances: 3
nats_instances: 3
diego_api_instances: 3
cell_instances: 105
router_instances: 15
api_instances: 12
doppler_instances: 54
log_api_instances: 27
scheduler_instances: 4
cc_worker_instances: 4
cc_hourly_rate_limit: 20000
cc_staging_timeout_in_seconds: 2700
paas_region_name: london

prometheus_disk_size: 750GB
prometheus_retention_size: 700GB

---
uaa_instances: 3
nats_instances: 3
diego_api_instances: 3
cell_instances: 105
router_instances: 15
api_instances: 12
doppler_instances: 54
log_api_instances: 27
scheduler_instances: 6
cc_worker_instances: 6
cc_hourly_rate_limit: 20000
cc_staging_timeout_in_seconds: 2700
paas_region_name: london

prometheus_disk_size: 750GB
prometheus_retention_size: 700GB

Increase number of CC workers
Increase number of CC workers

We'd like to eliminate the flakyness of the tests, by throwing more
resource at the system, hopefully handling more actions, more promptly.

This is a finger in the air change, that should be small enough but may
be informative to our investigation into flaky smoke tests.
