A Trino engine is sized with one field: size. Picking a rung sets seven underlying values — worker count, coordinator and worker JVM heap, coordinator and worker CPU, and the cluster-wide and per-node query memory ceilings — together, so they stay coherent with each other. You don’t tune them individually unless you choose custom.

The ladder

Two settings are sized separately, because they’re behaviour choices rather than capacity: Spill to disk (spill intermediate results instead of failing a query that exceeds memory) and Spot workers (run workers on cheaper interruptible capacity, if your plane has it — a reclaimed worker fails whatever it was running; the coordinator always stays on-demand).

Which sizes your plan allows

Creating an engine without naming a size gives you s if your plan includes it, or the largest size below it your plan does include. If you don’t see a rung in the size picker, or a create is refused naming a size, that’s your tenant’s plan — see Entitlements and ask your platform administrator to change it. This size ladder is a separate gate from the managed_engines feature flag: your plan can allow every size up to xl while that flag is still off, in which case registering, waking or reconfiguring an engine is refused regardless of the size you asked for. See Entitlements: flags that gate acquiring, not holding.

custom

custom means the seven values above stop being derived from a rung and become the configuration themselves — you set each one directly. It’s Enterprise-only, is never a default, and you have to choose it explicitly. Once an engine is on custom, editing any one of the seven fields doesn’t change its size class; you’re editing the engine’s actual settings.

Changing an engine’s size

Open the engine and Edit, or use the CLI. Either way, a size change is staged, not applied immediately — it shows as Config pending on the engine until you click Apply, which restarts the engine and fails any query running on it at that moment. See Catalogs and Apply.
Resize an engine
To hand-configure the raw knobs instead of a rung:
Custom configuration

Create an engine

Field by field through the register form, including where size fits in.

Catalogs and Apply

Why a size change stays pending until you click Apply.