When configuring servers for client apps and high-traffic APIs, cloud infrastructure choice directly dictates your tail latency and monthly hosting bills.
To find out which VPS provider delivers the highest throughput with zero CPU throttling, we ran standardized synthetic benchmarks using wrk2 generating sustained load over HTTP/3.
Test Methodology
All three testing environments were provisioned identically using Rubuz with rootless containers:
- Hetzner Cloud: CPX31 (4 vCPU AMD EPYC, 8 GB RAM) — €14.50/month
- DigitalOcean: Premium AMD Droplet (4 vCPU, 8 GB RAM) — $48.00/month
- AWS EC2: t4g.xlarge (4 vCPU ARM Graviton2, 16 GB RAM) — ~$96.00/month
Latency Under Load (99th Percentile)
Under a sustained barrage of 15,000 requests per second with keep-alive connections:
| Provider | Median Latency (p50) | 99th Percentile (p99) | Cost per 10k Req |
|---|---|---|---|
| Hetzner CPX31 | 14.2 ms | 31.8 ms | €0.0003 |
| AWS t4g.xlarge | 18.6 ms | 44.1 ms | $0.0021 |
| DigitalOcean Premium | 22.4 ms | 58.7 ms | $0.0011 |
Key Findings
- Bare-metal AMD EPYC performance: Hetzner’s dedicated AMD cores consistently delivered the lowest jitter and highest single-core burst throughput.
- Bandwidth Costs: AWS egress data transfer charges can quickly dwarf your base server compute invoice, whereas Hetzner bundles 20 TB of free outbound traffic per month.
- Rootless Containers: On all three providers, containerization added 0.0% CPU overhead compared to running natively on the host kernel.
Effortless Hetzner Cloud Management with Rubuz
While Hetzner consistently wins raw compute price-to-performance benchmarks, managing unmanaged Linux servers from the command line can be time-consuming. Rubuz connects over standard SSH, turning any Hetzner Cloud VPS or Robot server into a private PaaS with automated 1-click app deployments, wildcard SSL, automated S3/Storage Box backups, and zero agent overhead.
👉 Learn more about managing Hetzner Cloud servers with Rubuz or start deploying with git push.