Set org, space, and app limits
Org Managers are free to configure your org’s quota capacity among your spaces and applications as you see fit. This enables Org Managers to limit usage and corresponding costs.
See more about how to manage your orgs’ quotas.
Org Managers can create and modify space quota plans to limit the resources used by spaces. See the CF CLI documentation for
create-space-quota to create the quota plan, and create a space with that quota plan using
create-space (which has the option
Space Developers can specify application limits in your application manifest or as
cf push command line options.
Application limit options
memory: / -m
The application memory limit. This setting has a dual-purpose, as your application compute limit is derived from its memory limit. This relationship is explained in detail here.
disk_quota / -k
The maximum amount of disk space available to your app.
instances: / -i
Sets the number of application instances to launch. Each additional instance receives the same memory and disk reservation. An application with a manifest specifying
memory: 256M and
instances: 4 would reserve 1GB (256M x 4) total.
The application cannot access more than the specified amount of memory.
Application limit options: sizing
The environment default of 512MB
memory:is sufficient for most applications. Static sites and utility applications such as schedulers or loaders may require less. Use
cf app APPNAMEto check your application’s current memory and compute utilization.
requested state: started instances: 1/1 usage: 128M x 1 instances urls: last uploaded: Wed Jul 22 20:09:56 UTC 2015 state since cpu memory disk #0 running 2015-07-30 05:58:11 PM 0.0% 94.6M of 128M 80.4M of 128M
Any application which exceeds its memory limit will be automatically restarted. Use
cf events APPNAMEto look for ‘out of memory’ crashes.
... description ... index: 0, reason: CRASHED, exit_description: out of memory, exit_status: 255