---
uaa_instances: 3
nats_instances: 3
diego_api_instances: 3
cell_instances: 138
router_instances: 15
api_instances: 12
doppler_instances: 69
log_api_instances: 36
scheduler_instances: 10
cc_worker_instances: 10
cc_hourly_rate_limit: 60000
cc_staging_timeout_in_seconds: 2700
cc_maximum_health_check_timeout_in_seconds: 300
paas_region_name: london

prometheus_disk_size: 750GB
prometheus_retention_size: 700GB

---
uaa_instances: 3
nats_instances: 3
diego_api_instances: 3
cell_instances: 138
router_instances: 15
api_instances: 15
doppler_instances: 69
log_api_instances: 36
scheduler_instances: 10
cc_worker_instances: 10
cc_hourly_rate_limit: 60000
cc_staging_timeout_in_seconds: 2700
cc_maximum_health_check_timeout_in_seconds: 300
paas_region_name: london

prometheus_disk_size: 750GB
prometheus_retention_size: 700GB

Increase the number of API instances in London
Increase the number of API instances in London

Tenants are reporting CC instance scheduling failures.
API machines have 2 VCPUs and we see load exceeding 2 on some of the
instances.
