RamNode 2GB Standard
Server
-
ProviderRamNode
-
Plan2GB Standard
-
LocationSeattle, WA
-
vCPU2
-
RAM2 GB
-
Storage80 GB SSD
-
NetworkUnknown
-
OS imageUbuntu 24.04 Server Cloud
-
TriggerScheduled
-
Queued atOct 14, 2026, 00:54:00 UTC
CPU
| Version | Single-core | Multi-core | Result link |
|---|---|---|---|
| Geekbench 7 | 435 | 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 |
453
|
Single-core only |
| Navigation |
586
|
Single-core only |
| HTML5 Browser |
409
|
Single-core only |
| PDF Viewer |
485
|
Single-core only |
| Photo Library |
346
|
Single-core only |
| Clang |
385
|
Single-core only |
| Text Processing |
390
|
Single-core only |
| Asset Compression |
436
|
Single-core only |
| HDR |
489
|
Single-core only |
| Photo Editor |
520
|
Single-core only |
| Ray Tracer |
504
|
Single-core only |
| Structure from Motion |
520
|
Single-core only |
| Game Physics |
317
|
Single-core only |
| Video Encoder |
381
|
Single-core only |
| Audio Encoder |
481
|
Single-core only |
| Video Player |
362
|
Single-core only |
Rank among the 151 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 | 28.8 GB/s | 3 | 0.857% |
| Scale higher is better | 17.4 GB/s | 3 | 2.88% |
| Add higher is better | 18.3 GB/s | 3 | 0.953% |
| Triad higher is better | 18.7 GB/s | 3 | 0.801% |
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 | 108/s | 3 | 5.65% |
| RSA 4096 verifies higher is better | 7,450/s | 3 | 13.1% |
| SHA-256 higher is better | 226 MB/s | 3 | 3.12% |
| AES-256-GCM higher is better | 2.43 GB/s | 3 | 3.41% |
| ChaCha20-Poly1305 higher is better | 1.64 GB/s | 3 | 17% |
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 | 10.5 ms | 3 | 0.769% |
| Requests per second, 90th percentile higher is better | 174/s | 3 | 1.84% |
| Request latency, 99.9th percentile lower is better | 54.3 ms | 3 | 15% |
| Requests per second, average higher is better | 153/s | 3 | 2.86% |
Average of 3 runs. Spread is the standard deviation as a share of the average.
Disk
| Block size | Read | Write | Total |
|---|---|---|---|
| 4K | 6 MB/s (1,526 IOPS) | 6 MB/s (1,524 IOPS) | 11.9 MB/s (3,050 IOPS) |
| 64K | 66.8 MB/s (1,069 IOPS) | 67.1 MB/s (1,074 IOPS) | 134 MB/s (2,143 IOPS) |
| 512K | 309.6 MB/s (619 IOPS) | 326.1 MB/s (652 IOPS) | 635.7 MB/s (1,271 IOPS) |
| 1M | 353.1 MB/s (353 IOPS) | 376.6 MB/s (376 IOPS) | 729.7 MB/s (729 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 | 372 Mbps | 156 Mbps |
| Eranium, Amsterdam, NL (100G) | IPv4 | 391 Mbps | 492 Mbps |
| Leaseweb, Singapore, SG (10G) | IPv4 | 429 Mbps | 251 Mbps |
| Clouvider, Los Angeles, CA, US (10G) | IPv4 | 518 Mbps | 229 Mbps |
| Leaseweb, NYC, NY, US (10G) | IPv4 | 509 Mbps | 293 Mbps |
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 | 377 | 2.65 ms |
| fdatasync | 379 | 2.64 ms |
| fsync | 173 | 5.79 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 141 | 7.08 ms |
| Two 8 kB writes | ||
| open_datasync | 194 | 5.15 ms |
| fdatasync | 347 | 2.88 ms |
| fsync | 157 | 6.36 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 80.1 | 12.5 ms |
| open_sync at different write sizes | ||
| 1 * 16kB open_sync write | 156 | 6.42 ms |
| 2 * 8kB open_sync writes | 80.9 | 12.4 ms |
| 4 * 4kB open_sync writes | 34 | 29.4 ms |
| 8 * 2kB open_sync writes | 14.2 | 70.6 ms |
| 16 * 1kB open_sync writes | 8.78 | 114 ms |
| fsync on a non-write descriptor | ||
| write, fsync, close | 159 | 6.28 ms |
| write, close, fsync | 175 | 5.72 ms |
| Non-synced 8 kB writes | ||
| write | 328,718 | 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 | 213 | 3.52 ms | 11.1 ms | 22.8 ms | 31.2 ms | 0 |
| Read/write (TPC-B like) | 8 | 443 | 14.1 ms | 42.8 ms | 68.2 ms | 110 ms | 0 |
| Read/write (TPC-B like) | 32 | 479 | 49.5 ms | 179 ms | 289 ms | 489 ms | 0 |
| Read only | 1 | 3,778 | 0.211 ms | 0.48 ms | 1.84 ms | 7.48 ms | 0 |
| Read only | 8 | 12,509 | 0.409 ms | 0.935 ms | 6.68 ms | 31.1 ms | 0 |
| Read only | 32 | 10,394 | 1.71 ms | 9.03 ms | 28.6 ms | 77.8 ms | 0 |
Scale 10 (1,000,000 accounts), loaded in 4.76 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 | 149 | 5.04 ms | 17.3 ms | 24.9 ms | n/a | 0 |
| Read/write (TPC-B like) | 8 | 342 | 18.7 ms | 53.8 ms | 77.2 ms | 126 ms | 0 |
| Read/write (TPC-B like) | 32 | 511 | 54.9 ms | 130 ms | 175 ms | 262 ms | 0 |
| Read only | 1 | 271 | 1.79 ms | 13 ms | 23.7 ms | 82.6 ms | 0 |
| Read only | 8 | 1,590 | 3.11 ms | 15.6 ms | 30.3 ms | 66.2 ms | 0 |
| Read only | 32 | 2,698 | 8.76 ms | 30.9 ms | 48 ms | 83.5 ms | 0 |
Scale 100 (10,000,000 accounts), loaded in 59.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 | 30.5 | 609 | 27.7 ms | 70.5 ms | 109 ms | 0 |
| Read/write | 8 | 94.3 | 1,886 | 73.1 ms | 174 ms | 277 ms | 0 |
| Read/write | 32 | 145 | 2,894 | 200 ms | 397 ms | 530 ms | 0 |
| Read only | 1 | 110 | 1,765 | 7.84 ms | 20 ms | 29.7 ms | 0 |
| Read only | 8 | 432 | 6,906 | 14.7 ms | 41.9 ms | 89.2 ms | 0 |
| Read only | 32 | 421 | 6,730 | 68.1 ms | 142 ms | 249 ms | 0 |
10 tables of 100,000 rows, loaded in 48.3 s. 60 s per run, one connection per thread.
Redis
memtier
| Mix | Operations/s | Hits/s | Median | p99 | p99.9 |
|---|---|---|---|---|---|
| 1:10 set:get | 13,700 | 12,454 | 3.36 ms | 24.7 ms | 46.6 ms |
| 1:1 set:get | 13,833 | 6,916 | 3.41 ms | 23.3 ms | 44.3 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 | 125 | 447 | 537 | 7.28 s |
| Express express-postgresjs | 2,364 | 2,901 | 6,226 | 499 ms |
| Fastify fastify-postgres | 2,499 | 3,534 | 5,329 | 1.24 s |
| NestJS nestjs | 978 | 1,168 | 3,968 | 732 ms |
| Nuxt nuxt | 1,753 | 2,615 | 4,764 | 2.64 s |
| FastAPI fastapi | 893 | 1,165 | 3,822 | 1.23 s |
| Django django-postgresql | 234 | 280 | 647 | 1.37 s |
| Rails rails | 384 | 568 | 2,183 | 1.5 s |
| Laravel laravel | 182 | 227 | 313 | 2.03 s |
| Symfony symfony | 245 | 271 | 738 | 1.6 s |
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.589 | 2.55 s | 3.33 s | 3.52 s | 0% |
| Shop page | 0.589 | 3.36 s | 3.94 s | 4.25 s | 0% |
| Category page | 0.589 | 2.1 s | 3.07 s | 3.46 s | 0% |
| Product page | 0.589 | 2.28 s | 3.47 s | 3.61 s | 0% |
| Product search | 0.589 | 1.95 s | 3.55 s | 3.88 s | 0% |
| 32 virtual users | |||||
| Home page | 0.812 | 10.7 s | 14.5 s | 14.9 s | 0% |
| Shop page | 0.441 | 12.8 s | 15 s | 15.5 s | 0% |
| Category page | 0.441 | 12.5 s | 14.6 s | 15.3 s | 0% |
| Product page | 0.441 | 8.97 s | 9.55 s | 9.63 s | 0% |
| Product search | 0.441 | 8.81 s | 9.2 s | 9.23 s | 0% |
Cart and checkout
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 8 virtual users | |||||
| Add to cart | 1.03 | 2.68 s | 3.43 s | 3.93 s | 0% |
| Cart | 1.03 | 2.17 s | 3.29 s | 3.86 s | 0% |
| Checkout | 1.03 | 1.63 s | 2.15 s | 2.45 s | 0% |
| 32 virtual users | |||||
| Add to cart | 1.26 | 10.6 s | 14.1 s | 14.5 s | 0% |
| Cart | 0.877 | 9.9 s | 11.6 s | 11.9 s | 0% |
| Checkout | 0.877 | 7.81 s | 9.3 s | 9.74 s | 0% |
k6 with a fixed number of virtual users, 68 to 73 s per level. The error rate counts responses that weren't a 200.
Discourse
Signed in
Failed: k6 summary at 4 virtual users didn't parse: k6 recorded no requests for step user_activity
Anonymous
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 16 virtual users | |||||
| Topic page | 16.6 | 262 ms | 702 ms | 937 ms | 1.25% |
| Topic JSON | 8.38 | 268 ms | 679 ms | 897 ms | 0.766% |
| Home page | 8.35 | 272 ms | 705 ms | 995 ms | 0.577% |
| Categories page | 4.19 | 263 ms | 621 ms | 1.05 s | 1.53% |
| User activity page | 4.21 | 746 ms | 1.5 s | 1.98 s | 0.382% |
k6 with a fixed number of virtual users, 62 s per level, after a 28 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 386 MB of it. The container peaked at 1,477 MB.
Ghost
Readers
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 1.27 | 216 ms | 364 ms | 500 ms | 0% |
| Post page | 3.14 | 106 ms | 224 ms | 294 ms | 0% |
| Tag page | 0.628 | 146 ms | 275 ms | 442 ms | 0% |
| Author page | 0.628 | 131 ms | 265 ms | 275 ms | 0% |
| RSS feed | 0.628 | 164 ms | 349 ms | 391 ms | 0% |
| 4 virtual users | |||||
| Home page | 1.62 | 613 ms | 960 ms | 1.08 s | 0% |
| Post page | 4.02 | 448 ms | 830 ms | 1.01 s | 0% |
| Tag page | 0.844 | 353 ms | 545 ms | 742 ms | 0% |
| Author page | 0.794 | 404 ms | 676 ms | 741 ms | 0% |
| RSS feed | 0.794 | 404 ms | 692 ms | 717 ms | 0% |
| 16 virtual users | |||||
| Home page | 1.64 | 2.35 s | 3.26 s | 3.59 s | 0% |
| Post page | 4.11 | 2.03 s | 2.77 s | 3.54 s | 0% |
| Tag page | 0.828 | 1.33 s | 2 s | 2.54 s | 0% |
| Author page | 0.796 | 1.29 s | 1.93 s | 2.45 s | 0% |
| RSS feed | 0.812 | 1.37 s | 2.12 s | 2.6 s | 0% |
Staff in Ghost Admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Post list | 0.588 | 237 ms | 400 ms | 570 ms | 0% |
| Post editor | 1.81 | 80.9 ms | 147 ms | 210 ms | 0% |
| Saving a draft | 1.81 | 239 ms | 362 ms | 479 ms | 0% |
| Member list | 0.604 | 291 ms | 503 ms | 711 ms | 0% |
| 4 virtual users | |||||
| Post list | 0.788 | 282 ms | 427 ms | 507 ms | 0% |
| Post editor | 2.43 | 113 ms | 215 ms | 260 ms | 0% |
| Saving a draft | 2.45 | 1.24 s | 1.76 s | 1.96 s | 0% |
| Member list | 0.788 | 331 ms | 531 ms | 585 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. 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 367 MB and MySQL at 598 MB.
Wagtail
Visitors
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 0.314 | 403 ms | 536 ms | 552 ms | 0% |
| Blog index | 0.314 | 1.53 s | 1.74 s | 1.93 s | 0% |
| Blog post | 0.909 | 123 ms | 248 ms | 298 ms | 0% |
| Bread page | 0.926 | 141 ms | 182 ms | 194 ms | 0% |
| Location page | 0.314 | 132 ms | 178 ms | 291 ms | 0% |
| Site search | 0.298 | 211 ms | 356 ms | 363 ms | 0% |
| 4 virtual users | |||||
| Home page | 0.514 | 1.07 s | 1.52 s | 1.65 s | 0% |
| Blog index | 0.546 | 3.68 s | 5.42 s | 5.57 s | 0% |
| Blog post | 1.54 | 295 ms | 566 ms | 832 ms | 0% |
| Bread page | 1.58 | 315 ms | 579 ms | 648 ms | 0% |
| Location page | 0.563 | 308 ms | 552 ms | 727 ms | 0% |
| Site search | 0.498 | 471 ms | 879 ms | 939 ms | 0% |
| 16 virtual users | |||||
| Home page | 0.435 | 4.09 s | 5.91 s | 6.05 s | 0% |
| Blog index | 0.483 | 10.2 s | 12.5 s | 13.3 s | 0% |
| Blog post | 1.34 | 2.31 s | 3.59 s | 4.09 s | 0% |
| Bread page | 1.34 | 2.3 s | 4.44 s | 5.6 s | 0% |
| Location page | 0.451 | 2.33 s | 4.57 s | 5.25 s | 0% |
| Site search | 0.451 | 2.41 s | 4.05 s | 4.3 s | 0% |
Editors in the Wagtail admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Admin dashboard | 0.111 | 462 ms | 729 ms | 791 ms | 0% |
| Page explorer | 0.253 | 1.65 s | 2.42 s | 3.16 s | 0% |
| Page editor | 0.348 | 801 ms | 1.25 s | 1.62 s | 0% |
| Image library | 0.111 | 364 ms | 2.53 s | 3.21 s | 0% |
| Admin page search | 0.111 | 165 ms | 355 ms | 359 ms | 0% |
| 4 virtual users | |||||
| Admin dashboard | 0.191 | 1.13 s | 1.73 s | 1.86 s | 0% |
| Page explorer | 0.397 | 4.25 s | 7.11 s | 7.86 s | 0% |
| Page editor | 0.62 | 1.87 s | 2.96 s | 3.29 s | 0% |
| Image library | 0.223 | 975 ms | 1.63 s | 1.68 s | 0% |
| Admin page search | 0.191 | 471 ms | 995 ms | 1.12 s | 0% |
k6 with a fixed number of virtual users, 60 to 63 s per level, after a 22 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 285 MB, Postgres at 211 MB, and Redis at 50 MB.
Advertised vs. measured
| Spec | Advertised | Measured |
|---|---|---|
| vCPU | 2 | 2 |
| CPU | Shared vCPU | 50% 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 Core Processor (Haswell, no TSX, IBRS)
- CPU cores
- 2
- CPU frequency
- 2400 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
- 50% 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
- Yes
Advertised at test time
- Plan
- 2GB Standard
- Product line
- Standard VPS
- Location
- Seattle, WA
- 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 14, 2026, 00:57:06 UTC
- Parser version
- 5
Run timeline
- Queued
- Oct 14, 2026, 00:54:00 UTC
- First update from the server
- Oct 14, 2026, 00:55:36 UTC
- Completed
- Oct 14, 2026, 04:02:00 UTC
- Server deleted
- Oct 14, 2026, 04:02:00 UTC
- Cost of this run
- $0.047
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.