Pod Sizes

Watasu’s process pods come in T-shirt sizes from hobby to standard-16x. Each standard step doubles CPU and memory.

Available sizes

Size	CPU	Memory	Notes
hobby	up to 1 (0.25 guaranteed)	1 GB	Max 1 replica. Prototypes and review apps.
standard-1x	1	2 GB	Baseline — small web/worker workloads
standard-2x	2	4 GB	Medium web traffic, modest workers
standard-4x	4	8 GB	Heavy web, memory-bound workers
standard-8x	8	15 GB	Large in-memory workloads, image processing
standard-16x	16	30 GB	Heavy lifters

The dashboard shows current per-size pricing. Use watasu pods --app <app> to see what your processes are running on right now.

Pick a size

watasu pods:type web=standard-2x worker=standard-1x --app my-app

Each process type gets its own size — they’re independent.

Scale up vs. scale out

Two questions decide which lever to pull:

“Is one process running out of CPU or memory?” → Scale up (bigger pod). Indicators:

• OOMKilled events
• one process pegged at high CPU while others are idle
• a single hot path that won’t parallelize

“Are concurrent requests piling up?” → Scale out (more replicas). Indicators:

• request queue depth growing
• response time degrading at high load even though no single request is slow
• needing redundancy for HA

You can do both. A common production formation:

watasu pods:scale web=3 worker=2 --app my-app
watasu pods:type web=standard-2x worker=standard-1x --app my-app

Remember hobby is capped at one replica — switch to a standard-* size before scaling out.

Limits

If a pods:scale or pods:type command is refused, the dashboard tells you which limit you’ve hit and what to do about it. See Billing and Limits.