FerryDocs

Resource limits

A plan, or the keys memoryLimit and cpuLimit, set the memory limit and the CPU limit of each container.

Edit on GitHub
planmemoryLimitcpuLimitNo keyserver defaultsLimitsof each container

A plan gives a memory limit and, for a service, a CPU limit.

1 / 4

Each that Ferry runs gets a and a . This applies to each instance and each job run of a service, and to each datastore.

The keys

KeyTypeDefaultFerry setting and notes
planstringnoneThe instance type of Render. See Plans of a service and Plans of a datastore.
memoryLimitstring or integernonememory_limit_mb, a . It replaces the memory of the plan.
cpuLimitstring or numbernonecpu_limit, a Ferry key. It replaces the CPU of the plan.

An entry can have a plan, the two keys, or all three. See memoryLimit and cpuLimit.

The server defaults

The defaults come from ferryd --default-memory-limit and --default-cpu-limit. They are 512 and 1 CPU unless the operator changed them. With the value 0, there is no limit. See Server options.

Resource limits explains how Ferry applies the limits.

On this page