VPSServer.com 2B 2GB 40GB
Server
-
ProviderVPSServer.com
-
Plan2B 2GB 40GB
-
LocationAtlanta
-
vCPU2
-
RAM2 GB
-
Storage40 GB SSD
-
NetworkUnknown
-
OS imageubuntu_server_24.04_64-bit
-
TriggerScheduled
-
Queued atOct 14, 2026, 04:45:00 UTC
CPU
| Version | Single-core | Multi-core | Result link |
|---|---|---|---|
| Geekbench 7 | 1,339 | 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,389
|
Single-core only |
| Navigation |
1,269
|
Single-core only |
| HTML5 Browser |
1,209
|
Single-core only |
| PDF Viewer |
1,554
|
Single-core only |
| Photo Library |
1,382
|
Single-core only |
| Clang |
1,231
|
Single-core only |
| Text Processing |
1,371
|
Single-core only |
| Asset Compression |
1,536
|
Single-core only |
| HDR |
1,265
|
Single-core only |
| Photo Editor |
1,650
|
Single-core only |
| Ray Tracer |
1,215
|
Single-core only |
| Structure from Motion |
1,509
|
Single-core only |
| Game Physics |
1,188
|
Single-core only |
| Video Encoder |
1,193
|
Single-core only |
| Audio Encoder |
1,261
|
Single-core only |
| Video Player |
1,312
|
Single-core only |
Rank among the 150 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 | 42.5 GB/s | 3 | 2.61% |
| Scale higher is better | 25.1 GB/s | 3 | 0.356% |
| Add higher is better | 31.2 GB/s | 3 | 0.812% |
| Triad higher is better | 31.3 GB/s | 3 | 1.45% |
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 | 996/s | 3 | 5.72% |
| RSA 4096 verifies higher is better | 27,796/s | 3 | 4.37% |
| SHA-256 higher is better | 1.62 GB/s | 3 | 3.84% |
| AES-256-GCM higher is better | 23.5 GB/s | 3 | 0.302% |
| ChaCha20-Poly1305 higher is better | 6.86 GB/s | 3 | 1.1% |
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.45 ms | 3 | 0.565% |
| Requests per second, 90th percentile higher is better | 770/s | 3 | 0.654% |
| Request latency, 99.9th percentile lower is better | 5.76 ms | 3 | 0.321% |
| Requests per second, average higher is better | 728/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 | 188.4 MB/s (48,217 IOPS) | 188.8 MB/s (48,345 IOPS) | 377.2 MB/s (96,562 IOPS) |
| 64K | 1.96 GB/s (32,104 IOPS) | 1.97 GB/s (32,273 IOPS) | 3.93 GB/s (64,377 IOPS) |
| 512K | 3.99 GB/s (8,176 IOPS) | 4.2 GB/s (8,610 IOPS) | 8.2 GB/s (16,786 IOPS) |
| 1M | 4.4 GB/s (4,504 IOPS) | 4.69 GB/s (4,804 IOPS) | 9.09 GB/s (9,308 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.85 Gbps | 2.47 Gbps |
| Eranium, Amsterdam, NL (100G) | IPv4 | 2.17 Gbps | 2.49 Gbps |
| Leaseweb, Singapore, SG (10G) | IPv4 | 886 Mbps | 1.04 Gbps |
| Clouvider, Los Angeles, CA, US (10G) | IPv4 | 1.89 Gbps | 2.77 Gbps |
| Leaseweb, NYC, NY, US (10G) | IPv4 | 8.31 Gbps | 5.96 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,421 | 0.135 ms |
| fdatasync | 7,166 | 0.14 ms |
| fsync | 5,222 | 0.191 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 5,601 | 0.179 ms |
| Two 8 kB writes | ||
| open_datasync | 3,841 | 0.26 ms |
| fdatasync | 7,241 | 0.138 ms |
| fsync | 5,407 | 0.185 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 2,911 | 0.343 ms |
| open_sync at different write sizes | ||
| 1 * 16kB open_sync write | 5,385 | 0.186 ms |
| 2 * 8kB open_sync writes | 2,951 | 0.339 ms |
| 4 * 4kB open_sync writes | 1,397 | 0.716 ms |
| 8 * 2kB open_sync writes | 706 | 1.42 ms |
| 16 * 1kB open_sync writes | 344 | 2.91 ms |
| fsync on a non-write descriptor | ||
| write, fsync, close | 4,770 | 0.21 ms |
| write, close, fsync | 4,826 | 0.207 ms |
| Non-synced 8 kB writes | ||
| write | 1,617,958 | 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,314 | 0.342 ms | 0.773 ms | 1.75 ms | 4.55 ms | 0 |
| Read/write (TPC-B like) | 8 | 6,176 | 1.11 ms | 2.52 ms | 4.44 ms | 7.41 ms | 0 |
| Read/write (TPC-B like) | 32 | 5,835 | 4.18 ms | 13.6 ms | 23.2 ms | 38.4 ms | 0 |
| Read only | 1 | 22,123 | 0.042 ms | 0.066 ms | 0.114 ms | 0.263 ms | 0 |
| Read only | 8 | 80,448 | 0.09 ms | 0.157 ms | 0.202 ms | 0.408 ms | 0 |
| Read only | 32 | 73,723 | 0.375 ms | 0.656 ms | 0.915 ms | 1.51 ms | 0 |
Scale 10 (1,000,000 accounts), loaded in 1.29 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,509 | 0.591 ms | 1.12 ms | 2.24 ms | 4.76 ms | 0 |
| Read/write (TPC-B like) | 8 | 5,031 | 1.37 ms | 3.18 ms | 5.73 ms | 9.51 ms | 0 |
| Read/write (TPC-B like) | 32 | 5,924 | 4.95 ms | 8.9 ms | 12.2 ms | 19.8 ms | 0 |
| Read only | 1 | 7,669 | 0.1 ms | 0.308 ms | 0.606 ms | 2.38 ms | 0 |
| Read only | 8 | 41,315 | 0.142 ms | 0.436 ms | 0.853 ms | 2.61 ms | 0 |
| Read only | 32 | 41,512 | 0.64 ms | 1.4 ms | 2.12 ms | 3.6 ms | 0 |
Scale 100 (10,000,000 accounts), loaded in 11.8 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,037 | 2.31 ms | 3.89 ms | 6.1 ms | 0 |
| Read/write | 8 | 1,119 | 22,388 | 6.55 ms | 12.1 ms | 16.4 ms | 0 |
| Read/write | 32 | 1,187 | 23,732 | 25.3 ms | 46.6 ms | 63.3 ms | 0 |
| Read only | 1 | 880 | 14,073 | 1.08 ms | 1.58 ms | 1.93 ms | 0 |
| Read only | 8 | 2,813 | 45,000 | 2.71 ms | 4.03 ms | 5.09 ms | 0 |
| Read only | 32 | 2,298 | 36,771 | 14.5 ms | 19.6 ms | 23.1 ms | 0 |
10 tables of 100,000 rows, loaded in 6.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 | 97,597 | 88,724 | 0.415 ms | 2.48 ms | 4.32 ms |
| 1:1 set:get | 95,063 | 47,531 | 0.439 ms | 2.48 ms | 4.29 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 | 351 | 1,646 | 1,804 | 1.05 s |
| Express express-postgresjs | 7,419 | 11,795 | 57,647 | 63.2 ms |
| Fastify fastify-postgres | 7,116 | 12,874 | 62,862 | 108 ms |
| NestJS nestjs | 6,408 | 6,452 | 37,142 | 90.1 ms |
| Nuxt nuxt | 6,391 | 12,370 | 49,586 | 83.6 ms |
| FastAPI fastapi | 4,182 | 5,863 | 23,988 | 396 ms |
| Django django-postgresql | 1,707 | 1,376 | 3,582 | 306 ms |
| Rails rails | 3,710 | 5,610 | 22,936 | 107 ms |
| Laravel laravel | 793 | 794 | 1,356 | 369 ms |
| Symfony symfony | 970 | 1,013 | 3,081 | 297 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.22 | 709 ms | 843 ms | 874 ms | 0% |
| Shop page | 2.22 | 985 ms | 1.16 s | 1.18 s | 0% |
| Category page | 2.22 | 590 ms | 1.01 s | 1.07 s | 0% |
| Product page | 2.22 | 643 ms | 754 ms | 827 ms | 0% |
| Product search | 2.22 | 562 ms | 663 ms | 704 ms | 0% |
| 32 virtual users | |||||
| Home page | 2.27 | 2.58 s | 2.93 s | 3.1 s | 0% |
| Shop page | 2.27 | 3.53 s | 3.99 s | 4.05 s | 0% |
| Category page | 2.27 | 3.02 s | 3.59 s | 3.87 s | 0% |
| Product page | 2.27 | 2.58 s | 2.76 s | 2.84 s | 0% |
| Product search | 2.11 | 2.38 s | 2.58 s | 2.66 s | 0% |
Cart and checkout
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 8 virtual users | |||||
| Add to cart | 4.33 | 758 ms | 884 ms | 1.02 s | 0% |
| Cart | 4.33 | 602 ms | 690 ms | 723 ms | 0% |
| Checkout | 4.33 | 457 ms | 533 ms | 556 ms | 0% |
| 32 virtual users | |||||
| Add to cart | 4.35 | 2.55 s | 3.08 s | 3.25 s | 0% |
| Cart | 4.35 | 2.65 s | 2.94 s | 3.08 s | 0% |
| Checkout | 4.35 | 2.07 s | 2.38 s | 2.48 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 | 216 ms | 440 ms | 584 ms | 0% |
| Topic JSON | 1.01 | 109 ms | 136 ms | 178 ms | 0% |
| Home page | 1.01 | 189 ms | 351 ms | 458 ms | 0% |
| Categories page | 0.496 | 220 ms | 252 ms | 315 ms | 0% |
| User activity page | 0.496 | 134 ms | 237 ms | 325 ms | 0% |
| 4 virtual users | |||||
| Topic page | 3.27 | 534 ms | 764 ms | 972 ms | 0% |
| Topic JSON | 1.64 | 289 ms | 382 ms | 424 ms | 0% |
| Home page | 1.63 | 473 ms | 601 ms | 1.29 s | 0% |
| Categories page | 0.839 | 562 ms | 987 ms | 1.4 s | 0% |
| User activity page | 0.806 | 336 ms | 459 ms | 1.04 s | 0% |
| 16 virtual users | |||||
| Topic page | 3.38 | 1.62 s | 2.08 s | 2.17 s | 0% |
| Topic JSON | 1.71 | 1.39 s | 1.79 s | 2.16 s | 0% |
| Home page | 1.7 | 1.54 s | 1.87 s | 2.5 s | 0% |
| Categories page | 0.857 | 1.62 s | 1.97 s | 2.07 s | 0% |
| User activity page | 0.857 | 1.44 s | 1.83 s | 2.06 s | 0% |
Anonymous
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 16 virtual users | |||||
| Topic page | 75.9 | 59.9 ms | 139 ms | 175 ms | 0% |
| Topic JSON | 38 | 58.5 ms | 139 ms | 169 ms | 0% |
| Home page | 38 | 60.7 ms | 146 ms | 185 ms | 0% |
| Categories page | 19 | 61 ms | 140 ms | 188 ms | 0% |
| User activity page | 19 | 188 ms | 298 ms | 431 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 510 MB of it. The container peaked at 1,464 MB.
Ghost
Readers
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 8.36 | 31.9 ms | 42.3 ms | 52.2 ms | 0% |
| Post page | 20.9 | 18.6 ms | 24.6 ms | 43.6 ms | 0% |
| Tag page | 4.18 | 22.3 ms | 30.9 ms | 40.7 ms | 0% |
| Author page | 4.18 | 21.8 ms | 29.7 ms | 42.3 ms | 0% |
| RSS feed | 4.16 | 25.8 ms | 34 ms | 40.5 ms | 0% |
| 4 virtual users | |||||
| Home page | 10.4 | 96.9 ms | 139 ms | 173 ms | 0% |
| Post page | 26 | 71.6 ms | 106 ms | 145 ms | 0% |
| Tag page | 5.2 | 62.8 ms | 87.1 ms | 112 ms | 0% |
| Author page | 5.2 | 63.1 ms | 93.3 ms | 120 ms | 0% |
| RSS feed | 5.2 | 65.3 ms | 98.9 ms | 129 ms | 0% |
| 16 virtual users | |||||
| Home page | 10.3 | 385 ms | 499 ms | 543 ms | 0% |
| Post page | 25.8 | 322 ms | 437 ms | 478 ms | 0% |
| Tag page | 5.16 | 207 ms | 282 ms | 316 ms | 0% |
| Author page | 5.16 | 211 ms | 286 ms | 319 ms | 0% |
| RSS feed | 5.12 | 215 ms | 293 ms | 332 ms | 0% |
Staff in Ghost Admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Post list | 4.08 | 31.8 ms | 45 ms | 125 ms | 0% |
| Post editor | 12.3 | 13.7 ms | 19.5 ms | 90.5 ms | 0% |
| Saving a draft | 12.3 | 34 ms | 45.1 ms | 140 ms | 0% |
| Member list | 4.09 | 35.2 ms | 47.3 ms | 188 ms | 0% |
| 4 virtual users | |||||
| Post list | 5.05 | 47.7 ms | 58.3 ms | 109 ms | 0% |
| Post editor | 15.2 | 26.3 ms | 35.7 ms | 62.1 ms | 0% |
| Saving a draft | 15.2 | 195 ms | 258 ms | 298 ms | 0% |
| Member list | 5.06 | 57.3 ms | 67.5 ms | 97.3 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 235 MB and MySQL at 633 MB.
Wagtail
Visitors
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 1.56 | 84.4 ms | 111 ms | 118 ms | 0% |
| Blog index | 1.55 | 284 ms | 316 ms | 358 ms | 0% |
| Blog post | 4.64 | 27.6 ms | 42 ms | 46.4 ms | 0% |
| Bread page | 4.66 | 29.8 ms | 38.3 ms | 42.2 ms | 0% |
| Location page | 1.55 | 28.2 ms | 34.7 ms | 37 ms | 0% |
| Site search | 1.55 | 46.8 ms | 82.7 ms | 97.5 ms | 0% |
| 4 virtual users | |||||
| Home page | 2.36 | 226 ms | 349 ms | 531 ms | 0% |
| Blog index | 2.36 | 817 ms | 1.06 s | 1.26 s | 0% |
| Blog post | 7.02 | 67.9 ms | 113 ms | 153 ms | 0% |
| Bread page | 7.04 | 77 ms | 113 ms | 130 ms | 0% |
| Location page | 2.36 | 73.9 ms | 102 ms | 125 ms | 0% |
| Site search | 2.34 | 121 ms | 243 ms | 296 ms | 0% |
| 16 virtual users | |||||
| Home page | 2.13 | 829 ms | 1.1 s | 1.33 s | 0% |
| Blog index | 2.28 | 2.17 s | 2.84 s | 3.05 s | 0% |
| Blog post | 6.53 | 477 ms | 808 ms | 1.07 s | 0% |
| Bread page | 6.55 | 476 ms | 796 ms | 1.08 s | 0% |
| Location page | 2.23 | 467 ms | 744 ms | 974 ms | 0% |
| Site search | 2.17 | 568 ms | 925 ms | 1.1 s | 0% |
Editors in the Wagtail admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Admin dashboard | 0.708 | 91.8 ms | 123 ms | 233 ms | 0% |
| Page explorer | 1.43 | 322 ms | 442 ms | 498 ms | 0% |
| Page editor | 2.12 | 156 ms | 189 ms | 290 ms | 0% |
| Image library | 0.708 | 63.6 ms | 78.7 ms | 592 ms | 0% |
| Admin page search | 0.708 | 39.6 ms | 82.9 ms | 92.4 ms | 0% |
| 4 virtual users | |||||
| Admin dashboard | 1.08 | 291 ms | 578 ms | 645 ms | 0% |
| Page explorer | 2.2 | 776 ms | 1.24 s | 1.43 s | 0% |
| Page editor | 3.34 | 439 ms | 751 ms | 907 ms | 0% |
| Image library | 1.12 | 201 ms | 463 ms | 594 ms | 0% |
| Admin page search | 1.08 | 119 ms | 292 ms | 408 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 177 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
- 2B 2GB 40GB
- Product line
- Type B General Purpose
- 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
- $28.00
- Hourly price at test time
- $0.038
- YABS version
- v2026-09-20
- Ran at
- Oct 14, 2026, 04:47:44 UTC
- Parser version
- 5
Run timeline
- Queued
- Oct 14, 2026, 04:45:00 UTC
- First update from the server
- Oct 14, 2026, 04:47:41 UTC
- Completed
- Oct 14, 2026, 06:19:00 UTC
- Server deleted
- Oct 14, 2026, 06:19:00 UTC
- Cost of this run
- $0.060
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.