FerryDocs
ConceptsResource limits

Render plans

Ferry changes each Render plan into a memory limit and a CPU limit.

Edit on GitHub
render.yaml
services:
  - type: web
    name: api
    plan: standard        # 2 GiB / 1 CPU
databases:
  - name: app-db
    plan: basic-1gb       # 1 GiB of memory

A is a size name from Render. Ferry reads it in a .

Plans of a service

PlanMemoryCPU
free, starter512 MiB0.5 CPU
standard2 GiB1 CPU
pro4 GiB2 CPUs
pro plus8 GiB4 CPUs
pro max16 GiB4 CPUs
pro ultra32 GiB8 CPUs

These are the values of Render, with one exception. On Render, free has 0.1 CPU. On Ferry, it gets 0.5 CPU, because a tenth of a core only makes an app slow on your own server.

Plans of a datastore

The plan of a datastore sets only the memory.

DatastorePlanMemory
Postgres (databases)basic-256mb, basic-1gb, basic-4gb, pro-<size>, accelerated-<size>The size in the name: pro-16gb gives 16 GiB
Postgres, old plansfree, starter256 MiB
standard1 GiB
pro4 GiB
pro plus8 GiB
Key Value (type: redis or keyvalue)free, starter256 MiB
standard1 GiB
pro5 GiB
pro plus10 GiB

Limits in a blueprint

In a blueprint, a plan or the keys memoryLimit and cpuLimit set the limits.

The process limit

A container can have 1024 processes and threads at most.

On this page

Plans of a servicePlans of a datastore