Limits in a blueprint

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

render.yaml

services:
  - type: web
    name: api
    plan: standard        # 2 GiB / 1 CPU
    cpuLimit: 500m        # but only half a core

The plan gives a memory limit and a CPU limit.

1 / 2

A blueprint is a render.yaml or a ferry.yaml file. The plan of a service or a database becomes its limits. See Render plans.

memoryLimit and cpuLimit are keys of Ferry. Each key replaces one value of the plan.

See the changes first

A dry run lists the changes of limits.

ferry blueprint apply render.yaml --dry-run

Blueprint render.yaml — dry run, nothing was changed

Would update:
  ~ service api
      - memory_limit: (server default) → 2 GiB
      - cpu_limit: (server default) → 1 CPU

Run without --dry-run to apply.

The apply restarts each live service whose limits change. It changes the limits of a datastore in place.

Server defaults

A service or a datastore with no limit of its own gets the defaults of the server.

Render plans

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

Limits in a blueprint

See the changes firstCopy Anchor Link

The rules of the keys

All the keys

On this page

See the changes first