VPSServer.com 2A 2GB 40GB
Server
-
ProviderVPSServer.com
-
Plan2A 2GB 40GB
-
LocationMiami
-
vCPU2
-
RAM2 GB
-
Storage40 GB SSD
-
NetworkUnknown
-
OS imageubuntu_server_24.04_64-bit
-
TriggerScheduled
-
Queued atOct 16, 2026, 22:54:00 UTC
Latest runs of this plan
- Los Angeles Oct 14, 2026 Skipped
- Atlanta Oct 13, 2026 1,340
- Los Angeles Oct 12, 2026 1,405
CPU
| Version | Single-core | Multi-core | Result link |
|---|---|---|---|
| Geekbench 7 | 1,142 | 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,258
|
Single-core only |
| Navigation |
1,213
|
Single-core only |
| HTML5 Browser |
1,206
|
Single-core only |
| PDF Viewer |
1,340
|
Single-core only |
| Photo Library |
1,203
|
Single-core only |
| Clang |
1,071
|
Single-core only |
| Text Processing |
1,095
|
Single-core only |
| Asset Compression |
926
|
Single-core only |
| HDR |
1,039
|
Single-core only |
| Photo Editor |
1,406
|
Single-core only |
| Ray Tracer |
1,082
|
Single-core only |
| Structure from Motion |
1,410
|
Single-core only |
| Game Physics |
947
|
Single-core only |
| Video Encoder |
992
|
Single-core only |
| Audio Encoder |
1,144
|
Single-core only |
| Video Player |
1,085
|
Single-core only |
Rank among the 216 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.6 GB/s | 3 | 5.62% |
| Scale higher is better | 24.2 GB/s | 3 | 4.91% |
| Add higher is better | 26.3 GB/s | 3 | 4.27% |
| Triad higher is better | 26.2 GB/s | 3 | 4.18% |
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,007/s | 3 | 1.23% |
| RSA 4096 verifies higher is better | 27,158/s | 3 | 0.904% |
| SHA-256 higher is better | 1.13 GB/s | 3 | 8.59% |
| AES-256-GCM higher is better | 18.6 GB/s | 3 | 4.24% |
| ChaCha20-Poly1305 higher is better | 6.87 GB/s | 3 | 1.88% |
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 ms | 3 | 0.417% |
| Requests per second, 90th percentile higher is better | 478/s | 3 | 0.121% |
| Request latency, 99.9th percentile lower is better | 8.72 ms | 3 | 8.71% |
| Requests per second, average higher is better | 440/s | 3 | 2.6% |
Average of 3 runs. Spread is the standard deviation as a share of the average.
Disk
| Block size | Read | Write | Total |
|---|---|---|---|
| 4K | 160.6 MB/s (41,105 IOPS) | 161 MB/s (41,213 IOPS) | 321.6 MB/s (82,318 IOPS) |
| 64K | 1.5 GB/s (24,591 IOPS) | 1.51 GB/s (24,720 IOPS) | 3.01 GB/s (49,311 IOPS) |
| 512K | 3.38 GB/s (6,927 IOPS) | 3.56 GB/s (7,295 IOPS) | 6.94 GB/s (14,222 IOPS) |
| 1M | 4.29 GB/s (4,394 IOPS) | 4.58 GB/s (4,687 IOPS) | 8.87 GB/s (9,081 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 | 76.9 Mbps | 2.11 Gbps |
| Eranium, Amsterdam, NL (100G) | IPv4 | 1.68 Gbps | 2.13 Gbps |
| Leaseweb, Singapore, SG (10G) | IPv4 | 395 Mbps | 976 Mbps |
| Clouvider, Los Angeles, CA, US (10G) | IPv4 | 990 Mbps | 3.78 Gbps |
| Leaseweb, NYC, NY, US (10G) | IPv4 | 5.57 Gbps | 3.08 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,457 | 0.134 ms |
| fdatasync | 6,855 | 0.146 ms |
| fsync | 4,849 | 0.206 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 5,295 | 0.189 ms |
| Two 8 kB writes | ||
| open_datasync | 3,504 | 0.285 ms |
| fdatasync | 6,729 | 0.149 ms |
| fsync | 4,287 | 0.233 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 2,043 | 0.489 ms |
| open_sync at different write sizes | ||
| 1 * 16kB open_sync write | 4,722 | 0.212 ms |
| 2 * 8kB open_sync writes | 2,583 | 0.387 ms |
| 4 * 4kB open_sync writes | 1,191 | 0.84 ms |
| 8 * 2kB open_sync writes | 635 | 1.58 ms |
| 16 * 1kB open_sync writes | 337 | 2.97 ms |
| fsync on a non-write descriptor | ||
| write, fsync, close | 4,399 | 0.227 ms |
| write, close, fsync | 4,400 | 0.227 ms |
| Non-synced 8 kB writes | ||
| write | 1,306,765 | 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,674 | 0.545 ms | 0.894 ms | 1.91 ms | 3.56 ms | 0 |
| Read/write (TPC-B like) | 8 | 4,654 | 1.49 ms | 3.28 ms | 5.69 ms | 10.5 ms | 0 |
| Read/write (TPC-B like) | 32 | 4,362 | 5.68 ms | 17.5 ms | 29.9 ms | 52.2 ms | 0 |
| Read only | 1 | 20,887 | 0.045 ms | 0.077 ms | 0.117 ms | 0.221 ms | 0 |
| Read only | 8 | 55,959 | 0.128 ms | 0.224 ms | 0.284 ms | 0.563 ms | 0 |
| Read only | 32 | 55,610 | 0.5 ms | 0.873 ms | 1.18 ms | 2.11 ms | 0 |
Scale 10 (1,000,000 accounts), loaded in 1.41 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,098 | 0.82 ms | 1.64 ms | 3.15 ms | 6.43 ms | 0 |
| Read/write (TPC-B like) | 8 | 3,946 | 1.74 ms | 4.01 ms | 6.6 ms | 11.1 ms | 0 |
| Read/write (TPC-B like) | 32 | 4,484 | 6.63 ms | 11.5 ms | 15.5 ms | 22.3 ms | 0 |
| Read only | 1 | 5,135 | 0.153 ms | 0.443 ms | 1.11 ms | 2.59 ms | 0 |
| Read only | 8 | 33,005 | 0.186 ms | 0.522 ms | 0.978 ms | 2.49 ms | 0 |
| Read only | 32 | 34,323 | 0.776 ms | 1.67 ms | 2.44 ms | 4.2 ms | 0 |
Scale 100 (10,000,000 accounts), loaded in 14.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 | 391 | 7,819 | 2.35 ms | 3.75 ms | 6.32 ms | 0 |
| Read/write | 8 | 904 | 18,075 | 8.43 ms | 14.2 ms | 19 ms | 0 |
| Read/write | 32 | 905 | 18,091 | 33.7 ms | 61.1 ms | 81.5 ms | 0 |
| Read only | 1 | 761 | 12,182 | 1.27 ms | 1.82 ms | 2.15 ms | 0 |
| Read only | 8 | 1,853 | 29,656 | 4.1 ms | 6.21 ms | 7.57 ms | 0 |
| Read only | 32 | 1,579 | 25,259 | 19.6 ms | 27.7 ms | 33.1 ms | 0 |
10 tables of 100,000 rows, loaded in 7.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 | 87,137 | 79,215 | 0.471 ms | 2.62 ms | 4.38 ms |
| 1:1 set:get | 86,675 | 43,337 | 0.511 ms | 2.58 ms | 4.22 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 | 333 | 1,501 | 1,935 | 1.27 s |
| Express express-postgresjs | 6,994 | 9,330 | 32,745 | 64 ms |
| Fastify fastify-postgres | 6,599 | 10,746 | 44,572 | 82.8 ms |
| NestJS nestjs | 5,329 | 5,512 | 21,439 | 126 ms |
| Nuxt nuxt | 6,076 | 10,181 | 34,194 | 125 ms |
| FastAPI fastapi | 3,511 | 4,611 | 18,149 | 313 ms |
| Django django-postgresql | 1,511 | 1,375 | 2,937 | 376 ms |
| Rails rails | 2,901 | 2,950 | 12,563 | 155 ms |
| Laravel laravel | 602 | 653 | 1,216 | 502 ms |
| Symfony symfony | 758 | 814 | 2,600 | 407 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.85 | 858 ms | 968 ms | 1.01 s | 0% |
| Shop page | 1.85 | 1.17 s | 1.36 s | 1.41 s | 0% |
| Category page | 1.85 | 728 ms | 1.17 s | 1.31 s | 0% |
| Product page | 1.85 | 767 ms | 880 ms | 906 ms | 0% |
| Product search | 1.85 | 682 ms | 774 ms | 856 ms | 0% |
| 32 virtual users | |||||
| Home page | 1.86 | 3.07 s | 3.51 s | 3.67 s | 0% |
| Shop page | 1.86 | 4.12 s | 4.67 s | 4.9 s | 0% |
| Category page | 1.86 | 3.65 s | 4.33 s | 4.46 s | 0% |
| Product page | 1.86 | 3.21 s | 3.54 s | 3.58 s | 0% |
| Product search | 1.86 | 2.85 s | 3.19 s | 3.41 s | 0% |
Cart and checkout
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 8 virtual users | |||||
| Add to cart | 3.47 | 955 ms | 1.07 s | 1.13 s | 0% |
| Cart | 3.47 | 741 ms | 844 ms | 958 ms | 0% |
| Checkout | 3.47 | 579 ms | 664 ms | 805 ms | 0% |
| 32 virtual users | |||||
| Add to cart | 3.57 | 3.05 s | 3.75 s | 4.08 s | 0% |
| Cart | 3.57 | 3.18 s | 3.55 s | 3.66 s | 0% |
| Checkout | 3.57 | 2.51 s | 2.86 s | 3.12 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 | 1.71 | 259 ms | 324 ms | 496 ms | 0% |
| Topic JSON | 0.857 | 132 ms | 214 ms | 307 ms | 0% |
| Home page | 0.857 | 228 ms | 327 ms | 438 ms | 0% |
| Categories page | 0.429 | 269 ms | 317 ms | 338 ms | 0% |
| User activity page | 0.429 | 161 ms | 270 ms | 317 ms | 0% |
| 4 virtual users | |||||
| Topic page | 3.04 | 586 ms | 765 ms | 1.1 s | 0% |
| Topic JSON | 1.51 | 315 ms | 411 ms | 441 ms | 0% |
| Home page | 1.5 | 535 ms | 725 ms | 904 ms | 0% |
| Categories page | 0.774 | 625 ms | 914 ms | 1.5 s | 0% |
| User activity page | 0.741 | 363 ms | 564 ms | 643 ms | 0% |
| 16 virtual users | |||||
| Topic page | 3.03 | 1.66 s | 2.18 s | 2.32 s | 0% |
| Topic JSON | 1.46 | 1.4 s | 1.75 s | 1.93 s | 0% |
| Home page | 1.47 | 1.61 s | 2.25 s | 2.43 s | 0% |
| Categories page | 0.753 | 1.69 s | 2.09 s | 2.39 s | 0% |
| User activity page | 0.769 | 1.47 s | 1.82 s | 1.95 s | 0% |
Anonymous
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 16 virtual users | |||||
| Topic page | 57.7 | 76.7 ms | 193 ms | 271 ms | 0% |
| Topic JSON | 28.9 | 73.7 ms | 185 ms | 268 ms | 0% |
| Home page | 28.9 | 78.2 ms | 192 ms | 263 ms | 0% |
| Categories page | 14.5 | 73.8 ms | 202 ms | 317 ms | 0% |
| User activity page | 14.4 | 254 ms | 415 ms | 604 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 416 MB of it. The container peaked at 1,496 MB.
Ghost
Readers
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 6.93 | 38.3 ms | 55.9 ms | 71.3 ms | 0% |
| Post page | 17.3 | 21.6 ms | 30.4 ms | 40.2 ms | 0% |
| Tag page | 3.46 | 26.7 ms | 38.6 ms | 41.3 ms | 0% |
| Author page | 3.46 | 25.9 ms | 38.7 ms | 44.4 ms | 0% |
| RSS feed | 3.45 | 31.5 ms | 46.9 ms | 49.4 ms | 0% |
| 4 virtual users | |||||
| Home page | 8.34 | 118 ms | 185 ms | 240 ms | 0% |
| Post page | 20.9 | 86.8 ms | 145 ms | 179 ms | 0% |
| Tag page | 4.18 | 75.1 ms | 122 ms | 164 ms | 0% |
| Author page | 4.18 | 77.4 ms | 117 ms | 146 ms | 0% |
| RSS feed | 4.16 | 85.5 ms | 129 ms | 159 ms | 0% |
| 16 virtual users | |||||
| Home page | 8.81 | 450 ms | 610 ms | 649 ms | 0% |
| Post page | 22 | 377 ms | 514 ms | 577 ms | 0% |
| Tag page | 4.38 | 245 ms | 363 ms | 401 ms | 0% |
| Author page | 4.38 | 242 ms | 353 ms | 405 ms | 0% |
| RSS feed | 4.38 | 252 ms | 356 ms | 391 ms | 0% |
Staff in Ghost Admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Post list | 3.97 | 36.4 ms | 49.8 ms | 72.2 ms | 0% |
| Post editor | 11.9 | 14.8 ms | 19.6 ms | 25.9 ms | 0% |
| Saving a draft | 11.9 | 37.3 ms | 47.4 ms | 63.4 ms | 0% |
| Member list | 3.98 | 42.3 ms | 56.4 ms | 66.7 ms | 0% |
| 4 virtual users | |||||
| Post list | 4.9 | 52.5 ms | 74.2 ms | 121 ms | 0% |
| Post editor | 14.7 | 26.6 ms | 38.8 ms | 48.7 ms | 0% |
| Saving a draft | 14.8 | 196 ms | 269 ms | 299 ms | 0% |
| Member list | 4.92 | 51.1 ms | 73.6 ms | 117 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 356 MB and MySQL at 591 MB.
Wagtail
Visitors
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 1.28 | 102 ms | 121 ms | 135 ms | 0% |
| Blog index | 1.28 | 352 ms | 433 ms | 455 ms | 0% |
| Blog post | 3.8 | 32.3 ms | 53.3 ms | 61.6 ms | 0% |
| Bread page | 3.81 | 34.9 ms | 42.9 ms | 48.4 ms | 0% |
| Location page | 1.28 | 32.9 ms | 40.7 ms | 48.2 ms | 0% |
| Site search | 1.26 | 59 ms | 98.3 ms | 109 ms | 0% |
| 4 virtual users | |||||
| Home page | 2.29 | 245 ms | 339 ms | 376 ms | 0% |
| Blog index | 2.32 | 835 ms | 1.15 s | 1.32 s | 0% |
| Blog post | 6.89 | 66.7 ms | 111 ms | 144 ms | 0% |
| Bread page | 6.9 | 77.4 ms | 113 ms | 126 ms | 0% |
| Location page | 2.32 | 73.4 ms | 107 ms | 117 ms | 0% |
| Site search | 2.29 | 114 ms | 216 ms | 252 ms | 0% |
| 16 virtual users | |||||
| Home page | 2.15 | 907 ms | 1.16 s | 1.27 s | 0% |
| Blog index | 2.21 | 2.18 s | 2.72 s | 2.85 s | 0% |
| Blog post | 6.49 | 501 ms | 737 ms | 888 ms | 0% |
| Bread page | 6.48 | 506 ms | 784 ms | 938 ms | 0% |
| Location page | 2.18 | 487 ms | 733 ms | 864 ms | 0% |
| Site search | 2.18 | 583 ms | 861 ms | 982 ms | 0% |
Editors in the Wagtail admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Admin dashboard | 0.61 | 100 ms | 129 ms | 135 ms | 0% |
| Page explorer | 1.24 | 380 ms | 482 ms | 554 ms | 0% |
| Page editor | 1.83 | 174 ms | 247 ms | 351 ms | 0% |
| Image library | 0.61 | 67.1 ms | 88.1 ms | 688 ms | 0% |
| Admin page search | 0.61 | 58 ms | 88.5 ms | 167 ms | 0% |
| 4 virtual users | |||||
| Admin dashboard | 0.989 | 299 ms | 565 ms | 719 ms | 0% |
| Page explorer | 2.01 | 972 ms | 1.49 s | 1.83 s | 0% |
| Page editor | 3.02 | 433 ms | 792 ms | 960 ms | 0% |
| Image library | 1.01 | 204 ms | 559 ms | 706 ms | 0% |
| Admin page search | 0.989 | 125 ms | 289 ms | 467 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 193 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
- 2594 MHz
- AES-NI
- Yes
- VM-x/AMD-V
- No
- 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
- Miami
- 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 16, 2026, 22:57:55 UTC
- Parser version
- 5
Run timeline
- Queued
- Oct 16, 2026, 22:54:00 UTC
- First update from the server
- Oct 16, 2026, 22:57:52 UTC
- Completed
- Oct 17, 2026, 00:31:00 UTC
- Server deleted
- Oct 17, 2026, 00:31:00 UTC
- Cost of this run
- $0.029
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.