Last updated 18th May 2021
Objective
By default, Web PaaS will automatically select appropriate resource sizes (CPU and memory) for a container when it's deployed, based on the plan size and the number of other containers in the cluster. The more containers in a project the fewer resources each one gets, and vice versa, with similar containers getting similar resources.
These are advanced settings and should only be used by experienced Web PaaS users. 99.9% of the time our default container sizes are the correct choice for best performance.
Usually that's fine, but sometimes it's undesirable. You may, for instance, want to have a queue worker container that you know has low memory and CPU needs, so it's helpful to give that one fewer resources and another container more. Or a given service may be very heavily used in your architecture so it needs all the resources it can take. In those cases you can provide sizing hints to the system on a per-service basis.
Every application container as well as every service in .platform/services.yaml supports a size key, which instructs the system how many resources to allocate to it. The exact CPU and memory allocated will depend on the application or service type, and we may adjust these values over time to better optimize resource usage.
If the total resources requested by all apps and services is larger than what the plan size allows then a production deployment will fail with an error.
How do I make a background processing container smaller to save resources?
Simply set the size key to S to ensure that the container gets fewer resources, leaving more to be allocated to other containers.
name: processing
type: nodejs:14
size: S
...
Did you find this guide useful?
Please feel free to give any suggestions in order to improve this documentation.
Whether your feedback is about images, content, or structure, please share it, so that we can improve it together.
Your support requests will not be processed via this form. To do this, please use the "Create a ticket" form.
Thank you. Your feedback has been received.