Scaling & resources
Resources
Section titled “Resources”Pick how much your service gets when you create it — change later from the dashboard.
| Resource | Range | Default |
|---|---|---|
| CPU | 0.1 – 2.0 cores | 0.5 |
| Memory | 64 – 1024 MB | 256 |
| Disk | 1 – 1000 GB | disabled |
If your app holds state on disk (uploads, SQLite, caches), enable persistent storage and set a mount path — the disk is preserved across restarts and redeploys.
Autoscaling
Section titled “Autoscaling”Autoscaling on Runsite is horizontal — more instances of the same container, not bigger ones. Set a min and max number of instances; Runsite watches CPU and memory and adjusts in between.
- Idle traffic runs at
mininstances. - When average CPU stays above ~80% or memory above ~85%, more instances are added — never above
max. - When load drops, instances are removed back down to
min.
Configure it in Settings → Scaling. To change the size of each instance instead, edit CPU and Memory above — that’s the vertical lever.
Sleep on idle
Section titled “Sleep on idle”A service can be set to sleep after a period without traffic. The next incoming request wakes it back up — usually under a second. Great for low-traffic services and preview environments.
Sleeping is transparent to clients: they just see a slightly slower first request after the wake-up. While asleep the service shows status SLEEPING — see Runtime → Deploy states.