Hetzner CPX11
Hillsboro, OR
Server
-
ProviderHetzner
-
PlanCPX11
-
LocationHillsboro, OR
-
vCPU2
-
RAM2 GB
-
Storage40 GB NVMe
-
NetworkUnknown
-
OS imageubuntu-24.04
-
TriggerScheduled
-
Queued atOct 12, 2026, 08:53:00 UTC
CPU
| Version | Single-core | Multi-core | Result link |
|---|---|---|---|
| Geekbench 7 | 1,382 | Skipped | Geekbench Browser |
Multi-core was skipped because Geekbench 7 needs about 3.1 GB of free memory to run 2 threads, and this server didn't have that much. Single-core needs much less, so it still ran.
Scores from different Geekbench versions aren't comparable with each other. Charts only use Geekbench 7.
Geekbench 7 workloads
| Workload | Single-core | Multi-core |
|---|---|---|
| File Compression |
1,427
|
Single-core only |
| Navigation |
1,396
|
Single-core only |
| HTML5 Browser |
1,267
|
Single-core only |
| PDF Viewer |
1,468
|
Single-core only |
| Photo Library |
1,299
|
Single-core only |
| Clang |
1,109
|
Single-core only |
| Text Processing |
1,217
|
Single-core only |
| Asset Compression |
1,396
|
Single-core only |
| HDR |
1,402
|
Single-core only |
| Photo Editor |
1,677
|
Single-core only |
| Ray Tracer |
1,358
|
Single-core only |
| Structure from Motion |
1,698
|
Single-core only |
| Game Physics |
1,285
|
Single-core only |
| Video Encoder |
1,296
|
Single-core only |
| Audio Encoder |
1,465
|
Single-core only |
| Video Player |
1,470
|
Single-core only |
Rank among the 129 runs with Geekbench 7 workload scores. Bars are relative to the best run. Geekbench doesn't run every workload multi-core, so some rows only have a single-core score.
Memory, TLS and scheduler
Memory bandwidth (STREAM)
| Test | Result | Runs | Spread |
|---|---|---|---|
| Copy higher is better | 59.4 GB/s | 3 | 20.3% |
| Scale higher is better | 40.2 GB/s | 3 | 17.9% |
| Add higher is better | 43.8 GB/s | 3 | 19.3% |
| Triad higher is better | 46 GB/s | 3 | 22% |
Average of 3 runs. Spread is the standard deviation as a share of the average.
TLS and crypto (OpenSSL)
| Test | Result | Runs | Spread |
|---|---|---|---|
| RSA 4096 signs higher is better | 425/s | 3 | 0.239% |
| RSA 4096 verifies higher is better | 28,194/s | 3 | 1.78% |
| SHA-256 higher is better | 1.61 GB/s | 3 | 0.516% |
| AES-256-GCM higher is better | 7.6 GB/s | 3 | 0.876% |
| ChaCha20-Poly1305 higher is better | 4.28 GB/s | 3 | 0.188% |
Average of 3 runs. Spread is the standard deviation as a share of the average.
Scheduler latency (schbench)
| Test | Result | Runs | Spread |
|---|---|---|---|
| Request latency, median lower is better | 4.65 ms | 3 | 0.199% |
| Requests per second, 90th percentile higher is better | 422/s | 3 | 0.362% |
| Request latency, 99.9th percentile lower is better | 9.1 ms | 3 | 14.9% |
| Requests per second, average higher is better | 416/s | 3 | 0.505% |
Average of 3 runs. Spread is the standard deviation as a share of the average.
Disk
| Block size | Read | Write | Total |
|---|---|---|---|
| 4K | 113.6 MB/s (29,085 IOPS) | 113.9 MB/s (29,162 IOPS) | 227.5 MB/s (58,247 IOPS) |
| 64K | 988.2 MB/s (15,811 IOPS) | 993.4 MB/s (15,894 IOPS) | 1.94 GB/s (31,705 IOPS) |
| 512K | 1.52 GB/s (3,117 IOPS) | 1.6 GB/s (3,282 IOPS) | 3.13 GB/s (6,399 IOPS) |
| 1M | 1.74 GB/s (1,780 IOPS) | 1.85 GB/s (1,899 IOPS) | 3.59 GB/s (3,679 IOPS) |
fio random read and write, 50/50, run by YABS against the boot disk.
Network
IPv4 transfer speed
| Target | Protocol | Send | Receive |
|---|---|---|---|
| Clouvider, London, UK (10G) | IPv4 | 1.17 Gbps | 1.4 Gbps |
| Eranium, Amsterdam, NL (100G) | IPv4 | 1.36 Gbps | 1.4 Gbps |
| Leaseweb, Singapore, SG (10G) | IPv4 | 881 Mbps | 1.29 Gbps |
| Clouvider, Los Angeles, CA, US (10G) | IPv4 | 4.49 Gbps | 7.69 Gbps |
| Leaseweb, NYC, NY, US (10G) | IPv4 | 2.6 Gbps | 3.33 Gbps |
Public iperf3 servers vary in capacity and availability. Compare a target only with itself over time.
Datastores
PostgreSQL
fsync speed (pg_test_fsync)
| Method | Operations per second | Time per operation |
|---|---|---|
| One 8 kB write | ||
| open_datasync | 4,274 | 0.234 ms |
| fdatasync | 3,816 | 0.262 ms |
| fsync | 2,267 | 0.441 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 2,555 | 0.391 ms |
| Two 8 kB writes | ||
| open_datasync | 2,082 | 0.48 ms |
| fdatasync | 3,928 | 0.255 ms |
| fsync | 2,500 | 0.4 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 1,271 | 0.787 ms |
| open_sync at different write sizes | ||
| 1 * 16kB open_sync write | 2,450 | 0.408 ms |
| 2 * 8kB open_sync writes | 1,255 | 0.797 ms |
| 4 * 4kB open_sync writes | 681 | 1.47 ms |
| 8 * 2kB open_sync writes | 280 | 3.57 ms |
| 16 * 1kB open_sync writes | 147 | 6.82 ms |
| fsync on a non-write descriptor | ||
| write, fsync, close | 2,214 | 0.452 ms |
| write, close, fsync | 2,186 | 0.457 ms |
| Non-synced 8 kB writes | ||
| write | 1,340,385 | 0.001 ms |
pg_test_fsync against the Docker volume Postgres keeps its data on. fdatasync is Linux's default wal_sync_method.
pgbench at scale 10
| Workload | Clients | Transactions/s | Median | p95 | p99 | p99.9 | Failed |
|---|---|---|---|---|---|---|---|
| Read/write (TPC-B like) | 1 | 1,433 | 0.669 ms | 0.869 ms | 1.1 ms | 2.72 ms | 0 |
| Read/write (TPC-B like) | 8 | 4,458 | 1.62 ms | 3.09 ms | 4.44 ms | 7.14 ms | 0 |
| Read/write (TPC-B like) | 32 | 4,791 | 5.16 ms | 16.2 ms | 27.1 ms | 47.3 ms | 0 |
| Read only | 1 | 18,149 | 0.051 ms | 0.078 ms | 0.099 ms | 0.179 ms | 0 |
| Read only | 8 | 56,719 | 0.126 ms | 0.219 ms | 0.279 ms | 0.502 ms | 0 |
| Read only | 32 | 61,845 | 0.441 ms | 0.754 ms | 1.13 ms | 2.06 ms | 0 |
Scale 10 (1,000,000 accounts), loaded in 1.05 s. 60 s per run, prepared statements. Latency comes from sampled transaction logs, and p99.9 is left out when fewer than 1,000 were sampled.
pgbench at scale 100
| Workload | Clients | Transactions/s | Median | p95 | p99 | p99.9 | Failed |
|---|---|---|---|---|---|---|---|
| Read/write (TPC-B like) | 1 | 903 | 1.06 ms | 1.51 ms | 2.75 ms | 4.79 ms | 0 |
| Read/write (TPC-B like) | 8 | 3,676 | 1.97 ms | 3.81 ms | 6 ms | 10.4 ms | 0 |
| Read/write (TPC-B like) | 32 | 4,859 | 6.23 ms | 10.5 ms | 13.9 ms | 19.3 ms | 0 |
| Read only | 1 | 4,434 | 0.251 ms | 0.43 ms | 0.885 ms | 1.79 ms | 0 |
| Read only | 8 | 32,225 | 0.186 ms | 0.56 ms | 0.84 ms | 2.09 ms | 0 |
| Read only | 32 | 37,871 | 0.697 ms | 1.5 ms | 2.29 ms | 4.1 ms | 0 |
Scale 100 (10,000,000 accounts), loaded in 12.9 s. 60 s per run, prepared statements. Latency comes from sampled transaction logs, and p99.9 is left out when fewer than 1,000 were sampled.
MySQL
sysbench OLTP
| Workload | Threads | Transactions/s | Queries/s | Median | p95 | p99 | Errors |
|---|---|---|---|---|---|---|---|
| Read/write | 1 | 311 | 6,218 | 2.97 ms | 4.25 ms | 9.06 ms | 0 |
| Read/write | 8 | 819 | 16,375 | 9.56 ms | 15 ms | 20.4 ms | 0 |
| Read/write | 32 | 905 | 18,093 | 35 ms | 56.8 ms | 68.1 ms | 0 |
| Read only | 1 | 695 | 11,114 | 1.39 ms | 1.89 ms | 2.22 ms | 0 |
| Read only | 8 | 1,849 | 29,584 | 4.03 ms | 6.32 ms | 7.3 ms | 0 |
| Read only | 32 | 1,736 | 27,774 | 18 ms | 24.4 ms | 28.2 ms | 0 |
10 tables of 100,000 rows, loaded in 6.5 s. 60 s per run, one connection per thread.
Redis
memtier
| Mix | Operations/s | Hits/s | Median | p99 | p99.9 |
|---|---|---|---|---|---|
| 1:10 set:get | 87,158 | 79,234 | 0.375 ms | 2.69 ms | 4.38 ms |
| 1:1 set:get | 88,336 | 44,168 | 0.391 ms | 2.69 ms | 4.42 ms |
1,000,000 keys of 32 bytes. 64 connections over 2 threads, 60 s per ratio.
Web frameworks
| Framework | Fortunes req/s | Single query req/s | JSON req/s | Fortunes p99 at 256 connections |
|---|---|---|---|---|
| Next.js nextjs | 420 | 1,604 | 2,054 | 1.57 s |
| Express express-postgresjs | 7,806 | 10,454 | 25,611 | 61.9 ms |
| Fastify fastify-postgres | 7,508 | 11,610 | 34,778 | 62.5 ms |
| NestJS nestjs | 4,678 | 5,396 | 15,490 | 105 ms |
| Nuxt nuxt | 6,973 | 10,680 | 33,365 | 103 ms |
| FastAPI fastapi | 3,716 | 4,576 | 19,081 | 340 ms |
| Django django-postgresql | 1,810 | 2,027 | 4,774 | 188 ms |
| Rails rails | 3,262 | 4,227 | 14,264 | 113 ms |
| Laravel laravel | 842 | 869 | 1,552 | 615 ms |
| Symfony symfony | 1,043 | 1,120 | 3,061 | 293 ms |
Peak requests per second across the 64 and 256 connection levels, measured with wrk. Each test has to pass the TechEmpower response checks first, or it's marked invalid.
WooCommerce
Page mix
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 8 virtual users | |||||
| Home page | 2.19 | 720 ms | 849 ms | 900 ms | 0% |
| Shop page | 2.19 | 993 ms | 1.11 s | 1.2 s | 0% |
| Category page | 2.19 | 641 ms | 1.04 s | 1.09 s | 0% |
| Product page | 2.19 | 662 ms | 778 ms | 825 ms | 0% |
| Product search | 2.19 | 565 ms | 694 ms | 755 ms | 0% |
| 32 virtual users | |||||
| Home page | 2.27 | 2.59 s | 2.97 s | 3.11 s | 0% |
| Shop page | 2.27 | 3.46 s | 3.83 s | 3.92 s | 0% |
| Category page | 2.27 | 3.04 s | 3.61 s | 3.8 s | 0% |
| Product page | 2.27 | 2.58 s | 2.92 s | 3.09 s | 0% |
| Product search | 2.14 | 2.4 s | 2.58 s | 2.7 s | 0% |
Cart and checkout
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 8 virtual users | |||||
| Add to cart | 4.28 | 780 ms | 942 ms | 1.04 s | 0% |
| Cart | 4.28 | 615 ms | 751 ms | 814 ms | 0% |
| Checkout | 4.28 | 478 ms | 587 ms | 648 ms | 0% |
| 32 virtual users | |||||
| Add to cart | 4.31 | 2.53 s | 3.09 s | 3.19 s | 0% |
| Cart | 4.31 | 2.66 s | 2.95 s | 3.02 s | 0% |
| Checkout | 4.31 | 2.11 s | 2.42 s | 2.46 s | 0% |
k6 with a fixed number of virtual users, 61 to 71 s per level. The error rate counts responses that weren't a 200.
Discourse
Signed in
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Topic page | 2.25 | 197 ms | 279 ms | 447 ms | 0% |
| Topic JSON | 1.13 | 98.5 ms | 123 ms | 180 ms | 0% |
| Home page | 1.13 | 176 ms | 282 ms | 421 ms | 0% |
| Categories page | 0.563 | 205 ms | 223 ms | 226 ms | 0% |
| User activity page | 0.563 | 126 ms | 157 ms | 191 ms | 0% |
| 4 virtual users | |||||
| Topic page | 4.26 | 419 ms | 587 ms | 1.07 s | 0% |
| Topic JSON | 2.13 | 219 ms | 299 ms | 330 ms | 0% |
| Home page | 2.13 | 375 ms | 462 ms | 590 ms | 0% |
| Categories page | 1.07 | 442 ms | 642 ms | 787 ms | 0% |
| User activity page | 1.06 | 264 ms | 409 ms | 631 ms | 0% |
| 16 virtual users | |||||
| Topic page | 4.1 | 1.53 s | 1.86 s | 2.23 s | 0% |
| Topic JSON | 2.1 | 1.33 s | 1.6 s | 1.73 s | 0% |
| Home page | 2.1 | 1.48 s | 1.71 s | 2.15 s | 0% |
| Categories page | 1.05 | 1.54 s | 1.79 s | 1.94 s | 0% |
| User activity page | 1.05 | 1.35 s | 1.58 s | 1.69 s | 0% |
Anonymous
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 16 virtual users | |||||
| Topic page | 83.3 | 52 ms | 134 ms | 183 ms | 0% |
| Topic JSON | 41.7 | 50.4 ms | 133 ms | 192 ms | 0% |
| Home page | 41.7 | 53.8 ms | 135 ms | 174 ms | 0% |
| Categories page | 20.8 | 49.3 ms | 133 ms | 190 ms | 0% |
| User activity page | 20.8 | 167 ms | 289 ms | 430 ms | 0% |
k6 with a fixed number of virtual users, 60 to 62 s per level, after a 21 s warmup. The error rate counts responses that weren't a 200. Discourse ran with 4 app workers and 256 MB of Postgres shared buffers, what its installer picks for a 2 GB box. It added a 2 GB swapfile first, the way its installer does, and used up to 310 MB of it. The container peaked at 1,452 MB.
Ghost
Readers
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 9.43 | 29.6 ms | 36.5 ms | 43.3 ms | 0% |
| Post page | 23.5 | 15.7 ms | 20.3 ms | 26.6 ms | 0% |
| Tag page | 4.71 | 20.9 ms | 28.1 ms | 35.7 ms | 0% |
| Author page | 4.7 | 20.8 ms | 24.9 ms | 30.3 ms | 0% |
| RSS feed | 4.7 | 25.1 ms | 30.6 ms | 34.2 ms | 0% |
| 4 virtual users | |||||
| Home page | 10.8 | 95.6 ms | 126 ms | 160 ms | 0% |
| Post page | 26.9 | 68.7 ms | 99.1 ms | 138 ms | 0% |
| Tag page | 5.38 | 61.5 ms | 85 ms | 117 ms | 0% |
| Author page | 5.38 | 64.1 ms | 92.4 ms | 141 ms | 0% |
| RSS feed | 5.38 | 67.5 ms | 95.7 ms | 121 ms | 0% |
| 16 virtual users | |||||
| Home page | 10.6 | 379 ms | 467 ms | 508 ms | 0% |
| Post page | 26.6 | 314 ms | 399 ms | 434 ms | 0% |
| Tag page | 5.27 | 206 ms | 288 ms | 317 ms | 0% |
| Author page | 5.3 | 207 ms | 277 ms | 323 ms | 0% |
| RSS feed | 5.3 | 215 ms | 285 ms | 308 ms | 0% |
Staff in Ghost Admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Post list | 5.2 | 28.7 ms | 38.8 ms | 53.7 ms | 0% |
| Post editor | 15.6 | 10.8 ms | 14.4 ms | 20.4 ms | 0% |
| Saving a draft | 15.6 | 27.9 ms | 34.5 ms | 41.8 ms | 0% |
| Member list | 5.22 | 34.6 ms | 46.9 ms | 55.6 ms | 0% |
| 4 virtual users | |||||
| Post list | 6.33 | 35.2 ms | 45.7 ms | 67.3 ms | 0% |
| Post editor | 19.1 | 19.3 ms | 26.8 ms | 40.7 ms | 0% |
| Saving a draft | 19.1 | 154 ms | 207 ms | 242 ms | 0% |
| Member list | 6.36 | 45.5 ms | 60 ms | 88 ms | 0% |
k6 with a fixed number of virtual users, 60 s per level, after a 20 s warmup. The error rate counts responses that weren't a 200. Ghost ran the way its ghost-docker setup runs it: one Node process, and MySQL with its stock 128 MB buffer pool. Memory peaked with Ghost at 358 MB and MySQL at 586 MB.
Wagtail
Visitors
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 1.73 | 76.8 ms | 85.9 ms | 95.9 ms | 0% |
| Blog index | 1.71 | 260 ms | 282 ms | 300 ms | 0% |
| Blog post | 5.14 | 25 ms | 39.4 ms | 43.1 ms | 0% |
| Bread page | 5.14 | 27.4 ms | 32.5 ms | 35.5 ms | 0% |
| Location page | 1.71 | 25.8 ms | 32 ms | 34.2 ms | 0% |
| Site search | 1.71 | 41.6 ms | 72 ms | 79.5 ms | 0% |
| 4 virtual users | |||||
| Home page | 2.87 | 197 ms | 289 ms | 309 ms | 0% |
| Blog index | 2.91 | 668 ms | 927 ms | 971 ms | 0% |
| Blog post | 8.62 | 54.7 ms | 98.6 ms | 125 ms | 0% |
| Bread page | 8.65 | 62.9 ms | 95.8 ms | 105 ms | 0% |
| Location page | 2.92 | 60.3 ms | 90.1 ms | 100 ms | 0% |
| Site search | 2.86 | 81.7 ms | 170 ms | 195 ms | 0% |
| 16 virtual users | |||||
| Home page | 3.24 | 586 ms | 795 ms | 954 ms | 0% |
| Blog index | 3.28 | 1.37 s | 1.76 s | 2.32 s | 0% |
| Blog post | 9.73 | 325 ms | 548 ms | 807 ms | 0% |
| Bread page | 9.76 | 333 ms | 536 ms | 882 ms | 0% |
| Location page | 3.26 | 308 ms | 509 ms | 876 ms | 0% |
| Site search | 3.28 | 389 ms | 639 ms | 832 ms | 0% |
Editors in the Wagtail admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Admin dashboard | 0.695 | 85.2 ms | 96.9 ms | 112 ms | 0% |
| Page explorer | 1.42 | 333 ms | 373 ms | 448 ms | 0% |
| Page editor | 2.13 | 155 ms | 193 ms | 358 ms | 0% |
| Image library | 0.712 | 62 ms | 83.2 ms | 566 ms | 0% |
| Admin page search | 0.695 | 37 ms | 70.4 ms | 73.7 ms | 0% |
| 4 virtual users | |||||
| Admin dashboard | 1.19 | 250 ms | 488 ms | 603 ms | 0% |
| Page explorer | 2.41 | 760 ms | 1.18 s | 1.35 s | 0% |
| Page editor | 3.59 | 378 ms | 686 ms | 813 ms | 0% |
| Image library | 1.2 | 208 ms | 520 ms | 563 ms | 0% |
| Admin page search | 1.19 | 87.6 ms | 273 ms | 356 ms | 0% |
k6 with a fixed number of virtual users, 60 to 61 s per level, after a 20 s warmup. The error rate counts responses that weren't a 200. Wagtail ran the way bakerydemo ships it: uWSGI with 2 workers of 4 threads each, whatever the box, and Postgres and Redis on stock settings. Memory peaked with Wagtail at 297 MB, Postgres at 175 MB, and Redis at 26 MB.
Advertised vs. measured
| Spec | Advertised | Measured |
|---|---|---|
| vCPU | 2 | 2 |
| CPU | Shared vCPU | 0% of busy CPU time stolen |
| RAM | 2 GB | 1.9 GiB |
| Storage | 40 GB NVMe | 37.5 GiB |
| Architecture | x86_64 | x86_64 |
| Virtualization | KVM | KVM |
Guests usually report slightly less RAM and disk than advertised because of kernel reservations and filesystem overhead.
Detected hardware
- CPU model
- AMD EPYC-Rome Processor
- CPU cores
- 2
- CPU frequency
- 2445 MHz
- AES-NI
- Yes
- VM-x/AMD-V
- No
- RAM reported
- 1.9 GiB
- Swap reported
- 0 MiB
- Disk reported
- 37.5 GiB
- Virtualization reported
- KVM
- CPU steal
- 0% of busy CPU time stolen
- Distro
- Ubuntu 24.04.4 LTS
- Kernel
- 6.8.0-138-generic
- Architecture
- x86_64
- IPv4 reachable
- Yes
- IPv6 reachable
- Yes
Advertised at test time
- Plan
- CPX11
- Product line
- regular_purpose
- Location
- Hillsboro, OR
- vCPU
- 2 shared vCPU
- Architecture
- x86_64
- RAM
- 2 GB
- Storage
- 40 GB NVMe
- Virtualization
- KVM
- Network
- Unknown
- Transfer
- 1.1 TB
- Port 25
- On request
- Monthly price at test time
- $20.49
- Hourly price at test time
- $0.033
- YABS version
- v2026-09-20
- Ran at
- Oct 12, 2026, 08:53:45 UTC
- Parser version
- 5
Run timeline
- Queued
- Oct 12, 2026, 08:53:00 UTC
- Server created
- Oct 12, 2026, 08:53:27 UTC
- First update from the server
- Oct 12, 2026, 08:53:27 UTC
- Completed
- Oct 12, 2026, 10:24:55 UTC
- Server deleted
- Oct 12, 2026, 10:24:55 UTC
- Cost of this run
- $0.050
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading details
Loading output.
This party closed at . It's read only now.
Reconnecting. Hang tight.