VPSServer.com 2A 2GB 40GB
Server
-
ProviderVPSServer.com
-
Plan2A 2GB 40GB
-
LocationAtlanta
-
vCPU2
-
RAM2 GB
-
Storage40 GB SSD
-
NetworkUnknown
-
OS imageubuntu_server_24.04_64-bit
-
TriggerScheduled
-
Queued atOct 13, 2026, 02:00:00 UTC
CPU
| Version | Single-core | Multi-core | Result link |
|---|---|---|---|
| Geekbench 7 | 1,340 | 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,380
|
Single-core only |
| Navigation |
1,328
|
Single-core only |
| HTML5 Browser |
1,379
|
Single-core only |
| PDF Viewer |
1,497
|
Single-core only |
| Photo Library |
1,335
|
Single-core only |
| Clang |
1,241
|
Single-core only |
| Text Processing |
1,337
|
Single-core only |
| Asset Compression |
1,549
|
Single-core only |
| HDR |
1,275
|
Single-core only |
| Photo Editor |
1,502
|
Single-core only |
| Ray Tracer |
1,208
|
Single-core only |
| Structure from Motion |
1,459
|
Single-core only |
| Game Physics |
1,219
|
Single-core only |
| Video Encoder |
1,236
|
Single-core only |
| Audio Encoder |
1,274
|
Single-core only |
| Video Player |
1,282
|
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 | 43.7 GB/s | 3 | 2.01% |
| Scale higher is better | 25.8 GB/s | 3 | 2.13% |
| Add higher is better | 31.5 GB/s | 3 | 1.39% |
| Triad higher is better | 31.6 GB/s | 3 | 0.506% |
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 | 1,027/s | 3 | 0.258% |
| RSA 4096 verifies higher is better | 28,374/s | 3 | 1.24% |
| SHA-256 higher is better | 1.66 GB/s | 3 | 0.572% |
| AES-256-GCM higher is better | 24 GB/s | 3 | 0.724% |
| ChaCha20-Poly1305 higher is better | 6.86 GB/s | 3 | 1.48% |
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 | 2.49 ms | 3 | 0.81% |
| Requests per second, 90th percentile higher is better | 759/s | 3 | 1.73% |
| Request latency, 99.9th percentile lower is better | 5.44 ms | 3 | 1.7% |
| Requests per second, average higher is better | 725/s | 3 | 2.44% |
Average of 3 runs. Spread is the standard deviation as a share of the average.
Disk
| Block size | Read | Write | Total |
|---|---|---|---|
| 4K | 169.1 MB/s (43,279 IOPS) | 169.5 MB/s (43,393 IOPS) | 338.6 MB/s (86,672 IOPS) |
| 64K | 1.97 GB/s (32,326 IOPS) | 1.98 GB/s (32,496 IOPS) | 3.96 GB/s (64,822 IOPS) |
| 512K | 3.98 GB/s (8,142 IOPS) | 4.19 GB/s (8,575 IOPS) | 8.16 GB/s (16,717 IOPS) |
| 1M | 4.39 GB/s (4,494 IOPS) | 4.68 GB/s (4,793 IOPS) | 9.07 GB/s (9,287 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.69 Gbps | 2.15 Gbps |
| Eranium, Amsterdam, NL (100G) | IPv4 | 1.87 Gbps | 2.47 Gbps |
| Leaseweb, Singapore, SG (10G) | IPv4 | 912 912 Mbits/sec Mbits/sec | 672 553 Mbits/sec Mbits/sec |
| Clouvider, Los Angeles, CA, US (10G) | IPv4 | 1.59 Gbps | 2.68 Gbps |
| Leaseweb, NYC, NY, US (10G) | IPv4 | 8.2 Gbps | 3.54 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 | 7,476 | 0.134 ms |
| fdatasync | 6,965 | 0.144 ms |
| fsync | 5,542 | 0.18 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 5,777 | 0.173 ms |
| Two 8 kB writes | ||
| open_datasync | 3,651 | 0.274 ms |
| fdatasync | 6,448 | 0.155 ms |
| fsync | 5,184 | 0.193 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 2,203 | 0.454 ms |
| open_sync at different write sizes | ||
| 1 * 16kB open_sync write | 5,442 | 0.184 ms |
| 2 * 8kB open_sync writes | 2,685 | 0.372 ms |
| 4 * 4kB open_sync writes | 1,394 | 0.718 ms |
| 8 * 2kB open_sync writes | 719 | 1.39 ms |
| 16 * 1kB open_sync writes | 341 | 2.94 ms |
| fsync on a non-write descriptor | ||
| write, fsync, close | 5,303 | 0.189 ms |
| write, close, fsync | 5,445 | 0.184 ms |
| Non-synced 8 kB writes | ||
| write | 1,650,834 | 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 | 2,067 | 0.453 ms | 0.787 ms | 1.53 ms | 3.84 ms | 0 |
| Read/write (TPC-B like) | 8 | 6,360 | 1.08 ms | 2.41 ms | 4.29 ms | 7.55 ms | 0 |
| Read/write (TPC-B like) | 32 | 5,679 | 4.28 ms | 13.9 ms | 23.8 ms | 49 ms | 0 |
| Read only | 1 | 22,349 | 0.042 ms | 0.067 ms | 0.116 ms | 0.243 ms | 0 |
| Read only | 8 | 82,116 | 0.087 ms | 0.151 ms | 0.193 ms | 0.345 ms | 0 |
| Read only | 32 | 73,507 | 0.365 ms | 0.776 ms | 1.24 ms | 2.06 ms | 0 |
Scale 10 (1,000,000 accounts), loaded in 1.06 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,395 | 0.645 ms | 1.15 ms | 2.46 ms | 4.85 ms | 0 |
| Read/write (TPC-B like) | 8 | 4,701 | 1.39 ms | 3.71 ms | 7.42 ms | 14.1 ms | 0 |
| Read/write (TPC-B like) | 32 | 6,028 | 4.86 ms | 9 ms | 12.3 ms | 18.5 ms | 0 |
| Read only | 1 | 7,757 | 0.112 ms | 0.282 ms | 0.536 ms | 2.3 ms | 0 |
| Read only | 8 | 44,627 | 0.135 ms | 0.405 ms | 0.644 ms | 2.15 ms | 0 |
| Read only | 32 | 41,269 | 0.635 ms | 1.41 ms | 2.17 ms | 3.6 ms | 0 |
Scale 100 (10,000,000 accounts), loaded in 12.2 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 | 402 | 8,038 | 2.18 ms | 4.1 ms | 7.7 ms | 0 |
| Read/write | 8 | 1,133 | 22,660 | 6.67 ms | 11.7 ms | 15.8 ms | 0 |
| Read/write | 32 | 1,250 | 25,005 | 23.9 ms | 45 ms | 62.2 ms | 0 |
| Read only | 1 | 858 | 13,735 | 1.1 ms | 1.58 ms | 1.93 ms | 0 |
| Read only | 8 | 2,334 | 37,345 | 3.36 ms | 4.49 ms | 5.37 ms | 0 |
| Read only | 32 | 2,350 | 37,592 | 13.2 ms | 18.6 ms | 22.7 ms | 0 |
10 tables of 100,000 rows, loaded in 6.9 s. 60 s per run, one connection per thread.
Redis
memtier
| Mix | Operations/s | Hits/s | Median | p99 | p99.9 |
|---|---|---|---|---|---|
| 1:10 set:get | 95,842 | 87,129 | 0.535 ms | 2.45 ms | 3.92 ms |
| 1:1 set:get | 96,705 | 48,352 | 0.431 ms | 2.46 ms | 3.95 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 | 399 | 1,663 | 1,886 | 888 ms |
| Express express-postgresjs | 7,678 | 11,848 | 58,903 | 72 ms |
| Fastify fastify-postgres | 7,371 | 11,748 | 63,511 | 63 ms |
| NestJS nestjs | 6,634 | 6,638 | 38,524 | 95.5 ms |
| Nuxt nuxt | 6,698 | 11,727 | 49,918 | 80 ms |
| FastAPI fastapi | 4,409 | 6,122 | 22,794 | 290 ms |
| Django django-postgresql | 1,929 | 2,090 | 4,239 | 312 ms |
| Rails rails | 3,470 | 4,527 | 16,910 | 132 ms |
| Laravel laravel | 764 | 803 | 1,380 | 398 ms |
| Symfony symfony | 963 | 1,052 | 2,944 | 296 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.28 | 687 ms | 809 ms | 863 ms | 0% |
| Shop page | 2.28 | 953 ms | 1.09 s | 1.13 s | 0% |
| Category page | 2.28 | 567 ms | 944 ms | 997 ms | 0% |
| Product page | 2.28 | 639 ms | 743 ms | 774 ms | 0% |
| Product search | 2.28 | 560 ms | 622 ms | 651 ms | 0% |
| 32 virtual users | |||||
| Home page | 2.27 | 2.62 s | 3.35 s | 3.54 s | 0% |
| Shop page | 2.27 | 3.51 s | 4.31 s | 4.48 s | 0% |
| Category page | 2.27 | 3.05 s | 3.82 s | 4.02 s | 0% |
| Product page | 2.21 | 2.6 s | 3.06 s | 3.22 s | 0% |
| Product search | 1.83 | 2.42 s | 3.06 s | 3.14 s | 0% |
Cart and checkout
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 8 virtual users | |||||
| Add to cart | 4.38 | 761 ms | 907 ms | 1.07 s | 0% |
| Cart | 4.38 | 605 ms | 711 ms | 907 ms | 0% |
| Checkout | 4.38 | 459 ms | 553 ms | 711 ms | 0% |
| 32 virtual users | |||||
| Add to cart | 4.4 | 2.49 s | 3.08 s | 3.21 s | 0% |
| Cart | 4.4 | 2.62 s | 2.96 s | 3.07 s | 0% |
| Checkout | 4.4 | 2.04 s | 2.5 s | 2.74 s | 0% |
k6 with a fixed number of virtual users, 62 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.14 | 207 ms | 344 ms | 516 ms | 0% |
| Topic JSON | 1.08 | 101 ms | 119 ms | 149 ms | 0% |
| Home page | 1.08 | 184 ms | 221 ms | 305 ms | 0% |
| Categories page | 0.547 | 213 ms | 289 ms | 441 ms | 0% |
| User activity page | 0.53 | 127 ms | 199 ms | 225 ms | 0% |
| 4 virtual users | |||||
| Topic page | 3.95 | 449 ms | 570 ms | 904 ms | 0% |
| Topic JSON | 1.98 | 229 ms | 294 ms | 329 ms | 0% |
| Home page | 1.95 | 402 ms | 542 ms | 913 ms | 0% |
| Categories page | 1.01 | 475 ms | 734 ms | 1.07 s | 0% |
| User activity page | 0.974 | 282 ms | 549 ms | 837 ms | 0% |
| 16 virtual users | |||||
| Topic page | 3.81 | 1.56 s | 1.87 s | 2 s | 0% |
| Topic JSON | 1.88 | 1.32 s | 1.64 s | 1.73 s | 0% |
| Home page | 1.9 | 1.45 s | 1.83 s | 2.12 s | 0% |
| Categories page | 0.989 | 1.57 s | 1.89 s | 2.09 s | 0% |
| User activity page | 0.957 | 1.35 s | 1.74 s | 1.87 s | 0% |
Anonymous
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 16 virtual users | |||||
| Topic page | 82.4 | 54.5 ms | 130 ms | 174 ms | 0% |
| Topic JSON | 41.2 | 52.3 ms | 128 ms | 166 ms | 0% |
| Home page | 41.2 | 54.7 ms | 128 ms | 161 ms | 0% |
| Categories page | 20.6 | 54.6 ms | 128 ms | 161 ms | 0% |
| User activity page | 20.6 | 177 ms | 264 ms | 381 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 559 MB of it. The container peaked at 1,469 MB.
Ghost
Readers
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 9.03 | 29.9 ms | 36.8 ms | 44.7 ms | 0% |
| Post page | 22.5 | 17.4 ms | 21.7 ms | 35.1 ms | 0% |
| Tag page | 4.51 | 21.1 ms | 26.5 ms | 35.7 ms | 0% |
| Author page | 4.51 | 20.4 ms | 26 ms | 31.7 ms | 0% |
| RSS feed | 4.5 | 24.1 ms | 32.2 ms | 42.1 ms | 0% |
| 4 virtual users | |||||
| Home page | 11.2 | 91.3 ms | 129 ms | 159 ms | 0% |
| Post page | 27.9 | 66 ms | 93.6 ms | 122 ms | 0% |
| Tag page | 5.57 | 57.7 ms | 85.1 ms | 115 ms | 0% |
| Author page | 5.59 | 59.5 ms | 87.1 ms | 130 ms | 0% |
| RSS feed | 5.59 | 64 ms | 87 ms | 127 ms | 0% |
| 16 virtual users | |||||
| Home page | 11.5 | 347 ms | 438 ms | 466 ms | 0% |
| Post page | 28.7 | 289 ms | 378 ms | 418 ms | 0% |
| Tag page | 5.75 | 191 ms | 269 ms | 295 ms | 0% |
| Author page | 5.75 | 190 ms | 257 ms | 293 ms | 0% |
| RSS feed | 5.75 | 194 ms | 276 ms | 310 ms | 0% |
Staff in Ghost Admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Post list | 4.6 | 30.3 ms | 43 ms | 64.2 ms | 0% |
| Post editor | 13.8 | 13.1 ms | 17.5 ms | 25 ms | 0% |
| Saving a draft | 13.8 | 32.4 ms | 43.7 ms | 63.8 ms | 0% |
| Member list | 4.6 | 33.1 ms | 45.4 ms | 60.8 ms | 0% |
| 4 virtual users | |||||
| Post list | 5.75 | 39.5 ms | 54.2 ms | 88.1 ms | 0% |
| Post editor | 17.3 | 23.3 ms | 31.5 ms | 47.9 ms | 0% |
| Saving a draft | 17.3 | 167 ms | 229 ms | 267 ms | 0% |
| Member list | 5.78 | 46.4 ms | 60.1 ms | 99.5 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 362 MB and MySQL at 596 MB.
Wagtail
Visitors
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 1.68 | 78.3 ms | 88.9 ms | 96.2 ms | 0% |
| Blog index | 1.66 | 270 ms | 298 ms | 314 ms | 0% |
| Blog post | 5.01 | 25.5 ms | 38.1 ms | 44.1 ms | 0% |
| Bread page | 5.03 | 27.6 ms | 33.5 ms | 37.2 ms | 0% |
| Location page | 1.68 | 26.7 ms | 30.7 ms | 32.9 ms | 0% |
| Site search | 1.66 | 43.2 ms | 73.1 ms | 79.6 ms | 0% |
| 4 virtual users | |||||
| Home page | 2.71 | 190 ms | 288 ms | 360 ms | 0% |
| Blog index | 2.76 | 744 ms | 951 ms | 1 s | 0% |
| Blog post | 8.14 | 58.5 ms | 106 ms | 144 ms | 0% |
| Bread page | 8.17 | 65.3 ms | 96.2 ms | 110 ms | 0% |
| Location page | 2.76 | 61.6 ms | 88.9 ms | 103 ms | 0% |
| Site search | 2.71 | 94.3 ms | 193 ms | 235 ms | 0% |
| 16 virtual users | |||||
| Home page | 2.88 | 648 ms | 880 ms | 980 ms | 0% |
| Blog index | 2.9 | 1.6 s | 2.06 s | 2.2 s | 0% |
| Blog post | 8.53 | 369 ms | 619 ms | 758 ms | 0% |
| Bread page | 8.6 | 373 ms | 634 ms | 772 ms | 0% |
| Location page | 2.87 | 372 ms | 607 ms | 755 ms | 0% |
| Site search | 2.83 | 439 ms | 756 ms | 834 ms | 0% |
Editors in the Wagtail admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Admin dashboard | 0.744 | 85.5 ms | 97 ms | 114 ms | 0% |
| Page explorer | 1.52 | 307 ms | 428 ms | 509 ms | 0% |
| Page editor | 2.25 | 146 ms | 191 ms | 257 ms | 0% |
| Image library | 0.744 | 60.1 ms | 71.2 ms | 524 ms | 0% |
| Admin page search | 0.744 | 36.7 ms | 71.1 ms | 74.5 ms | 0% |
| 4 virtual users | |||||
| Admin dashboard | 1.25 | 251 ms | 421 ms | 495 ms | 0% |
| Page explorer | 2.52 | 762 ms | 1.16 s | 1.55 s | 0% |
| Page editor | 3.8 | 323 ms | 679 ms | 839 ms | 0% |
| Image library | 1.25 | 186 ms | 493 ms | 576 ms | 0% |
| Admin page search | 1.25 | 98 ms | 233 ms | 275 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 301 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 SSD | 39.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
- Intel Xeon Processor (SapphireRapids)
- CPU cores
- 2
- CPU frequency
- 2700 MHz
- AES-NI
- Yes
- VM-x/AMD-V
- Yes
- RAM reported
- 1.9 GiB
- Swap reported
- 0 MiB
- Disk reported
- 39.3 GiB
- Virtualization reported
- KVM
- CPU steal
- 0% of busy CPU time stolen
- Distro
- Ubuntu 24.04.5 LTS
- Kernel
- 6.8.0-139-generic
- Architecture
- x86_64
- IPv4 reachable
- Yes
- IPv6 reachable
- No
Advertised at test time
- Plan
- 2A 2GB 40GB
- Product line
- Type A Availability
- Location
- Atlanta
- vCPU
- 2 shared vCPU
- Architecture
- x86_64
- RAM
- 2 GB
- Storage
- 40 GB SSD
- Virtualization
- KVM
- Network
- Unknown
- Transfer
- 5 TB
- Port 25
- Unknown
- Monthly price at test time
- $13.00
- Hourly price at test time
- $0.018
- YABS version
- v2026-09-20
- Ran at
- Oct 13, 2026, 02:03:36 UTC
- Parser version
- 5
Run timeline
- Queued
- Oct 13, 2026, 02:00:00 UTC
- Server created
- Oct 13, 2026, 02:03:33 UTC
- First update from the server
- Oct 13, 2026, 02:03:33 UTC
- Completed
- Oct 13, 2026, 03:33:00 UTC
- Server deleted
- Oct 13, 2026, 03:33:00 UTC
- Cost of this run
- $0.028
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.