FerryDocs
Concepts

Resource limits

Each container has a limit of memory and CPU. One bad app cannot stop your server.

Edit on GitHub
Limit: 512 MiB, 1 CPUApp120 MiBDatabaseferryd

An app, a database and ferryd run on the same server.

1 / 4

A is the most memory and CPU that one can use. Ferry puts limits on each container that it starts: instances, one-off jobs, cron runs and datastores.

An app with a bug gets slower or stops. It cannot stop the server, ferryd or your databases.

Set a limit

Terminal
ferry update api --memory 2G
ferry restart api --follow

In this section

The five guardsMemory, CPU, processes, logs and free disk space.The memory limitA box that the container cannot grow out of.Out-of-memory killsSee that an app had no memory left, and repair it.Set the limits of a serviceWith the CLI, the dashboard, the API or a blueprint.

Restart to apply changes

A restart is a new deploy of the live image with the current settings and variables.

The five guards

Five guards stop a container that uses too much of the server.

On this page

Set a limitIn this section