X-ZoneServers VPS I KVM
Server
-
ProviderX-ZoneServers
-
PlanVPS I KVM
-
LocationAshburn
-
vCPU1
-
RAM2 GB
-
Storage20 GB SSD
-
Network1 Gbps
-
OS imageUbuntu 24.04 LTS
-
TriggerScheduled
-
Queued atOct 15, 2026, 08:33:00 UTC
CPU
| Version | Single-core | Multi-core | Result link |
|---|---|---|---|
| Geekbench 7 | 1,489 | Skipped | Geekbench Browser |
Multi-core was skipped because Geekbench 7 needs about 2.1 GB of free memory to run 1 thread, 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,472
|
Single-core only |
| Navigation |
1,607
|
Single-core only |
| HTML5 Browser |
1,483
|
Single-core only |
| PDF Viewer |
1,501
|
Single-core only |
| Photo Library |
1,523
|
Single-core only |
| Clang |
1,363
|
Single-core only |
| Text Processing |
1,378
|
Single-core only |
| Asset Compression |
1,453
|
Single-core only |
| HDR |
1,512
|
Single-core only |
| Photo Editor |
1,792
|
Single-core only |
| Ray Tracer |
1,388
|
Single-core only |
| Structure from Motion |
1,723
|
Single-core only |
| Game Physics |
1,368
|
Single-core only |
| Video Encoder |
1,406
|
Single-core only |
| Audio Encoder |
1,414
|
Single-core only |
| Video Player |
1,508
|
Single-core only |
Rank among the 191 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 | 29.9 GB/s | 3 | 2.92% |
| Scale higher is better | 36.3 GB/s | 3 | 6.96% |
| Add higher is better | 26.9 GB/s | 3 | 13% |
| Triad higher is better | 28 GB/s | 3 | 8.07% |
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 | 560/s | 3 | 0.812% |
| RSA 4096 verifies higher is better | 13,509/s | 3 | 0.0886% |
| SHA-256 higher is better | 835 MB/s | 3 | 0.234% |
| AES-256-GCM higher is better | 8.26 GB/s | 3 | 0.0414% |
| ChaCha20-Poly1305 higher is better | 3.12 GB/s | 3 | 0.0763% |
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.8 ms | 3 | 0.192% |
| Requests per second, 90th percentile higher is better | 206/s | 3 | 0.28% |
| Request latency, 99.9th percentile lower is better | 8.64 ms | 3 | 3% |
| Requests per second, average higher is better | 206/s | 3 | 0.363% |
Average of 3 runs. Spread is the standard deviation as a share of the average.
Disk
| Block size | Read | Write | Total |
|---|---|---|---|
| 4K | 361.1 MB/s (92,442 IOPS) | 362.1 MB/s (92,686 IOPS) | 723.2 MB/s (185,128 IOPS) |
| 64K | 2.65 GB/s (43,402 IOPS) | 2.66 GB/s (43,630 IOPS) | 5.31 GB/s (87,032 IOPS) |
| 512K | 6.13 GB/s (12,547 IOPS) | 6.45 GB/s (13,213 IOPS) | 12.58 GB/s (25,760 IOPS) |
| 1M | 6.52 GB/s (6,673 IOPS) | 6.95 GB/s (7,117 IOPS) | 13.47 GB/s (13,790 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 | 96.9 Mbps | 88.2 Mbps |
| Eranium, Amsterdam, NL (100G) | IPv4 | 98.4 Mbps | 89.5 Mbps |
| Leaseweb, Singapore, SG (10G) | IPv4 | 90.8 Mbps | 69.2 Mbps |
| Clouvider, Los Angeles, CA, US (10G) | IPv4 | 101 Mbps | 92.1 Mbps |
| Leaseweb, NYC, NY, US (10G) | IPv4 | 99.5 Mbps | 88.3 Mbps |
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 | 2,586 | 0.387 ms |
| fdatasync | 2,610 | 0.383 ms |
| fsync | 1,149 | 0.871 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 1,237 | 0.808 ms |
| Two 8 kB writes | ||
| open_datasync | 1,394 | 0.718 ms |
| fdatasync | 2,382 | 0.42 ms |
| fsync | 1,162 | 0.86 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 662 | 1.51 ms |
| open_sync at different write sizes | ||
| 1 * 16kB open_sync write | 1,287 | 0.777 ms |
| 2 * 8kB open_sync writes | 664 | 1.51 ms |
| 4 * 4kB open_sync writes | 329 | 3.04 ms |
| 8 * 2kB open_sync writes | 227 | 4.4 ms |
| 16 * 1kB open_sync writes | 107 | 9.38 ms |
| fsync on a non-write descriptor | ||
| write, fsync, close | 1,251 | 0.799 ms |
| write, close, fsync | 1,190 | 0.84 ms |
| Non-synced 8 kB writes | ||
| write | 1,636,801 | 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,731 | 0.559 ms | 0.685 ms | 0.926 ms | 1.82 ms | 0 |
| Read/write (TPC-B like) | 8 | 3,959 | 1.77 ms | 3.66 ms | 5.27 ms | 10.1 ms | 0 |
| Read/write (TPC-B like) | 32 | 4,303 | 5.72 ms | 18 ms | 31 ms | 51.7 ms | 0 |
| Read only | 1 | 63,510 | 0.015 ms | 0.019 ms | 0.03 ms | 0.045 ms | 0 |
| Read only | 8 | 54,499 | 0.125 ms | 0.232 ms | 0.271 ms | 0.545 ms | 0 |
| Read only | 32 | 50,044 | 0.566 ms | 0.719 ms | 0.847 ms | 1.78 ms | 0 |
Scale 10 (1,000,000 accounts), loaded in 1.3 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 | 1,204 | 0.806 ms | 1.01 ms | 1.66 ms | 3.04 ms | 0 |
| Read/write (TPC-B like) | 8 | 3,143 | 2.53 ms | 3.99 ms | 5.36 ms | 9.66 ms | 0 |
| Read/write (TPC-B like) | 32 | 4,081 | 7.4 ms | 11.3 ms | 14.5 ms | 19.8 ms | 0 |
| Read only | 1 | 16,039 | 0.033 ms | 0.142 ms | 0.219 ms | 0.779 ms | 0 |
| Read only | 8 | 31,111 | 0.209 ms | 0.494 ms | 0.667 ms | 1.66 ms | 0 |
| Read only | 32 | 29,190 | 0.954 ms | 1.47 ms | 2.17 ms | 3.2 ms | 0 |
Scale 100 (10,000,000 accounts), loaded in 13.7 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 | 352 | 7,031 | 2.66 ms | 3.43 ms | 7.3 ms | 0 |
| Read/write | 8 | 755 | 15,108 | 10.3 ms | 15.5 ms | 21.1 ms | 0 |
| Read/write | 32 | 759 | 15,176 | 39.7 ms | 69.3 ms | 90.8 ms | 0 |
| Read only | 1 | 1,746 | 27,937 | 0.556 ms | 0.654 ms | 1.04 ms | 0 |
| Read only | 8 | 1,600 | 25,602 | 4.91 ms | 5.99 ms | 6.91 ms | 0 |
| Read only | 32 | 1,453 | 23,245 | 21.9 ms | 26.7 ms | 29.7 ms | 0 |
10 tables of 100,000 rows, loaded in 12.1 s. 60 s per run, one connection per thread.
Redis
memtier
| Mix | Operations/s | Hits/s | Median | p99 | p99.9 |
|---|---|---|---|---|---|
| 1:10 set:get | 79,163 | 71,966 | 0.847 ms | 1.19 ms | 2.56 ms |
| 1:1 set:get | 77,553 | 38,776 | 0.863 ms | 1.25 ms | 2.62 ms |
1,000,000 keys of 32 bytes. 64 connections over 1 thread, 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 | 371 | 1,374 | 1,997 | 1.3 s |
| Express express-postgresjs | 4,145 | 6,680 | 31,981 | 969 ms |
| Fastify fastify-postgres | 4,117 | 6,938 | 36,453 | 1.73 s |
| NestJS nestjs | 3,554 | 3,657 | 15,015 | 123 ms |
| Nuxt nuxt | 3,774 | 6,781 | 29,238 | 1.91 s |
| FastAPI fastapi | 2,441 | 3,097 | 15,461 | 466 ms |
| Django django-postgresql | 1,072 | 1,209 | 3,061 | 264 ms |
| Rails rails | 2,069 | 2,880 | 12,760 | 135 ms |
| Laravel laravel | 513 | 547 | 959 | 530 ms |
| Symfony symfony | 626 | 684 | 1,901 | 423 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.
Web apps
WooCommerce
Page mix
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 8 virtual users | |||||
| Home page | 1.39 | 1.09 s | 1.18 s | 1.2 s | 0% |
| Shop page | 1.39 | 1.41 s | 1.58 s | 1.59 s | 0% |
| Category page | 1.39 | 1.17 s | 1.51 s | 1.56 s | 0% |
| Product page | 1.39 | 1.06 s | 1.21 s | 1.26 s | 0% |
| Product search | 1.39 | 975 ms | 1.06 s | 1.13 s | 0% |
| 32 virtual users | |||||
| Home page | 1.4 | 4 s | 4.41 s | 4.51 s | 0% |
| Shop page | 1.4 | 5.28 s | 6 s | 6.17 s | 0% |
| Category page | 1.4 | 4.91 s | 5.7 s | 5.95 s | 0% |
| Product page | 1.4 | 4.32 s | 4.56 s | 4.63 s | 0% |
| Product search | 1.4 | 4.02 s | 4.32 s | 4.38 s | 0% |
Cart and checkout
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 8 virtual users | |||||
| Add to cart | 2.72 | 1.11 s | 1.23 s | 1.25 s | 0% |
| Cart | 2.72 | 996 ms | 1.1 s | 1.13 s | 0% |
| Checkout | 2.72 | 833 ms | 985 ms | 1.02 s | 0% |
| 32 virtual users | |||||
| Add to cart | 2.78 | 3.72 s | 4.66 s | 4.84 s | 0% |
| Cart | 2.78 | 4.21 s | 4.61 s | 4.76 s | 0% |
| Checkout | 2.78 | 3.33 s | 3.76 s | 3.85 s | 0% |
k6 with a fixed number of virtual users, 62 to 69 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.55 | 165 ms | 272 ms | 453 ms | 0% |
| Topic JSON | 1.29 | 82.4 ms | 116 ms | 167 ms | 0% |
| Home page | 1.29 | 150 ms | 218 ms | 339 ms | 0% |
| Categories page | 0.646 | 174 ms | 275 ms | 416 ms | 0% |
| User activity page | 0.646 | 102 ms | 239 ms | 283 ms | 0% |
| 4 virtual users | |||||
| Topic page | 2.11 | 809 ms | 1.02 s | 2.01 s | 0% |
| Topic JSON | 1.07 | 425 ms | 505 ms | 574 ms | 0% |
| Home page | 1.05 | 734 ms | 915 ms | 1.77 s | 0% |
| Categories page | 0.544 | 845 ms | 2.3 s | 2.43 s | 0% |
| User activity page | 0.527 | 493 ms | 855 ms | 1.26 s | 0% |
| 16 virtual users | |||||
| Topic page | 2.01 | 1.89 s | 2.56 s | 3.27 s | 0% |
| Topic JSON | 1.02 | 1.5 s | 1.97 s | 2.27 s | 0% |
| Home page | 1.02 | 1.87 s | 2.34 s | 3.11 s | 0% |
| Categories page | 0.517 | 1.92 s | 2.38 s | 2.42 s | 0% |
| User activity page | 0.485 | 1.62 s | 1.95 s | 2.04 s | 0% |
Anonymous
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 16 virtual users | |||||
| Topic page | 45.4 | 95.5 ms | 240 ms | 316 ms | 0% |
| Topic JSON | 22.7 | 91.6 ms | 235 ms | 293 ms | 0.0728% |
| Home page | 22.7 | 90.3 ms | 238 ms | 315 ms | 0% |
| Categories page | 11.4 | 103 ms | 244 ms | 314 ms | 0% |
| User activity page | 11.4 | 300 ms | 481 ms | 785 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 353 MB of it. The container peaked at 1,505 MB.
Ghost
Readers
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 8.16 | 33.9 ms | 45.1 ms | 84.4 ms | 0% |
| Post page | 20.4 | 17.2 ms | 26.4 ms | 54.9 ms | 0% |
| Tag page | 4.08 | 22.9 ms | 30.4 ms | 37.3 ms | 0% |
| Author page | 4.08 | 23.8 ms | 32.9 ms | 43.4 ms | 0% |
| RSS feed | 4.06 | 26.7 ms | 36.1 ms | 58.6 ms | 0% |
| 4 virtual users | |||||
| Home page | 8.37 | 125 ms | 182 ms | 261 ms | 0% |
| Post page | 20.9 | 84.8 ms | 125 ms | 202 ms | 0% |
| Tag page | 4.19 | 76 ms | 102 ms | 156 ms | 0% |
| Author page | 4.19 | 82.7 ms | 137 ms | 208 ms | 0% |
| RSS feed | 4.18 | 83.4 ms | 119 ms | 200 ms | 0% |
| 16 virtual users | |||||
| Home page | 8.3 | 476 ms | 621 ms | 657 ms | 0% |
| Post page | 20.8 | 396 ms | 534 ms | 583 ms | 0% |
| Tag page | 4.15 | 255 ms | 378 ms | 418 ms | 0% |
| Author page | 4.18 | 251 ms | 377 ms | 415 ms | 0% |
| RSS feed | 4.12 | 261 ms | 380 ms | 406 ms | 0% |
Staff in Ghost Admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Post list | 4.25 | 33.8 ms | 53.6 ms | 89.2 ms | 0% |
| Post editor | 12.8 | 13.5 ms | 20.7 ms | 36.1 ms | 0% |
| Saving a draft | 12.8 | 33 ms | 46.9 ms | 85.5 ms | 0% |
| Member list | 4.25 | 37.1 ms | 54.5 ms | 79.1 ms | 0% |
| 4 virtual users | |||||
| Post list | 4.57 | 50.8 ms | 68.3 ms | 137 ms | 0% |
| Post editor | 13.8 | 25.2 ms | 37.1 ms | 64.4 ms | 0% |
| Saving a draft | 13.8 | 215 ms | 297 ms | 366 ms | 0% |
| Member list | 4.59 | 55.1 ms | 73.7 ms | 172 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 346 MB and MySQL at 576 MB.
Wagtail
Visitors
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 1.85 | 68.3 ms | 84.7 ms | 102 ms | 0% |
| Blog index | 1.83 | 235 ms | 263 ms | 314 ms | 0% |
| Blog post | 5.49 | 22.7 ms | 34.1 ms | 42.7 ms | 0% |
| Bread page | 5.51 | 24.8 ms | 31 ms | 38.9 ms | 0% |
| Location page | 1.83 | 23.9 ms | 31.9 ms | 46.6 ms | 0% |
| Site search | 1.83 | 38.9 ms | 69.3 ms | 226 ms | 0% |
| 4 virtual users | |||||
| Home page | 1.8 | 310 ms | 393 ms | 597 ms | 0% |
| Blog index | 1.85 | 1 s | 1.16 s | 1.34 s | 0% |
| Blog post | 5.42 | 86.7 ms | 137 ms | 158 ms | 0% |
| Bread page | 5.45 | 97.9 ms | 126 ms | 186 ms | 0% |
| Location page | 1.85 | 93.5 ms | 117 ms | 127 ms | 0% |
| Site search | 1.78 | 147 ms | 272 ms | 289 ms | 0% |
| 16 virtual users | |||||
| Home page | 1.76 | 1.06 s | 1.38 s | 1.45 s | 0% |
| Blog index | 1.81 | 2.59 s | 3.21 s | 3.33 s | 0% |
| Blog post | 5.24 | 615 ms | 989 ms | 1.16 s | 0% |
| Bread page | 5.26 | 614 ms | 929 ms | 1.08 s | 0% |
| Location page | 1.76 | 599 ms | 953 ms | 1.13 s | 0% |
| Site search | 1.75 | 734 ms | 1.1 s | 1.16 s | 0% |
Editors in the Wagtail admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Admin dashboard | 0.911 | 68.3 ms | 75.9 ms | 86.7 ms | 0% |
| Page explorer | 1.85 | 253 ms | 275 ms | 394 ms | 0% |
| Page editor | 2.77 | 120 ms | 150 ms | 267 ms | 0% |
| Image library | 0.911 | 49.3 ms | 56.8 ms | 517 ms | 0% |
| Admin page search | 0.911 | 26.7 ms | 57.9 ms | 61 ms | 0% |
| 4 virtual users | |||||
| Admin dashboard | 0.826 | 365 ms | 465 ms | 498 ms | 0% |
| Page explorer | 1.7 | 1.19 s | 1.44 s | 1.77 s | 0% |
| Page editor | 2.51 | 550 ms | 742 ms | 970 ms | 0% |
| Image library | 0.826 | 253 ms | 436 ms | 639 ms | 0% |
| Admin page search | 0.826 | 128 ms | 274 ms | 389 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 296 MB, Postgres at 175 MB, and Redis at 26 MB.
Advertised vs. measured
| Spec | Advertised | Measured |
|---|---|---|
| vCPU | 1 | 1 |
| CPU | Shared vCPU | 0.1% of busy CPU time stolen |
| RAM | 2 GB | 1.9 GiB |
| Storage | 20 GB SSD | 19.3 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-Turin Processor
- CPU cores
- 1
- CPU frequency
- 2250 MHz
- AES-NI
- Yes
- VM-x/AMD-V
- Yes
- RAM reported
- 1.9 GiB
- Swap reported
- 0 MiB
- Disk reported
- 19.3 GiB
- Virtualization reported
- KVM
- CPU steal
- 0.1% of busy CPU time stolen
- Distro
- Ubuntu 24.04.4 LTS
- Kernel
- 6.8.0-124-generic
- Architecture
- x86_64
- IPv4 reachable
- Yes
- IPv6 reachable
- No
Advertised at test time
- Plan
- VPS I KVM
- Product line
- Hourly VPS
- Location
- Ashburn
- vCPU
- 1 shared vCPU
- Architecture
- x86_64
- RAM
- 2 GB
- Storage
- 20 GB SSD
- Virtualization
- KVM
- Network
- 1 Gbps
- Transfer
- Unmetered
- Port 25
- Unknown
- Monthly price at test time
- €5.50 EUR
- Hourly price at test time
- €0.0077 EUR
- YABS version
- v2026-09-20
- Ran at
- Oct 15, 2026, 08:35:41 UTC
- Parser version
- 5
Run timeline
- Queued
- Oct 15, 2026, 08:33:00 UTC
- Server created
- Oct 15, 2026, 08:33:53 UTC
- First update from the server
- Oct 15, 2026, 08:33:53 UTC
- Completed
- Oct 15, 2026, 10:12:58 UTC
- Server deleted
- Oct 15, 2026, 10:12:58 UTC
- Cost of this run
- €0.013 EUR
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.