As per TAS 10.2 Release Notes, the memory footprint of Cloud Controller is calculated as follows -
Memory Footprint - Each process loads a full copy of the Cloud Controller application code into its own memory space and does not share memory with other workers.
How do we calculate how many MB/GB the CC application code will be?
For the memory footprint, it's recommendation to check each individual enviroment when doing this estimation.
The metrics vitals.mem_bytes / cc_vitals_mem_bytes metrics is best suited for this calculation.
See: https://docs.cloudfoundry.org/running/all_metrics.html#cc
| cc_vitals_mem_bytes |
The RSS bytes (resident set size) or real memory of the Cloud Controller process. Emitted every 30 seconds per VM. |
Alternatively check monit status if you are SSH'd in to the control VM.
Example:
cloud_controller/#####-######:/# sudo -i monit status
Process 'cloud_controller_ng'
status running
children 1
memory kilobytes 984
memory kilobytes total 233084
memory percent 0.0%
memory percent total 2.8%
cpu percent 0.0%
cpu percent total 0.4%
data collected Wed Mar 4 23:19:06 2026
Process 'cloud_controller_worker_local_1'
status running
children 1
memory kilobytes 964
memory kilobytes total 174916
memory percent 0.0%
memory percent total 2.1%
cpu percent 0.0%
cpu percent total 0.0%
data collected Wed Mar 4 23:19:06 2026