RamNode 2GB Premium
Server
-
ProviderRamNode
-
Plan2GB Premium
-
LocationLos Angeles, CA
-
vCPU2
-
RAM2 GB
-
Storage80 GB NVMe
-
NetworkUnknown
-
OS imageUbuntu 24.04 Server Cloud
-
TriggerScheduled
-
Queued atOct 16, 2026, 11:19:00 UTC
CPU
| Version | Single-core | Multi-core | Result link |
|---|---|---|---|
| Geekbench 7 | 868 | 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,001
|
Single-core only |
| Navigation |
1,118
|
Single-core only |
| HTML5 Browser |
713
|
Single-core only |
| PDF Viewer |
1,012
|
Single-core only |
| Photo Library |
783
|
Single-core only |
| Clang |
887
|
Single-core only |
| Text Processing |
546
|
Single-core only |
| Asset Compression |
804
|
Single-core only |
| HDR |
916
|
Single-core only |
| Photo Editor |
1,096
|
Single-core only |
| Ray Tracer |
797
|
Single-core only |
| Structure from Motion |
1,008
|
Single-core only |
| Game Physics |
814
|
Single-core only |
| Video Encoder |
792
|
Single-core only |
| Audio Encoder |
994
|
Single-core only |
| Video Player |
813
|
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 | 20.8 GB/s | 3 | 0.863% |
| Scale higher is better | 21 GB/s | 3 | 2.44% |
| Add higher is better | 22.9 GB/s | 3 | 2.78% |
| Triad higher is better | 23.1 GB/s | 3 | 1.33% |
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 | 464/s | 3 | 0.665% |
| RSA 4096 verifies higher is better | 31,511/s | 3 | 0.724% |
| SHA-256 higher is better | 483 MB/s | 3 | 2.56% |
| AES-256-GCM higher is better | 7.62 GB/s | 3 | 1.01% |
| ChaCha20-Poly1305 higher is better | 4.25 GB/s | 3 | 2.12% |
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 | 3.83 ms | 3 | 0.836% |
| Requests per second, 90th percentile higher is better | 518/s | 3 | 0.589% |
| Request latency, 99.9th percentile lower is better | 8.03 ms | 3 | 3.58% |
| Requests per second, average higher is better | 503/s | 3 | 0.876% |
Average of 3 runs. Spread is the standard deviation as a share of the average.
Disk
| Block size | Read | Write | Total |
|---|---|---|---|
| 4K | 181.1 MB/s (46,356 IOPS) | 181.6 MB/s (46,478 IOPS) | 362.6 MB/s (92,834 IOPS) |
| 64K | 342.9 MB/s (5,486 IOPS) | 344.7 MB/s (5,515 IOPS) | 687.6 MB/s (11,001 IOPS) |
| 512K | 325.4 MB/s (650 IOPS) | 342.7 MB/s (685 IOPS) | 668.2 MB/s (1,335 IOPS) |
| 1M | 411.4 MB/s (411 IOPS) | 438.8 MB/s (438 IOPS) | 850.1 MB/s (849 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.08 Gbps | 1.29 Gbps |
| Eranium, Amsterdam, NL (100G) | IPv4 | 1.38 Gbps | 1.63 Gbps |
| Leaseweb, Singapore, SG (10G) | IPv4 | 770 Mbps | 1.37 Gbps |
| Clouvider, Los Angeles, CA, US (10G) | IPv4 | 8.88 Gbps | 3.49 Gbps |
| Leaseweb, NYC, NY, US (10G) | IPv4 | 1.8 Gbps | 3.1 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 | 5,658 | 0.177 ms |
| fdatasync | 5,463 | 0.183 ms |
| fsync | 2,740 | 0.365 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 3,804 | 0.263 ms |
| Two 8 kB writes | ||
| open_datasync | 2,824 | 0.354 ms |
| fdatasync | 4,824 | 0.207 ms |
| fsync | 3,277 | 0.305 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 1,894 | 0.528 ms |
| open_sync at different write sizes | ||
| 1 * 16kB open_sync write | 3,306 | 0.302 ms |
| 2 * 8kB open_sync writes | 1,802 | 0.555 ms |
| 4 * 4kB open_sync writes | 996 | 1 ms |
| 8 * 2kB open_sync writes | 521 | 1.92 ms |
| 16 * 1kB open_sync writes | 237 | 4.22 ms |
| fsync on a non-write descriptor | ||
| write, fsync, close | 3,017 | 0.331 ms |
| write, close, fsync | 2,842 | 0.352 ms |
| Non-synced 8 kB writes | ||
| write | 610,217 | 0.002 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,607 | 0.585 ms | 0.828 ms | 1.3 ms | 3.08 ms | 0 |
| Read/write (TPC-B like) | 8 | 3,605 | 1.99 ms | 3.75 ms | 6.15 ms | 15.5 ms | 0 |
| Read/write (TPC-B like) | 32 | 3,433 | 7.5 ms | 21.3 ms | 36.2 ms | 71.5 ms | 0 |
| Read only | 1 | 21,325 | 0.044 ms | 0.068 ms | 0.084 ms | 0.157 ms | 0 |
| Read only | 8 | 37,193 | 0.195 ms | 0.338 ms | 0.432 ms | 0.951 ms | 0 |
| Read only | 32 | 37,233 | 0.738 ms | 1.32 ms | 1.81 ms | 3.3 ms | 0 |
Scale 10 (1,000,000 accounts), loaded in 2.35 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 | 945 | 0.98 ms | 1.56 ms | 3.15 ms | 11.4 ms | 0 |
| Read/write (TPC-B like) | 8 | 2,736 | 2.53 ms | 5.75 ms | 10 ms | 18.6 ms | 0 |
| Read/write (TPC-B like) | 32 | 3,152 | 9.32 ms | 16.9 ms | 25.3 ms | 41.6 ms | 0 |
| Read only | 1 | 4,762 | 0.212 ms | 0.396 ms | 1.05 ms | 3.59 ms | 0 |
| Read only | 8 | 20,051 | 0.302 ms | 0.849 ms | 2.02 ms | 4.83 ms | 0 |
| Read only | 32 | 22,602 | 1.19 ms | 2.48 ms | 3.76 ms | 6.65 ms | 0 |
Scale 100 (10,000,000 accounts), loaded in 24.4 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 | 236 | 4,724 | 3.68 ms | 6.55 ms | 17 ms | 0 |
| Read/write | 8 | 590 | 11,796 | 12.5 ms | 24.8 ms | 37.6 ms | 0 |
| Read/write | 32 | 627 | 12,532 | 50.1 ms | 83 ms | 105 ms | 0 |
| Read only | 1 | 624 | 9,977 | 1.55 ms | 2.11 ms | 3.02 ms | 0 |
| Read only | 8 | 1,154 | 18,467 | 6.79 ms | 9.73 ms | 11.2 ms | 0 |
| Read only | 32 | 1,075 | 17,195 | 29.7 ms | 38.9 ms | 43.4 ms | 0 |
10 tables of 100,000 rows, loaded in 13.6 s. 60 s per run, one connection per thread.
Redis
memtier
| Mix | Operations/s | Hits/s | Median | p99 | p99.9 |
|---|---|---|---|---|---|
| 1:10 set:get | 60,287 | 54,806 | 0.799 ms | 3.15 ms | 5.31 ms |
| 1:1 set:get | 58,892 | 29,446 | 0.823 ms | 3.17 ms | 5.86 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 | 394 | 1,475 | 2,042 | 1.17 s |
| Express express-postgresjs | 5,757 | 7,617 | 22,989 | 184 ms |
| Fastify fastify-postgres | 5,578 | 8,596 | 25,619 | 264 ms |
| NestJS nestjs | 3,323 | 3,877 | 14,271 | 131 ms |
| Nuxt nuxt | 4,837 | 7,955 | 23,349 | 143 ms |
| FastAPI fastapi | 2,437 | 3,224 | 11,569 | 488 ms |
| Django django-postgresql | 895 | 1,130 | 2,400 | 610 ms |
| Rails rails | 1,422 | 1,991 | 7,707 | 218 ms |
| Laravel laravel | 517 | 558 | 997 | 538 ms |
| Symfony symfony | 593 | 654 | 1,920 | 462 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.25 | 1.27 s | 1.4 s | 1.46 s | 0% |
| Shop page | 1.25 | 1.71 s | 1.87 s | 1.91 s | 0% |
| Category page | 1.25 | 1.09 s | 1.7 s | 1.75 s | 0% |
| Product page | 1.25 | 1.14 s | 1.3 s | 1.37 s | 0% |
| Product search | 1.25 | 1.02 s | 1.2 s | 1.31 s | 0% |
| 32 virtual users | |||||
| Home page | 1.35 | 4.58 s | 5.22 s | 5.32 s | 0% |
| Shop page | 1.35 | 6.14 s | 7.13 s | 7.26 s | 0% |
| Category page | 1.35 | 5.42 s | 6.33 s | 6.66 s | 0% |
| Product page | 1.11 | 4.69 s | 5.19 s | 5.33 s | 0% |
| Product search | 0.902 | 4.34 s | 4.61 s | 4.82 s | 0% |
Cart and checkout
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 8 virtual users | |||||
| Add to cart | 2.23 | 1.39 s | 1.49 s | 1.55 s | 0% |
| Cart | 2.23 | 1.1 s | 1.25 s | 1.3 s | 0% |
| Checkout | 2.23 | 892 ms | 974 ms | 1.02 s | 0% |
| 32 virtual users | |||||
| Add to cart | 2.4 | 4.55 s | 5.55 s | 5.75 s | 0% |
| Cart | 2.4 | 4.73 s | 5.25 s | 5.44 s | 0% |
| Checkout | 2.4 | 3.75 s | 4.29 s | 4.41 s | 0% |
k6 with a fixed number of virtual users, 64 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 | 1.18 | 357 ms | 540 ms | 927 ms | 0% |
| Topic JSON | 0.589 | 184 ms | 224 ms | 389 ms | 0% |
| Home page | 0.605 | 329 ms | 462 ms | 761 ms | 0% |
| Categories page | 0.295 | 369 ms | 470 ms | 525 ms | 0% |
| User activity page | 0.295 | 215 ms | 412 ms | 468 ms | 0% |
| 4 virtual users | |||||
| Topic page | 2.18 | 807 ms | 981 ms | 1.47 s | 0% |
| Topic JSON | 1.11 | 416 ms | 521 ms | 537 ms | 0% |
| Home page | 1.08 | 705 ms | 894 ms | 1.35 s | 0% |
| Categories page | 0.57 | 841 ms | 1.25 s | 1.5 s | 0% |
| User activity page | 0.538 | 486 ms | 878 ms | 1.47 s | 0% |
| 16 virtual users | |||||
| Topic page | 1.96 | 1.95 s | 2.49 s | 2.69 s | 0% |
| Topic JSON | 1.01 | 1.57 s | 2.11 s | 2.31 s | 0% |
| Home page | 1.03 | 1.86 s | 2.24 s | 2.88 s | 0% |
| Categories page | 0.514 | 2.02 s | 2.39 s | 2.56 s | 0% |
| User activity page | 0.498 | 1.58 s | 1.94 s | 1.99 s | 0% |
Anonymous
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 16 virtual users | |||||
| Topic page | 44.6 | 103 ms | 244 ms | 294 ms | 0% |
| Topic JSON | 22.3 | 99.2 ms | 234 ms | 306 ms | 0% |
| Home page | 22.3 | 102 ms | 234 ms | 299 ms | 0% |
| Categories page | 11.2 | 103 ms | 247 ms | 310 ms | 0% |
| User activity page | 11.1 | 319 ms | 469 ms | 660 ms | 0% |
k6 with a fixed number of virtual users, 60 to 62 s per level, after a 22 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 509 MB of it. The container peaked at 1,556 MB.
Ghost
Readers
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 5.36 | 53.3 ms | 69.7 ms | 98.9 ms | 0% |
| Post page | 13.4 | 27.2 ms | 36.1 ms | 47.5 ms | 0% |
| Tag page | 2.68 | 37.2 ms | 47.7 ms | 73.5 ms | 0% |
| Author page | 2.66 | 36.1 ms | 48.3 ms | 64.5 ms | 0% |
| RSS feed | 2.66 | 44.1 ms | 57.6 ms | 76.8 ms | 0% |
| 4 virtual users | |||||
| Home page | 6.47 | 163 ms | 219 ms | 308 ms | 0% |
| Post page | 16.2 | 109 ms | 166 ms | 223 ms | 0% |
| Tag page | 3.24 | 104 ms | 141 ms | 213 ms | 0% |
| Author page | 3.26 | 103 ms | 146 ms | 193 ms | 0% |
| RSS feed | 3.23 | 115 ms | 180 ms | 231 ms | 0% |
| 16 virtual users | |||||
| Home page | 6.58 | 611 ms | 746 ms | 829 ms | 0% |
| Post page | 16.4 | 508 ms | 636 ms | 699 ms | 0% |
| Tag page | 3.29 | 331 ms | 441 ms | 525 ms | 0% |
| Author page | 3.29 | 334 ms | 447 ms | 508 ms | 0% |
| RSS feed | 3.26 | 343 ms | 454 ms | 548 ms | 0% |
Staff in Ghost Admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Post list | 2.95 | 51.6 ms | 76.6 ms | 120 ms | 0% |
| Post editor | 8.87 | 18.3 ms | 26.1 ms | 40.2 ms | 0% |
| Saving a draft | 8.86 | 47.5 ms | 61.5 ms | 90.7 ms | 0% |
| Member list | 2.95 | 64.2 ms | 81.3 ms | 93.4 ms | 0% |
| 4 virtual users | |||||
| Post list | 3.69 | 68.5 ms | 88.8 ms | 134 ms | 0% |
| Post editor | 11.1 | 32.3 ms | 44.1 ms | 66.8 ms | 0% |
| Saving a draft | 11.1 | 263 ms | 360 ms | 431 ms | 0% |
| Member list | 3.72 | 77 ms | 101 ms | 185 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 392 MB and MySQL at 596 MB.
Wagtail
Visitors
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 1.03 | 130 ms | 147 ms | 191 ms | 0% |
| Blog index | 1.01 | 443 ms | 464 ms | 504 ms | 0% |
| Blog post | 3.04 | 42.7 ms | 64.6 ms | 69.6 ms | 0% |
| Bread page | 3.04 | 46.5 ms | 53.7 ms | 62.6 ms | 0% |
| Location page | 1.01 | 44.3 ms | 52.4 ms | 57.2 ms | 0% |
| Site search | 1.01 | 75.1 ms | 121 ms | 127 ms | 0% |
| 4 virtual users | |||||
| Home page | 1.71 | 341 ms | 472 ms | 504 ms | 0% |
| Blog index | 1.71 | 1.07 s | 1.55 s | 1.75 s | 0% |
| Blog post | 5.09 | 94.6 ms | 159 ms | 190 ms | 0% |
| Bread page | 5.09 | 105 ms | 151 ms | 168 ms | 0% |
| Location page | 1.71 | 101 ms | 162 ms | 180 ms | 0% |
| Site search | 1.69 | 141 ms | 286 ms | 406 ms | 0% |
| 16 virtual users | |||||
| Home page | 1.57 | 1.13 s | 1.64 s | 1.77 s | 0% |
| Blog index | 1.7 | 2.84 s | 3.4 s | 3.82 s | 0% |
| Blog post | 4.81 | 613 ms | 1.08 s | 1.45 s | 0% |
| Bread page | 4.84 | 635 ms | 1.17 s | 1.49 s | 0% |
| Location page | 1.64 | 630 ms | 1.07 s | 1.2 s | 0% |
| Site search | 1.64 | 747 ms | 1.21 s | 1.41 s | 0% |
Editors in the Wagtail admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Admin dashboard | 0.376 | 143 ms | 177 ms | 185 ms | 0% |
| Page explorer | 0.784 | 579 ms | 795 ms | 983 ms | 0% |
| Page editor | 1.18 | 276 ms | 369 ms | 486 ms | 0% |
| Image library | 0.392 | 106 ms | 125 ms | 989 ms | 0% |
| Admin page search | 0.376 | 85.8 ms | 146 ms | 190 ms | 0% |
| 4 virtual users | |||||
| Admin dashboard | 0.679 | 364 ms | 755 ms | 865 ms | 0% |
| Page explorer | 1.33 | 1.33 s | 2.19 s | 2.36 s | 0% |
| Page editor | 2.01 | 641 ms | 1.16 s | 1.35 s | 0% |
| Image library | 0.679 | 315 ms | 665 ms | 718 ms | 0% |
| Admin page search | 0.679 | 166 ms | 414 ms | 555 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. 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 293 MB, Postgres at 213 MB, and Redis at 52 MB.
Advertised vs. measured
| Spec | Advertised | Measured |
|---|---|---|
| vCPU | 2 | 2 |
| CPU | Shared vCPU | 1.3% of busy CPU time stolen |
| RAM | 2 GB | 1.9 GiB |
| Storage | 80 GB NVMe | 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
- 3492 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
- 1.3% 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 Premium
- Product line
- Premium VPS
- Location
- Los Angeles, CA
- vCPU
- 2 shared vCPU
- Architecture
- x86_64
- RAM
- 2 GB
- Storage
- 80 GB NVMe
- Virtualization
- KVM
- Network
- Unknown
- Transfer
- 6 TB
- Port 25
- Unknown
- Monthly price at test time
- $14.00
- Hourly price at test time
- $0.021
- YABS version
- v2026-09-20
- Ran at
- Oct 16, 2026, 11:19:54 UTC
- Parser version
- 5
Run timeline
- Queued
- Oct 16, 2026, 11:19:00 UTC
- Server created
- Oct 16, 2026, 11:19:46 UTC
- First update from the server
- Oct 16, 2026, 11:19:46 UTC
- Completed
- Oct 16, 2026, 12:55:00 UTC
- Server deleted
- Oct 16, 2026, 12:55:00 UTC
- Cost of this run
- $0.034
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.