RamNode 2GB Standard
Piscataway, NJ
Server
-
ProviderRamNode
-
Plan2GB Standard
-
LocationPiscataway, NJ
-
vCPU2
-
RAM2 GB
-
Storage80 GB SSD
-
NetworkUnknown
-
OS imageUbuntu 24.04 Server Cloud
-
TriggerScheduled
-
Queued atOct 13, 2026, 23:24:00 UTC
CPU
| Version | Single-core | Multi-core | Result link |
|---|---|---|---|
| Geekbench 7 | 477 | 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 |
556
|
Single-core only |
| Navigation |
618
|
Single-core only |
| HTML5 Browser |
360
|
Single-core only |
| PDF Viewer |
539
|
Single-core only |
| Photo Library |
406
|
Single-core only |
| Clang |
428
|
Single-core only |
| Text Processing |
247
|
Single-core only |
| Asset Compression |
456
|
Single-core only |
| HDR |
505
|
Single-core only |
| Photo Editor |
613
|
Single-core only |
| Ray Tracer |
481
|
Single-core only |
| Structure from Motion |
590
|
Single-core only |
| Game Physics |
453
|
Single-core only |
| Video Encoder |
509
|
Single-core only |
| Audio Encoder |
562
|
Single-core only |
| Video Player |
480
|
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 | 17.4 GB/s | 3 | 1.31% |
| Scale higher is better | 19.9 GB/s | 3 | 2.87% |
| Add higher is better | 21 GB/s | 3 | 2.88% |
| Triad higher is better | 21 GB/s | 3 | 2.23% |
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 | 259/s | 3 | 1.95% |
| RSA 4096 verifies higher is better | 15,876/s | 3 | 4.45% |
| SHA-256 higher is better | 261 MB/s | 3 | 0.912% |
| AES-256-GCM higher is better | 4.22 GB/s | 3 | 0.57% |
| ChaCha20-Poly1305 higher is better | 2.33 GB/s | 3 | 4.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 | 6.59 ms | 3 | 1.2% |
| Requests per second, 90th percentile higher is better | 296/s | 3 | 0.39% |
| Request latency, 99.9th percentile lower is better | 18.2 ms | 3 | 7.03% |
| Requests per second, average higher is better | 265/s | 3 | 1.25% |
Average of 3 runs. Spread is the standard deviation as a share of the average.
Disk
| Block size | Read | Write | Total |
|---|---|---|---|
| 4K | 43.6 MB/s (11,167 IOPS) | 43.7 MB/s (11,182 IOPS) | 87.3 MB/s (22,349 IOPS) |
| 64K | 792 MB/s (12,672 IOPS) | 796.2 MB/s (12,739 IOPS) | 1.55 GB/s (25,411 IOPS) |
| 512K | 1000.5 MB/s (2,001 IOPS) | 1.03 GB/s (2,107 IOPS) | 2.01 GB/s (4,108 IOPS) |
| 1M | 1.04 GB/s (1,061 IOPS) | 1.11 GB/s (1,132 IOPS) | 2.14 GB/s (2,193 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 | 954 Mbps | 344 Mbps |
| Eranium, Amsterdam, NL (100G) | IPv4 | 1.5 Gbps | 2.23 Gbps |
| Leaseweb, Singapore, SG (10G) | IPv4 | 502 Mbps | 597 Mbps |
| Clouvider, Los Angeles, CA, US (10G) | IPv4 | 1.6 Gbps | 385 Mbps |
| Leaseweb, NYC, NY, US (10G) | IPv4 | 8.64 Gbps | 2.82 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 | 2,976 | 0.336 ms |
| fdatasync | 2,998 | 0.334 ms |
| fsync | 1,535 | 0.652 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 1,730 | 0.578 ms |
| Two 8 kB writes | ||
| open_datasync | 1,541 | 0.649 ms |
| fdatasync | 2,679 | 0.373 ms |
| fsync | 1,580 | 0.633 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 854 | 1.17 ms |
| open_sync at different write sizes | ||
| 1 * 16kB open_sync write | 1,704 | 0.587 ms |
| 2 * 8kB open_sync writes | 873 | 1.15 ms |
| 4 * 4kB open_sync writes | 409 | 2.45 ms |
| 8 * 2kB open_sync writes | 154 | 6.49 ms |
| 16 * 1kB open_sync writes | 95.8 | 10.4 ms |
| fsync on a non-write descriptor | ||
| write, fsync, close | 1,203 | 0.831 ms |
| write, close, fsync | 1,429 | 0.7 ms |
| Non-synced 8 kB writes | ||
| write | 322,842 | 0.003 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 | 762 | 1.08 ms | 2.51 ms | 5.6 ms | 11.6 ms | 0 |
| Read/write (TPC-B like) | 8 | 1,878 | 3.63 ms | 8.3 ms | 15 ms | 30.6 ms | 0 |
| Read/write (TPC-B like) | 32 | 1,742 | 14.8 ms | 41.9 ms | 69.2 ms | 121 ms | 0 |
| Read only | 1 | 11,917 | 0.074 ms | 0.126 ms | 0.216 ms | 0.575 ms | 0 |
| Read only | 8 | 20,689 | 0.346 ms | 0.602 ms | 0.801 ms | 2.57 ms | 0 |
| Read only | 32 | 18,865 | 1.4 ms | 2.79 ms | 4.38 ms | 10.5 ms | 0 |
Scale 10 (1,000,000 accounts), loaded in 3.52 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 | 488 | 1.75 ms | 4.06 ms | 8.87 ms | 29.9 ms | 0 |
| Read/write (TPC-B like) | 8 | 1,413 | 4.61 ms | 11.8 ms | 23 ms | 48.5 ms | 0 |
| Read/write (TPC-B like) | 32 | 1,263 | 22.1 ms | 48.7 ms | 80.1 ms | 158 ms | 0 |
| Read only | 1 | 1,827 | 0.464 ms | 1.25 ms | 3.21 ms | 11.9 ms | 0 |
| Read only | 8 | 9,104 | 0.596 ms | 2.39 ms | 5.18 ms | 13.7 ms | 0 |
| Read only | 32 | 11,543 | 2.22 ms | 5.37 ms | 9.29 ms | 19.8 ms | 0 |
Scale 100 (10,000,000 accounts), loaded in 37.9 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 | 134 | 2,677 | 6.43 ms | 13.7 ms | 23.5 ms | 0 |
| Read/write | 8 | 343 | 6,851 | 22.3 ms | 40.4 ms | 55.8 ms | 0 |
| Read/write | 32 | 355 | 7,099 | 87.6 ms | 148 ms | 187 ms | 0 |
| Read only | 1 | 316 | 5,063 | 2.81 ms | 5.09 ms | 10.3 ms | 0 |
| Read only | 8 | 675 | 10,795 | 11.7 ms | 17 ms | 21.9 ms | 0 |
| Read only | 32 | 598 | 9,567 | 52.9 ms | 71.8 ms | 84.5 ms | 0 |
10 tables of 100,000 rows, loaded in 21.5 s. 60 s per run, one connection per thread.
Redis
memtier
| Mix | Operations/s | Hits/s | Median | p99 | p99.9 |
|---|---|---|---|---|---|
| 1:10 set:get | 31,007 | 28,188 | 1.9 ms | 6.27 ms | 14.8 ms |
| 1:1 set:get | 30,392 | 15,196 | 1.95 ms | 6.37 ms | 15.9 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 | 226 | 800 | 1,180 | 3.75 s |
| Express express-postgresjs | 3,999 | 5,337 | 13,621 | 735 ms |
| Fastify fastify-postgres | 3,833 | 5,988 | 15,567 | 262 ms |
| NestJS nestjs | 1,918 | 2,225 | 8,334 | 241 ms |
| Nuxt nuxt | 3,226 | 5,142 | 12,001 | 771 ms |
| FastAPI fastapi | 1,284 | 1,762 | 6,249 | 694 ms |
| Django django-postgresql | 440 | 551 | 1,254 | 1.26 s |
| Rails rails | 773 | 1,068 | 4,551 | 438 ms |
| Laravel laravel | 290 | 294 | 549 | 960 ms |
| Symfony symfony | 331 | 384 | 1,157 | 837 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 | 0.762 | 2.03 s | 2.24 s | 2.28 s | 0% |
| Shop page | 0.762 | 2.77 s | 2.93 s | 2.97 s | 0% |
| Category page | 0.762 | 1.65 s | 2.85 s | 2.94 s | 0% |
| Product page | 0.762 | 1.86 s | 2.15 s | 2.2 s | 0% |
| Product search | 0.762 | 1.65 s | 1.85 s | 1.88 s | 0% |
| 32 virtual users | |||||
| Home page | 0.893 | 7.24 s | 8.15 s | 8.26 s | 0% |
| Shop page | 0.893 | 9.85 s | 11.2 s | 11.3 s | 0% |
| Category page | 0.893 | 8.99 s | 10.4 s | 11 s | 0% |
| Product page | 0.516 | 7.6 s | 8.22 s | 8.35 s | 0% |
| Product search | 0.446 | 7.07 s | 7.59 s | 7.65 s | 0% |
Cart and checkout
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 8 virtual users | |||||
| Add to cart | 1.39 | 2.14 s | 2.3 s | 2.35 s | 0% |
| Cart | 1.39 | 1.73 s | 1.9 s | 1.94 s | 0% |
| Checkout | 1.39 | 1.36 s | 1.5 s | 1.61 s | 0% |
| 32 virtual users | |||||
| Add to cart | 1.4 | 7.37 s | 9.67 s | 10 s | 0% |
| Cart | 1.4 | 8.07 s | 9.32 s | 9.47 s | 0% |
| Checkout | 1.4 | 6.35 s | 7.2 s | 7.39 s | 0% |
k6 with a fixed number of virtual users, 67 to 72 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 | 0.6 | 687 ms | 986 ms | 1.25 s | 0% |
| Topic JSON | 0.308 | 366 ms | 513 ms | 521 ms | 0% |
| Home page | 0.308 | 609 ms | 770 ms | 884 ms | 0% |
| Categories page | 0.146 | 706 ms | 1.6 s | 1.82 s | 0% |
| User activity page | 0.146 | 405 ms | 815 ms | 946 ms | 0% |
| 4 virtual users | |||||
| Topic page | 1.14 | 1.47 s | 2.21 s | 3.57 s | 0% |
| Topic JSON | 0.571 | 779 ms | 1.08 s | 1.19 s | 0% |
| Home page | 0.555 | 1.3 s | 1.73 s | 2.28 s | 0% |
| Categories page | 0.317 | 1.62 s | 2.35 s | 3.2 s | 0% |
| User activity page | 0.27 | 924 ms | 1.14 s | 1.31 s | 0% |
| 16 virtual users | |||||
| Topic page | 1.06 | 2.58 s | 3.1 s | 3.46 s | 0% |
| Topic JSON | 0.53 | 1.87 s | 2.43 s | 2.45 s | 0% |
| Home page | 0.546 | 2.41 s | 3.14 s | 3.66 s | 0% |
| Categories page | 0.265 | 2.74 s | 3.33 s | 3.4 s | 0% |
| User activity page | 0.249 | 2.11 s | 2.62 s | 2.81 s | 0% |
Anonymous
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 16 virtual users | |||||
| Topic page | 22.1 | 177 ms | 532 ms | 780 ms | 0.299% |
| Topic JSON | 11.1 | 175 ms | 591 ms | 945 ms | 0.298% |
| Home page | 11.1 | 181 ms | 582 ms | 823 ms | 0.149% |
| Categories page | 5.55 | 167 ms | 549 ms | 1.22 s | 0.595% |
| User activity page | 5.5 | 595 ms | 1.19 s | 1.64 s | 0% |
k6 with a fixed number of virtual users, 61 to 64 s per level, after a 25 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 502 MB of it. The container peaked at 1,425 MB.
Ghost
Readers
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 2.95 | 99.3 ms | 131 ms | 180 ms | 0% |
| Post page | 7.36 | 48.2 ms | 75.6 ms | 104 ms | 0% |
| Tag page | 1.48 | 65.4 ms | 88.7 ms | 98.6 ms | 0% |
| Author page | 1.46 | 65.8 ms | 83.5 ms | 103 ms | 0% |
| RSS feed | 1.46 | 76.2 ms | 107 ms | 120 ms | 0% |
| 4 virtual users | |||||
| Home page | 3.74 | 291 ms | 412 ms | 490 ms | 0% |
| Post page | 9.32 | 181 ms | 283 ms | 365 ms | 0% |
| Tag page | 1.86 | 176 ms | 312 ms | 420 ms | 0% |
| Author page | 1.86 | 199 ms | 284 ms | 349 ms | 0% |
| RSS feed | 1.86 | 191 ms | 279 ms | 330 ms | 0% |
| 16 virtual users | |||||
| Home page | 3.63 | 1.11 s | 1.43 s | 1.55 s | 0% |
| Post page | 9.13 | 908 ms | 1.23 s | 1.35 s | 0% |
| Tag page | 1.83 | 593 ms | 780 ms | 884 ms | 0% |
| Author page | 1.83 | 595 ms | 832 ms | 985 ms | 0% |
| RSS feed | 1.83 | 611 ms | 810 ms | 965 ms | 0% |
Staff in Ghost Admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Post list | 1.52 | 94.5 ms | 148 ms | 175 ms | 0% |
| Post editor | 4.59 | 36 ms | 58.2 ms | 96 ms | 0% |
| Saving a draft | 4.59 | 92.1 ms | 135 ms | 176 ms | 0% |
| Member list | 1.53 | 115 ms | 180 ms | 292 ms | 0% |
| 4 virtual users | |||||
| Post list | 1.95 | 132 ms | 191 ms | 232 ms | 0% |
| Post editor | 5.88 | 65.6 ms | 94 ms | 160 ms | 0% |
| Saving a draft | 5.91 | 492 ms | 653 ms | 804 ms | 0% |
| Member list | 1.96 | 142 ms | 221 ms | 250 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. 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 384 MB and MySQL at 598 MB.
Wagtail
Visitors
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 0.493 | 269 ms | 306 ms | 432 ms | 0% |
| Blog index | 0.493 | 932 ms | 1.15 s | 1.44 s | 0% |
| Blog post | 1.45 | 83.7 ms | 130 ms | 156 ms | 0% |
| Bread page | 1.46 | 88.6 ms | 110 ms | 156 ms | 0% |
| Location page | 0.493 | 86.5 ms | 107 ms | 120 ms | 0% |
| Site search | 0.477 | 132 ms | 192 ms | 229 ms | 0% |
| 4 virtual users | |||||
| Home page | 0.928 | 616 ms | 915 ms | 1.02 s | 0% |
| Blog index | 0.944 | 1.95 s | 2.68 s | 2.89 s | 0% |
| Blog post | 2.8 | 174 ms | 296 ms | 356 ms | 0% |
| Bread page | 2.78 | 199 ms | 308 ms | 403 ms | 0% |
| Location page | 0.944 | 200 ms | 280 ms | 297 ms | 0% |
| Site search | 0.911 | 270 ms | 430 ms | 496 ms | 0% |
| 16 virtual users | |||||
| Home page | 0.853 | 2 s | 2.79 s | 3 s | 0% |
| Blog index | 0.948 | 5.18 s | 5.99 s | 6.28 s | 0% |
| Blog post | 2.57 | 1.15 s | 1.79 s | 2.05 s | 0% |
| Bread page | 2.65 | 1.22 s | 1.86 s | 2.21 s | 0% |
| Location page | 0.9 | 1.09 s | 1.8 s | 1.94 s | 0% |
| Site search | 0.869 | 1.42 s | 2.13 s | 2.79 s | 0% |
Editors in the Wagtail admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Admin dashboard | 0.191 | 298 ms | 446 ms | 542 ms | 0% |
| Page explorer | 0.415 | 1.07 s | 1.32 s | 1.38 s | 0% |
| Page editor | 0.59 | 504 ms | 779 ms | 842 ms | 0% |
| Image library | 0.191 | 206 ms | 1.13 s | 1.97 s | 0% |
| Admin page search | 0.191 | 134 ms | 306 ms | 338 ms | 0% |
| 4 virtual users | |||||
| Admin dashboard | 0.33 | 579 ms | 1.03 s | 1.11 s | 0% |
| Page explorer | 0.708 | 2.66 s | 4.36 s | 4.86 s | 0% |
| Page editor | 1.1 | 1.17 s | 1.84 s | 1.93 s | 0% |
| Image library | 0.362 | 635 ms | 1.2 s | 1.23 s | 0% |
| Admin page search | 0.33 | 240 ms | 681 ms | 700 ms | 0% |
k6 with a fixed number of virtual users, 60 to 64 s per level, after a 21 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 291 MB, Postgres at 220 MB, and Redis at 51 MB.
Advertised vs. measured
| Spec | Advertised | Measured |
|---|---|---|
| vCPU | 2 | 2 |
| CPU | Shared vCPU | 10.4% of busy CPU time stolen |
| RAM | 2 GB | 1.9 GiB |
| Storage | 80 GB SSD | 77.4 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 (Skylake, IBRS)
- CPU cores
- 2
- CPU frequency
- 2095 MHz
- AES-NI
- Yes
- VM-x/AMD-V
- Yes
- RAM reported
- 1.9 GiB
- Swap reported
- 0 MiB
- Disk reported
- 77.4 GiB
- Virtualization reported
- KVM
- CPU steal
- 10.4% of busy CPU time stolen
- Distro
- Ubuntu 24.04.1 LTS
- Kernel
- 6.8.0-51-generic
- Architecture
- x86_64
- IPv4 reachable
- Yes
- IPv6 reachable
- No
Advertised at test time
- Plan
- 2GB Standard
- Product line
- Standard VPS
- Location
- Piscataway, NJ
- vCPU
- 2 shared vCPU
- Architecture
- x86_64
- RAM
- 2 GB
- Storage
- 80 GB SSD
- Virtualization
- KVM
- Network
- Unknown
- Transfer
- 4 TB
- Port 25
- Unknown
- Monthly price at test time
- $10.00
- Hourly price at test time
- $0.015
- YABS version
- v2026-09-20
- Ran at
- Oct 13, 2026, 23:27:53 UTC
- Parser version
- 5
Run timeline
- Queued
- Oct 13, 2026, 23:24:00 UTC
- First update from the server
- Oct 13, 2026, 23:26:03 UTC
- Completed
- Oct 14, 2026, 01:17:00 UTC
- Server deleted
- Oct 14, 2026, 01:17: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 details
Loading output.
This party closed at . It's read only now.
Reconnecting. Hang tight.