Repository navigation
Question: Realistic workload capacity on Hetzner CPX31 tier #18
Description
This looks like a really 💯 interesting service — exactly what I’ve been looking for. I’m considering rolling out DevPush for my own projects and for some client sites as well.
I noticed you recommend the Hetzner CPX31 tier (4 vCPU / 8 GB RAM) for deployment. Do you have any insight into what kind of workload that configuration can realistically handle? For example, how many active containers or typical web apps can it run comfortably before resource limits become an issue? Is performance usually constrained by RAM, CPU, or something else in your experience?
Thanks for the great work — really enjoying exploring the project so far!
Activity
hunvreus commentedon Dec 9, 2025
It's hard to tell honestly, it depends on how much load you intend to have from each app. It depends as well how your app is built and whether or not you're using a CDN.
lemmon commentedon Dec 17, 2025
Agreed, it definitely depends on the workload and traffic patterns. My understanding though is that even mostly idle containers still consume some baseline resources (memory, a bit of CPU for the runtime, networking, etc.), so there’s always a practical upper bound even with low-traffic apps.
Roughly speaking, if an app container idles at e.g. ~50–150 MB RAM, that already puts some limits on how many apps comfortably fit on an 8 GB machine before accounting for bursts, Postgres, Redis, Traefik, etc.
I was mostly curious whether the CPX31 recommendation is based on any internal benchmarks, rough heuristics, or real-world experience, or if it’s just a “safe default” starting point.