LunaNode s.2 4 vCPU / 2 GB
Server
-
ProviderLunaNode
-
Plans.2 4 vCPU / 2 GB
-
LocationToronto
-
vCPU4
-
RAM2 GB
-
Storage35 GB SSD
-
NetworkUnknown
-
OS imageUbuntu 24.04 64-bit (template)
-
TriggerScheduled
-
Queued atOct 13, 2026, 19:07:00 UTC
CPU
| Version | Single-core | Multi-core | Result link |
|---|---|---|---|
| Geekbench 7 | 894 | Skipped | Geekbench Browser |
Multi-core was skipped because Geekbench 7 needs about 4.2 GB of free memory to run 4 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 |
959
|
Single-core only |
| Navigation |
1,089
|
Single-core only |
| HTML5 Browser |
854
|
Single-core only |
| PDF Viewer |
980
|
Single-core only |
| Photo Library |
696
|
Single-core only |
| Clang |
763
|
Single-core only |
| Text Processing |
985
|
Single-core only |
| Asset Compression |
1,042
|
Single-core only |
| HDR |
840
|
Single-core only |
| Photo Editor |
883
|
Single-core only |
| Ray Tracer |
1,033
|
Single-core only |
| Structure from Motion |
841
|
Single-core only |
| Game Physics |
936
|
Single-core only |
| Video Encoder |
807
|
Single-core only |
| Audio Encoder |
924
|
Single-core only |
| Video Player |
774
|
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 | 48.2 GB/s | 3 | 0.89% |
| Scale higher is better | 32 GB/s | 3 | 1.72% |
| Add higher is better | 34 GB/s | 3 | 1.16% |
| Triad higher is better | 34.6 GB/s | 3 | 1.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 | 901/s | 3 | 0.739% |
| RSA 4096 verifies higher is better | 58,705/s | 3 | 0.594% |
| SHA-256 higher is better | 991 MB/s | 3 | 1.1% |
| AES-256-GCM higher is better | 11.1 GB/s | 3 | 1.21% |
| ChaCha20-Poly1305 higher is better | 5.96 GB/s | 3 | 1.08% |
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 | 4.08 ms | 3 | 0.196% |
| Requests per second, 90th percentile higher is better | 944/s | 3 | 0.122% |
| Request latency, 99.9th percentile lower is better | 11.8 ms | 3 | 6.38% |
| Requests per second, average higher is better | 917/s | 3 | 0.945% |
Average of 3 runs. Spread is the standard deviation as a share of the average.
Disk
| Block size | Read | Write | Total |
|---|---|---|---|
| 4K | 162.6 MB/s (41,628 IOPS) | 163 MB/s (41,737 IOPS) | 325.6 MB/s (83,365 IOPS) |
| 64K | 1.72 GB/s (28,174 IOPS) | 1.73 GB/s (28,322 IOPS) | 3.45 GB/s (56,496 IOPS) |
| 512K | 1.83 GB/s (3,753 IOPS) | 1.93 GB/s (3,952 IOPS) | 3.76 GB/s (7,705 IOPS) |
| 1M | 1.89 GB/s (1,933 IOPS) | 2.01 GB/s (2,062 IOPS) | 3.9 GB/s (3,995 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 | 957 Mbps | 172 Mbps |
| Eranium, Amsterdam, NL (100G) | IPv4 | 1.24 Gbps | 624 Mbps |
| Leaseweb, Singapore, SG (10G) | IPv4 | 685 Mbps | 347 Mbps |
| Clouvider, Los Angeles, CA, US (10G) | IPv4 | 1.19 Gbps | 443 Mbps |
| Leaseweb, NYC, NY, US (10G) | IPv4 | 1.51 Gbps | 636 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 | 4,360 | 0.229 ms |
| fdatasync | 4,313 | 0.232 ms |
| fsync | 2,357 | 0.424 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 3,170 | 0.315 ms |
| Two 8 kB writes | ||
| open_datasync | 2,305 | 0.434 ms |
| fdatasync | 3,730 | 0.268 ms |
| fsync | 2,128 | 0.47 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 1,461 | 0.684 ms |
| open_sync at different write sizes | ||
| 1 * 16kB open_sync write | 2,643 | 0.378 ms |
| 2 * 8kB open_sync writes | 1,509 | 0.662 ms |
| 4 * 4kB open_sync writes | 723 | 1.38 ms |
| 8 * 2kB open_sync writes | 412 | 2.43 ms |
| 16 * 1kB open_sync writes | 209 | 4.78 ms |
| fsync on a non-write descriptor | ||
| write, fsync, close | 2,611 | 0.383 ms |
| write, close, fsync | 2,558 | 0.391 ms |
| Non-synced 8 kB writes | ||
| write | 296,509 | 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 | 1,104 | 0.865 ms | 1.15 ms | 1.5 ms | 7.57 ms | 0 |
| Read/write (TPC-B like) | 8 | 3,999 | 1.79 ms | 3.32 ms | 4.88 ms | 10.5 ms | 0 |
| Read/write (TPC-B like) | 32 | 4,501 | 5.58 ms | 16.3 ms | 28 ms | 56.7 ms | 0 |
| Read only | 1 | 13,737 | 0.067 ms | 0.099 ms | 0.127 ms | 0.208 ms | 0 |
| Read only | 8 | 48,408 | 0.152 ms | 0.27 ms | 0.341 ms | 0.617 ms | 0 |
| Read only | 32 | 54,002 | 0.524 ms | 0.835 ms | 1.09 ms | 2.55 ms | 0 |
Scale 10 (1,000,000 accounts), loaded in 2.59 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 | 849 | 1.12 ms | 1.53 ms | 2.4 ms | 8.05 ms | 0 |
| Read/write (TPC-B like) | 8 | 3,092 | 2.3 ms | 4.42 ms | 8.26 ms | 16.1 ms | 0 |
| Read/write (TPC-B like) | 32 | 4,204 | 6.7 ms | 13.6 ms | 20.9 ms | 34.7 ms | 0 |
| Read only | 1 | 4,635 | 0.208 ms | 0.368 ms | 0.544 ms | 2.29 ms | 0 |
| Read only | 8 | 27,374 | 0.24 ms | 0.567 ms | 0.909 ms | 3.26 ms | 0 |
| Read only | 32 | 32,481 | 0.832 ms | 1.78 ms | 3.09 ms | 8.13 ms | 0 |
Scale 100 (10,000,000 accounts), loaded in 28 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 | 229 | 4,577 | 3.96 ms | 6.21 ms | 11.9 ms | 0 |
| Read/write | 8 | 849 | 16,971 | 8.58 ms | 15 ms | 23.1 ms | 0 |
| Read/write | 32 | 960 | 19,199 | 30.3 ms | 58.9 ms | 77.2 ms | 0 |
| Read only | 1 | 572 | 9,156 | 1.7 ms | 2.07 ms | 2.52 ms | 0 |
| Read only | 8 | 1,955 | 31,287 | 4.03 ms | 5.99 ms | 7.04 ms | 0 |
| Read only | 32 | 1,797 | 28,754 | 17.6 ms | 23.5 ms | 27.7 ms | 0 |
10 tables of 100,000 rows, loaded in 7.8 s. 60 s per run, one connection per thread.
Redis
memtier
| Mix | Operations/s | Hits/s | Median | p99 | p99.9 |
|---|---|---|---|---|---|
| 1:10 set:get | 43,453 | 39,502 | 1.42 ms | 2.67 ms | 4.1 ms |
| 1:1 set:get | 42,812 | 21,406 | 1.43 ms | 2.7 ms | 4.26 ms |
1,000,000 keys of 32 bytes. 64 connections over 4 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 | 548 | 1,920 | 2,350 | 720 ms |
| Express express-postgresjs | 12,206 | 14,864 | 35,430 | 55.2 ms |
| Fastify fastify-postgres | 11,995 | 16,609 | 39,806 | 54.6 ms |
| NestJS nestjs | 890 | 1,049 | 13,615 | 400 ms |
| Nuxt nuxt | 2,097 | 2,563 | 4,665 | 295 ms |
| FastAPI fastapi | 1,241 | 1,013 | 3,517 | 1.1 s |
| Django django-postgresql | 1,810 | 2,024 | 4,432 | 286 ms |
| Rails rails | 559 | 731 | 13,900 | 709 ms |
| Laravel laravel | 189 | 206 | 366 | 1.59 s |
| Symfony symfony | 233 | 257 | 663 | 1.39 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 | 3.5 | 459 ms | 584 ms | 623 ms | 0% |
| Shop page | 3.5 | 594 ms | 765 ms | 793 ms | 0% |
| Category page | 3.5 | 390 ms | 626 ms | 722 ms | 0% |
| Product page | 3.5 | 420 ms | 556 ms | 589 ms | 0% |
| Product search | 3.5 | 369 ms | 500 ms | 541 ms | 0% |
| 32 virtual users | |||||
| Home page | 3.5 | 1.71 s | 2.14 s | 2.28 s | 0% |
| Shop page | 3.5 | 2.19 s | 2.69 s | 2.77 s | 0% |
| Category page | 3.5 | 1.84 s | 2.24 s | 2.4 s | 0% |
| Product page | 3.5 | 1.71 s | 1.94 s | 2.11 s | 0% |
| Product search | 3.5 | 1.55 s | 1.78 s | 1.85 s | 0% |
Cart and checkout
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 8 virtual users | |||||
| Add to cart | 6.67 | 486 ms | 620 ms | 668 ms | 0% |
| Cart | 6.67 | 395 ms | 525 ms | 574 ms | 0% |
| Checkout | 6.67 | 311 ms | 422 ms | 465 ms | 0% |
| 32 virtual users | |||||
| Add to cart | 6.59 | 1.74 s | 2.05 s | 2.28 s | 0% |
| Cart | 6.59 | 1.64 s | 1.89 s | 2 s | 0% |
| Checkout | 6.59 | 1.43 s | 1.66 s | 1.74 s | 0% |
k6 with a fixed number of virtual users, 62 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 | 0.891 | 448 ms | 802 ms | 1.05 s | 0% |
| Topic JSON | 0.454 | 228 ms | 413 ms | 486 ms | 0% |
| Home page | 0.454 | 406 ms | 604 ms | 749 ms | 0% |
| Categories page | 0.227 | 477 ms | 807 ms | 1.12 s | 0% |
| User activity page | 0.227 | 290 ms | 493 ms | 504 ms | 0% |
| 4 virtual users | |||||
| Topic page | 0.837 | 1.89 s | 2.44 s | 2.84 s | 0% |
| Topic JSON | 0.418 | 1.01 s | 1.67 s | 2.15 s | 0% |
| Home page | 0.387 | 1.7 s | 2.29 s | 2.68 s | 0% |
| Categories page | 0.232 | 1.91 s | 2.81 s | 3.21 s | 0% |
| User activity page | 0.186 | 1.4 s | 2.18 s | 2.35 s | 0% |
| 16 virtual users | |||||
| Topic page | 0.78 | 3.4 s | 4.86 s | 5.6 s | 0% |
| Topic JSON | 0.374 | 2.6 s | 4.4 s | 5.03 s | 0% |
| Home page | 0.374 | 3.05 s | 5.18 s | 5.56 s | 0% |
| Categories page | 0.172 | 3.01 s | 4.45 s | 4.89 s | 0% |
| User activity page | 0.203 | 2.8 s | 3.23 s | 3.28 s | 0% |
Anonymous
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 16 virtual users | |||||
| Topic page | 36.2 | 54.6 ms | 594 ms | 894 ms | 0.272% |
| Topic JSON | 18.1 | 50.6 ms | 511 ms | 800 ms | 0.542% |
| Home page | 18.1 | 57.7 ms | 599 ms | 998 ms | 0.633% |
| Categories page | 9.05 | 48.2 ms | 600 ms | 945 ms | 0.543% |
| User activity page | 9.11 | 155 ms | 1.29 s | 2.05 s | 0.719% |
k6 with a fixed number of virtual users, 61 to 65 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 448 MB of it. The container peaked at 1,431 MB.
Ghost
Readers
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 5.96 | 47.2 ms | 63.5 ms | 71.7 ms | 0% |
| Post page | 14.8 | 24.7 ms | 33.1 ms | 39.8 ms | 0% |
| Tag page | 2.98 | 32.2 ms | 41.7 ms | 51.2 ms | 0% |
| Author page | 2.96 | 32 ms | 43 ms | 50.5 ms | 0% |
| RSS feed | 2.96 | 39.6 ms | 52.5 ms | 63.5 ms | 0% |
| 4 virtual users | |||||
| Home page | 7.29 | 146 ms | 190 ms | 208 ms | 0% |
| Post page | 18.2 | 101 ms | 140 ms | 161 ms | 0% |
| Tag page | 3.64 | 91.8 ms | 132 ms | 143 ms | 0% |
| Author page | 3.63 | 91.8 ms | 127 ms | 148 ms | 0% |
| RSS feed | 3.61 | 100 ms | 134 ms | 144 ms | 0% |
| 16 virtual users | |||||
| Home page | 7.22 | 556 ms | 657 ms | 730 ms | 0% |
| Post page | 18.1 | 467 ms | 564 ms | 627 ms | 0% |
| Tag page | 3.61 | 306 ms | 391 ms | 437 ms | 0% |
| Author page | 3.63 | 304 ms | 382 ms | 426 ms | 0% |
| RSS feed | 3.63 | 312 ms | 390 ms | 456 ms | 0% |
Staff in Ghost Admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Post list | 3.15 | 46.5 ms | 63.4 ms | 77.5 ms | 0% |
| Post editor | 9.46 | 17.7 ms | 24.5 ms | 35.1 ms | 0% |
| Saving a draft | 9.46 | 46.1 ms | 60.1 ms | 67.4 ms | 0% |
| Member list | 3.15 | 57.2 ms | 78.1 ms | 107 ms | 0% |
| 4 virtual users | |||||
| Post list | 3.96 | 63 ms | 80.6 ms | 88.3 ms | 0% |
| Post editor | 11.9 | 31 ms | 42.7 ms | 50.3 ms | 0% |
| Saving a draft | 12 | 249 ms | 328 ms | 359 ms | 0% |
| Member list | 3.98 | 75.2 ms | 99.4 ms | 109 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 346 MB and MySQL at 586 MB.
Wagtail
Visitors
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 1.21 | 107 ms | 126 ms | 144 ms | 0% |
| Blog index | 1.21 | 378 ms | 419 ms | 455 ms | 0% |
| Blog post | 3.64 | 33.8 ms | 50.1 ms | 54.8 ms | 0% |
| Bread page | 3.64 | 36.7 ms | 52.5 ms | 60.3 ms | 0% |
| Location page | 1.21 | 36.1 ms | 46.5 ms | 58.5 ms | 0% |
| Site search | 1.21 | 57.2 ms | 92.7 ms | 101 ms | 0% |
| 4 virtual users | |||||
| Home page | 1.52 | 247 ms | 894 ms | 999 ms | 0% |
| Blog index | 1.57 | 980 ms | 3.24 s | 3.6 s | 0% |
| Blog post | 4.56 | 71.4 ms | 283 ms | 308 ms | 0% |
| Bread page | 4.61 | 78.7 ms | 288 ms | 378 ms | 0% |
| Location page | 1.57 | 76.4 ms | 220 ms | 299 ms | 0% |
| Site search | 1.5 | 124 ms | 476 ms | 707 ms | 0% |
| 16 virtual users | |||||
| Home page | 0.671 | 2.6 s | 3.28 s | 3.73 s | 0% |
| Blog index | 0.734 | 7.11 s | 8.12 s | 9.3 s | 0% |
| Blog post | 2 | 1.51 s | 2.21 s | 3.5 s | 0% |
| Bread page | 2.01 | 1.51 s | 2.31 s | 3.56 s | 0% |
| Location page | 0.671 | 1.48 s | 2.07 s | 2.48 s | 0% |
| Site search | 0.671 | 1.78 s | 2.59 s | 2.99 s | 0% |
Editors in the Wagtail admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Admin dashboard | 0.291 | 173 ms | 278 ms | 284 ms | 0% |
| Page explorer | 0.598 | 762 ms | 998 ms | 1.25 s | 0% |
| Page editor | 0.872 | 364 ms | 586 ms | 680 ms | 0% |
| Image library | 0.291 | 128 ms | 408 ms | 1.49 s | 0% |
| Admin page search | 0.291 | 85 ms | 122 ms | 161 ms | 0% |
| 4 virtual users | |||||
| Admin dashboard | 0.237 | 1.11 s | 1.76 s | 1.85 s | 0% |
| Page explorer | 0.521 | 3.7 s | 5.73 s | 6.02 s | 0% |
| Page editor | 0.742 | 1.6 s | 2.69 s | 2.93 s | 0% |
| Image library | 0.237 | 1 s | 1.57 s | 1.58 s | 0% |
| Admin page search | 0.237 | 418 ms | 1.01 s | 1.24 s | 0% |
k6 with a fixed number of virtual users, 60 to 63 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 292 MB, Postgres at 175 MB, and Redis at 26 MB.
Advertised vs. measured
| Spec | Advertised | Measured |
|---|---|---|
| vCPU | 4 | 4 |
| CPU | Shared vCPU | 0.4% of busy CPU time stolen |
| RAM | 2 GB | 1.9 GiB |
| Storage | 35 GB SSD | 33.8 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 (Skylake, IBRS)
- CPU cores
- 4
- CPU frequency
- 2600 MHz
- AES-NI
- Yes
- VM-x/AMD-V
- Yes
- RAM reported
- 1.9 GiB
- Swap reported
- 1024 MiB
- Disk reported
- 33.8 GiB
- Virtualization reported
- KVM
- CPU steal
- 0.4% of busy CPU time stolen
- Distro
- Ubuntu 24.04.5 LTS
- Kernel
- 6.8.0-106-generic
- Architecture
- x86_64
- IPv4 reachable
- Yes
- IPv6 reachable
- Yes
Advertised at test time
- Plan
- s.2 4 vCPU / 2 GB
- Product line
- General Purpose
- Location
- Toronto
- vCPU
- 4 shared vCPU
- Architecture
- x86_64
- RAM
- 2 GB
- Storage
- 35 GB SSD
- Virtualization
- KVM
- Network
- Unknown
- Transfer
- 2.5 TB
- Port 25
- Unknown
- Monthly price at test time
- $14.00
- Hourly price at test time
- $0.019
- YABS version
- v2026-09-20
- Ran at
- Oct 13, 2026, 19:11:47 UTC
- Parser version
- 5
Run timeline
- Queued
- Oct 13, 2026, 19:07:00 UTC
- Server created
- Oct 13, 2026, 19:11:34 UTC
- First update from the server
- Oct 13, 2026, 19:11:35 UTC
- Completed
- Oct 13, 2026, 21:01:27 UTC
- Server deleted
- Oct 13, 2026, 21:01:27 UTC
- Cost of this run
- $0.037
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.