VPSServer.com 2A 2GB 40GB
Server
-
ProviderVPSServer.com
-
Plan2A 2GB 40GB
-
LocationLos Angeles
-
vCPU2
-
RAM2 GB
-
Storage40 GB SSD
-
NetworkUnknown
-
OS imageubuntu_server_24.04_64-bit
-
TriggerManual
-
Queued atOct 12, 2026, 00:37:38 UTC
CPU
| Version | Single-core | Multi-core | Result link |
|---|---|---|---|
| Geekbench 7 | 1,405 | 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,440
|
Single-core only |
| Navigation |
1,411
|
Single-core only |
| HTML5 Browser |
1,439
|
Single-core only |
| PDF Viewer |
1,602
|
Single-core only |
| Photo Library |
1,389
|
Single-core only |
| Clang |
1,290
|
Single-core only |
| Text Processing |
1,442
|
Single-core only |
| Asset Compression |
1,588
|
Single-core only |
| HDR |
1,320
|
Single-core only |
| Photo Editor |
1,608
|
Single-core only |
| Ray Tracer |
1,274
|
Single-core only |
| Structure from Motion |
1,624
|
Single-core only |
| Game Physics |
1,261
|
Single-core only |
| Video Encoder |
1,255
|
Single-core only |
| Audio Encoder |
1,270
|
Single-core only |
| Video Player |
1,357
|
Single-core only |
Rank among the 106 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 | 39.2 GB/s | 3 | 5.33% |
| Scale higher is better | 23 GB/s | 3 | 11.9% |
| Add higher is better | 28.3 GB/s | 3 | 9.53% |
| Triad higher is better | 28.3 GB/s | 3 | 9.98% |
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,034/s | 3 | 1.4% |
| RSA 4096 verifies higher is better | 29,079/s | 3 | 0.365% |
| SHA-256 higher is better | 1.68 GB/s | 3 | 0.543% |
| AES-256-GCM higher is better | 24.4 GB/s | 3 | 0.759% |
| ChaCha20-Poly1305 higher is better | 7.09 GB/s | 3 | 1.69% |
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.38 ms | 3 | 0.195% |
| Requests per second, 90th percentile higher is better | 826/s | 3 | 0.504% |
| Request latency, 99.9th percentile lower is better | 4.69 ms | 3 | 4.12% |
| Requests per second, average higher is better | 809/s | 3 | 0.537% |
Average of 3 runs. Spread is the standard deviation as a share of the average.
Disk
| Block size | Read | Write | Total |
|---|---|---|---|
| 4K | 203.5 MB/s (52,104 IOPS) | 204.1 MB/s (52,241 IOPS) | 407.6 MB/s (104,345 IOPS) |
| 64K | 1.84 GB/s (30,149 IOPS) | 1.85 GB/s (30,308 IOPS) | 3.69 GB/s (60,457 IOPS) |
| 512K | 3.54 GB/s (7,241 IOPS) | 3.72 GB/s (7,626 IOPS) | 7.26 GB/s (14,867 IOPS) |
| 1M | 3.96 GB/s (4,053 IOPS) | 4.22 GB/s (4,323 IOPS) | 8.18 GB/s (8,376 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.19 Gbps | 1.65 Gbps |
| Eranium, Amsterdam, NL (100G) | IPv4 | 19.7 Mbps | 1.65 Gbps |
| Leaseweb, Singapore, SG (10G) | IPv4 | 1.12 Gbps | 1.33 Gbps |
| Clouvider, Los Angeles, CA, US (10G) | IPv4 | 9.19 Gbps | 8.27 Gbps |
| Leaseweb, NYC, NY, US (10G) | IPv4 | 2.05 Gbps | 3.2 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 | 9,193 | 0.109 ms |
| fdatasync | 9,139 | 0.109 ms |
| fsync | 6,957 | 0.144 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 7,643 | 0.131 ms |
| Two 8 kB writes | ||
| open_datasync | 4,765 | 0.21 ms |
| fdatasync | 8,732 | 0.115 ms |
| fsync | 7,090 | 0.141 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 3,654 | 0.274 ms |
| open_sync at different write sizes | ||
| 1 * 16kB open_sync write | 7,256 | 0.138 ms |
| 2 * 8kB open_sync writes | 3,567 | 0.28 ms |
| 4 * 4kB open_sync writes | 1,874 | 0.533 ms |
| 8 * 2kB open_sync writes | 939 | 1.07 ms |
| 16 * 1kB open_sync writes | 472 | 2.12 ms |
| fsync on a non-write descriptor | ||
| write, fsync, close | 6,821 | 0.147 ms |
| write, close, fsync | 7,170 | 0.139 ms |
| Non-synced 8 kB writes | ||
| write | 1,637,422 | 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,709 | 0.38 ms | 0.55 ms | 1.12 ms | 3.04 ms | 0 |
| Read/write (TPC-B like) | 8 | 8,067 | 0.876 ms | 1.77 ms | 3.27 ms | 7.37 ms | 0 |
| Read/write (TPC-B like) | 32 | 7,394 | 3.33 ms | 10.5 ms | 18.2 ms | 33.2 ms | 0 |
| Read only | 1 | 24,892 | 0.04 ms | 0.049 ms | 0.06 ms | 0.167 ms | 0 |
| Read only | 8 | 85,967 | 0.085 ms | 0.14 ms | 0.171 ms | 0.316 ms | 0 |
| Read only | 32 | 84,289 | 0.334 ms | 0.523 ms | 0.746 ms | 1.23 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 | 2,062 | 0.425 ms | 0.747 ms | 1.8 ms | 5.22 ms | 0 |
| Read/write (TPC-B like) | 8 | 6,201 | 1.1 ms | 2.59 ms | 5.15 ms | 10.3 ms | 0 |
| Read/write (TPC-B like) | 32 | 7,242 | 4.02 ms | 7.37 ms | 10.7 ms | 21.6 ms | 0 |
| Read only | 1 | 10,495 | 0.086 ms | 0.2 ms | 0.415 ms | 1.97 ms | 0 |
| Read only | 8 | 51,281 | 0.118 ms | 0.343 ms | 0.541 ms | 2.01 ms | 0 |
| Read only | 32 | 48,124 | 0.545 ms | 1.15 ms | 1.71 ms | 3 ms | 0 |
Scale 100 (10,000,000 accounts), loaded in 10.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 | 597 | 11,939 | 1.47 ms | 2.52 ms | 5.18 ms | 0 |
| Read/write | 8 | 1,082 | 21,636 | 6.91 ms | 12.8 ms | 17.3 ms | 0 |
| Read/write | 32 | 1,475 | 29,497 | 20.4 ms | 37.6 ms | 51 ms | 0 |
| Read only | 1 | 1,068 | 17,087 | 0.904 ms | 1.18 ms | 1.39 ms | 0 |
| Read only | 8 | 3,038 | 48,611 | 2.57 ms | 3.55 ms | 4.18 ms | 0 |
| Read only | 32 | 2,656 | 42,492 | 11.9 ms | 15 ms | 17.3 ms | 0 |
10 tables of 100,000 rows, loaded in 5.7 s. 60 s per run, one connection per thread.
Redis
memtier
| Mix | Operations/s | Hits/s | Median | p99 | p99.9 |
|---|---|---|---|---|---|
| 1:10 set:get | 108,591 | 98,719 | 0.319 ms | 2.45 ms | 4.29 ms |
| 1:1 set:get | 102,756 | 51,378 | 0.383 ms | 2.38 ms | 3.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 | 473 | 1,866 | 2,014 | 739 ms |
| Express express-postgresjs | 7,921 | 12,711 | 65,109 | 56.7 ms |
| Fastify fastify-postgres | 7,598 | 13,138 | 66,943 | 60.9 ms |
| NestJS nestjs | 7,101 | 7,449 | 44,900 | 80.7 ms |
| Nuxt nuxt | 6,626 | 12,455 | 56,291 | 88.8 ms |
| FastAPI fastapi | 4,632 | 6,391 | 26,440 | 211 ms |
| Django django-postgresql | 1,540 | 1,784 | 4,378 | 293 ms |
| Rails rails | 3,842 | 4,025 | 23,155 | 84.2 ms |
| Laravel laravel | 820 | 869 | 1,505 | 330 ms |
| Symfony symfony | 1,060 | 1,132 | 3,241 | 298 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.41 | 651 ms | 725 ms | 792 ms | 0% |
| Shop page | 2.41 | 899 ms | 972 ms | 1.01 s | 0% |
| Category page | 2.41 | 547 ms | 892 ms | 994 ms | 0% |
| Product page | 2.41 | 617 ms | 707 ms | 744 ms | 0% |
| Product search | 2.41 | 526 ms | 607 ms | 635 ms | 0% |
| 32 virtual users | |||||
| Home page | 2.5 | 2.33 s | 2.64 s | 2.73 s | 0% |
| Shop page | 2.5 | 3.14 s | 3.49 s | 3.59 s | 0% |
| Category page | 2.5 | 2.65 s | 3.18 s | 3.48 s | 0% |
| Product page | 2.5 | 2.33 s | 2.52 s | 2.57 s | 0% |
| Product search | 2.5 | 2.16 s | 2.35 s | 2.39 s | 0% |
Cart and checkout
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 8 virtual users | |||||
| Add to cart | 4.92 | 673 ms | 755 ms | 772 ms | 0% |
| Cart | 4.92 | 533 ms | 603 ms | 618 ms | 0% |
| Checkout | 4.92 | 405 ms | 461 ms | 477 ms | 0% |
| 32 virtual users | |||||
| Add to cart | 5.02 | 2.18 s | 2.66 s | 2.74 s | 0% |
| Cart | 5.02 | 2.31 s | 2.57 s | 2.64 s | 0% |
| Checkout | 5.02 | 1.8 s | 2.06 s | 2.1 s | 0% |
k6 with a fixed number of virtual users, 61 to 64 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.52 | 176 ms | 222 ms | 351 ms | 0% |
| Topic JSON | 1.28 | 88.1 ms | 149 ms | 269 ms | 0% |
| Home page | 1.28 | 160 ms | 188 ms | 204 ms | 0% |
| Categories page | 0.63 | 186 ms | 232 ms | 369 ms | 0% |
| User activity page | 0.63 | 111 ms | 142 ms | 151 ms | 0% |
| 4 virtual users | |||||
| Topic page | 4.43 | 408 ms | 524 ms | 831 ms | 0% |
| Topic JSON | 2.22 | 208 ms | 273 ms | 285 ms | 0% |
| Home page | 2.21 | 363 ms | 446 ms | 668 ms | 0% |
| Categories page | 1.12 | 429 ms | 541 ms | 775 ms | 0% |
| User activity page | 1.09 | 259 ms | 329 ms | 666 ms | 0% |
| 16 virtual users | |||||
| Topic page | 4.36 | 1.44 s | 1.78 s | 1.95 s | 0% |
| Topic JSON | 2.16 | 1.24 s | 1.48 s | 1.62 s | 0% |
| Home page | 2.16 | 1.38 s | 1.7 s | 1.77 s | 0% |
| Categories page | 1.12 | 1.51 s | 1.85 s | 2.02 s | 0% |
| User activity page | 1.07 | 1.31 s | 1.6 s | 1.77 s | 0% |
Anonymous
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 16 virtual users | |||||
| Topic page | 97.3 | 43.6 ms | 114 ms | 139 ms | 0% |
| Topic JSON | 48.7 | 42.3 ms | 113 ms | 139 ms | 0% |
| Home page | 48.7 | 43.2 ms | 113 ms | 138 ms | 0% |
| Categories page | 24.3 | 44.5 ms | 116 ms | 154 ms | 0% |
| User activity page | 24.4 | 153 ms | 230 ms | 290 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 535 MB of it. The container peaked at 1,486 MB.
Ghost
Readers
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 10.2 | 26.7 ms | 31.5 ms | 46.5 ms | 0% |
| Post page | 25.4 | 15.3 ms | 19.6 ms | 26.9 ms | 0% |
| Tag page | 5.1 | 19 ms | 22.8 ms | 26.9 ms | 0% |
| Author page | 5.08 | 18.5 ms | 21.8 ms | 27.4 ms | 0% |
| RSS feed | 5.08 | 21.6 ms | 25.8 ms | 30 ms | 0% |
| 4 virtual users | |||||
| Home page | 12.4 | 82.2 ms | 112 ms | 148 ms | 0% |
| Post page | 31.1 | 58.9 ms | 84.7 ms | 117 ms | 0% |
| Tag page | 6.24 | 53.6 ms | 76.4 ms | 94.5 ms | 0% |
| Author page | 6.22 | 52.5 ms | 76 ms | 111 ms | 0% |
| RSS feed | 6.21 | 59.5 ms | 81.2 ms | 106 ms | 0% |
| 16 virtual users | |||||
| Home page | 12.7 | 317 ms | 400 ms | 430 ms | 0% |
| Post page | 31.8 | 261 ms | 338 ms | 368 ms | 0% |
| Tag page | 6.34 | 175 ms | 241 ms | 266 ms | 0% |
| Author page | 6.35 | 175 ms | 232 ms | 274 ms | 0% |
| RSS feed | 6.35 | 176 ms | 248 ms | 277 ms | 0% |
Staff in Ghost Admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Post list | 5.22 | 27.1 ms | 36.2 ms | 60.7 ms | 0% |
| Post editor | 15.7 | 11.6 ms | 15.5 ms | 25.2 ms | 0% |
| Saving a draft | 15.7 | 28.4 ms | 37.2 ms | 46.9 ms | 0% |
| Member list | 5.22 | 30.1 ms | 39 ms | 47.9 ms | 0% |
| 4 virtual users | |||||
| Post list | 6.66 | 38 ms | 53.1 ms | 88.5 ms | 0% |
| Post editor | 20.1 | 20.1 ms | 26.8 ms | 51 ms | 0% |
| Saving a draft | 20.1 | 148 ms | 200 ms | 233 ms | 0% |
| Member list | 6.71 | 40.9 ms | 54 ms | 92.6 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 371 MB and MySQL at 582 MB.
Wagtail
Visitors
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 1.88 | 70.2 ms | 84.4 ms | 95.9 ms | 0% |
| Blog index | 1.88 | 235 ms | 255 ms | 269 ms | 0% |
| Blog post | 5.6 | 23 ms | 34.8 ms | 38.2 ms | 0% |
| Bread page | 5.62 | 25 ms | 30.4 ms | 33.4 ms | 0% |
| Location page | 1.88 | 24.2 ms | 28.1 ms | 30.7 ms | 0% |
| Site search | 1.86 | 38.5 ms | 67.3 ms | 82.4 ms | 0% |
| 4 virtual users | |||||
| Home page | 3.05 | 174 ms | 265 ms | 312 ms | 0% |
| Blog index | 3.1 | 622 ms | 846 ms | 912 ms | 0% |
| Blog post | 9.17 | 53.8 ms | 85 ms | 105 ms | 0% |
| Bread page | 9.2 | 59.6 ms | 85.7 ms | 99.2 ms | 0% |
| Location page | 3.1 | 57.9 ms | 82.3 ms | 93.1 ms | 0% |
| Site search | 3.05 | 83.7 ms | 170 ms | 206 ms | 0% |
| 16 virtual users | |||||
| Home page | 3.08 | 621 ms | 790 ms | 897 ms | 0% |
| Blog index | 3.13 | 1.51 s | 1.92 s | 2.05 s | 0% |
| Blog post | 9.23 | 348 ms | 506 ms | 604 ms | 0% |
| Bread page | 9.25 | 359 ms | 556 ms | 657 ms | 0% |
| Location page | 3.1 | 358 ms | 563 ms | 629 ms | 0% |
| Site search | 3.1 | 414 ms | 599 ms | 661 ms | 0% |
Editors in the Wagtail admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Admin dashboard | 0.828 | 76.1 ms | 93.3 ms | 102 ms | 0% |
| Page explorer | 1.69 | 279 ms | 372 ms | 430 ms | 0% |
| Page editor | 2.5 | 134 ms | 169 ms | 240 ms | 0% |
| Image library | 0.828 | 52.4 ms | 64.2 ms | 450 ms | 0% |
| Admin page search | 0.828 | 30.6 ms | 65.2 ms | 72.4 ms | 0% |
| 4 virtual users | |||||
| Admin dashboard | 1.4 | 202 ms | 405 ms | 485 ms | 0% |
| Page explorer | 2.85 | 643 ms | 1.01 s | 1.04 s | 0% |
| Page editor | 4.25 | 330 ms | 572 ms | 645 ms | 0% |
| Image library | 1.42 | 172 ms | 401 ms | 455 ms | 0% |
| Admin page search | 1.4 | 87.6 ms | 193 ms | 222 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 183 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
- Los Angeles
- 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 12, 2026, 00:41:07 UTC
- Parser version
- 5
Run timeline
- Queued
- Oct 12, 2026, 00:37:38 UTC
- Server created
- Oct 12, 2026, 00:41:04 UTC
- First update from the server
- Oct 12, 2026, 00:41:04 UTC
- Completed
- Oct 12, 2026, 02:09:00 UTC
- Server deleted
- Oct 12, 2026, 02:09:00 UTC
- Cost of this run
- $0.027
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.