Linode Linode 4GB
Server
-
ProviderLinode
-
PlanLinode 4GB
-
LocationMiami, FL
-
vCPU2
-
RAM4 GB
-
Storage80 GB SSD
-
Network4 Gbps
-
OS imagelinode/ubuntu24.04
-
TriggerScheduled
-
Queued atOct 13, 2026, 18:03:00 UTC
Referral link. If you sign up through it, I may get paid. How this works
Latest runs of this plan
- Chicago, IL Oct 12, 2026 857
- Tokyo 2, JP Oct 12, 2026 1,256
- Fremont, CA Oct 11, 2026 1,219
- Newark, NJ Oct 10, 2026 967
CPU
| Version | Single-core | Multi-core | Result link |
|---|---|---|---|
| Geekbench 7 | 1,033 | 1,951 | Geekbench Browser |
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,180
|
2,058
|
| Navigation |
1,083
|
Single-core only |
| HTML5 Browser |
1,043
|
Single-core only |
| PDF Viewer |
1,165
|
Single-core only |
| Photo Library |
919
|
1,944
|
| Clang |
746
|
1,636
|
| Text Processing |
821
|
1,469
|
| Asset Compression |
1,005
|
2,017
|
| HDR |
1,106
|
2,105
|
| Photo Editor |
1,161
|
2,635
|
| Ray Tracer |
964
|
1,955
|
| Structure from Motion |
1,130
|
Single-core only |
| Game Physics |
1,026
|
Single-core only |
| Video Encoder |
979
|
Single-core only |
| Audio Encoder |
1,148
|
Single-core only |
| Video Player |
1,191
|
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 | 44.6 GB/s | 3 | 6.96% |
| Scale higher is better | 33.5 GB/s | 3 | 7.28% |
| Add higher is better | 35.7 GB/s | 3 | 6.13% |
| Triad higher is better | 35.5 GB/s | 3 | 7.51% |
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 | 352/s | 3 | 3.05% |
| RSA 4096 verifies higher is better | 21,822/s | 3 | 3.89% |
| SHA-256 higher is better | 1.32 GB/s | 3 | 1.05% |
| AES-256-GCM higher is better | 5.65 GB/s | 3 | 0.303% |
| ChaCha20-Poly1305 higher is better | 3.41 GB/s | 3 | 21.7% |
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 | 5.92 ms | 3 | 2.03% |
| Requests per second, 90th percentile higher is better | 348/s | 3 | 2.67% |
| Request latency, 99.9th percentile lower is better | 23.8 ms | 3 | 70.8% |
| Requests per second, average higher is better | 306/s | 3 | 3.48% |
Average of 3 runs. Spread is the standard deviation as a share of the average.
Disk
| Block size | Read | Write | Total |
|---|---|---|---|
| 4K | 156.8 MB/s (40,150 IOPS) | 157.3 MB/s (40,256 IOPS) | 314.1 MB/s (80,406 IOPS) |
| 64K | 1.54 GB/s (25,237 IOPS) | 1.55 GB/s (25,369 IOPS) | 3.09 GB/s (50,606 IOPS) |
| 512K | 2 GB/s (4,096 IOPS) | 2.11 GB/s (4,314 IOPS) | 4.11 GB/s (8,410 IOPS) |
| 1M | 2.22 GB/s (2,278 IOPS) | 2.37 GB/s (2,429 IOPS) | 4.6 GB/s (4,707 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.67 Gbps | 1.99 Gbps |
| Eranium, Amsterdam, NL (100G) | IPv4 | 1.71 Gbps | 1.93 Gbps |
| Leaseweb, Singapore, SG (10G) | IPv4 | 571 Mbps | 974 Mbps |
| Clouvider, Los Angeles, CA, US (10G) | IPv4 | 2.57 Gbps | 3.64 Gbps |
| Leaseweb, NYC, NY, US (10G) | IPv4 | 4.28 Gbps | 6.69 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 | 8,253 | 0.121 ms |
| fdatasync | 4,615 | 0.217 ms |
| fsync | 3,385 | 0.295 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 824 | 1.21 ms |
| Two 8 kB writes | ||
| open_datasync | 4,269 | 0.234 ms |
| fdatasync | 4,283 | 0.233 ms |
| fsync | 3,238 | 0.309 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 1,676 | 0.597 ms |
| open_sync at different write sizes | ||
| 1 * 16kB open_sync write | 2,604 | 0.384 ms |
| 2 * 8kB open_sync writes | 1,539 | 0.65 ms |
| 4 * 4kB open_sync writes | 878 | 1.14 ms |
| 8 * 2kB open_sync writes | 307 | 3.26 ms |
| 16 * 1kB open_sync writes | 136 | 7.33 ms |
| fsync on a non-write descriptor | ||
| write, fsync, close | 424 | 2.36 ms |
| write, close, fsync | 2,580 | 0.388 ms |
| Non-synced 8 kB writes | ||
| write | 419,875 | 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,156 | 0.795 ms | 1.16 ms | 2.31 ms | 6.69 ms | 0 |
| Read/write (TPC-B like) | 8 | 2,948 | 2.26 ms | 4.92 ms | 10.7 ms | 33.9 ms | 0 |
| Read/write (TPC-B like) | 32 | 3,429 | 7.34 ms | 22.2 ms | 36.7 ms | 59 ms | 0 |
| Read only | 1 | 12,491 | 0.071 ms | 0.114 ms | 0.172 ms | 0.669 ms | 0 |
| Read only | 8 | 34,023 | 0.193 ms | 0.381 ms | 0.497 ms | 2.09 ms | 0 |
| Read only | 32 | 35,343 | 0.685 ms | 1.38 ms | 2 ms | 10.5 ms | 0 |
Scale 10 (1,000,000 accounts), loaded in 1.5 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 | 947 | 0.899 ms | 1.57 ms | 4.41 ms | 15.1 ms | 0 |
| Read/write (TPC-B like) | 8 | 3,249 | 2.29 ms | 3.96 ms | 5.92 ms | 11.6 ms | 0 |
| Read/write (TPC-B like) | 32 | 3,286 | 8.39 ms | 17.6 ms | 37 ms | 70.1 ms | 0 |
| Read only | 1 | 10,351 | 0.084 ms | 0.144 ms | 0.42 ms | 1.02 ms | 0 |
| Read only | 8 | 26,033 | 0.252 ms | 0.478 ms | 0.673 ms | 8.42 ms | 0 |
| Read only | 32 | 31,748 | 0.815 ms | 1.7 ms | 2.45 ms | 5.19 ms | 0 |
Scale 100 (10,000,000 accounts), loaded in 16 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 | 228 | 4,563 | 3.62 ms | 7.57 ms | 21.1 ms | 0 |
| Read/write | 8 | 556 | 11,123 | 13.7 ms | 24.4 ms | 38.9 ms | 0 |
| Read/write | 32 | 621 | 12,415 | 49.2 ms | 87.6 ms | 121 ms | 0 |
| Read only | 1 | 547 | 8,749 | 1.67 ms | 2.39 ms | 4.91 ms | 0 |
| Read only | 8 | 1,155 | 18,474 | 6.43 ms | 10.7 ms | 14.5 ms | 0 |
| Read only | 32 | 1,210 | 19,354 | 25.3 ms | 35.6 ms | 44.2 ms | 0 |
10 tables of 100,000 rows, loaded in 9 s. 60 s per run, one connection per thread.
Redis
memtier
| Mix | Operations/s | Hits/s | Median | p99 | p99.9 |
|---|---|---|---|---|---|
| 1:10 set:get | 42,679 | 38,799 | 1.18 ms | 4.58 ms | 12.3 ms |
| 1:1 set:get | 41,886 | 20,943 | 1.14 ms | 4.67 ms | 13.4 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 | 514 | 1,762 | 2,637 | 716 ms |
| Express express-postgresjs | 5,186 | 7,803 | 17,712 | 94.9 ms |
| Fastify fastify-postgres | 5,856 | 8,298 | 17,998 | 90 ms |
| NestJS nestjs | 3,136 | 3,959 | 11,786 | 128 ms |
| Nuxt nuxt | 5,005 | 6,884 | 18,532 | 203 ms |
| FastAPI fastapi | 2,552 | 3,356 | 11,569 | 469 ms |
| Django django-postgresql | 1,382 | 1,455 | 3,409 | 253 ms |
| Rails rails | 2,182 | 3,180 | 9,578 | 233 ms |
| Laravel laravel | 570 | 571 | 1,080 | 512 ms |
| Symfony symfony | 670 | 794 | 1,932 | 796 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 | 1.61 | 972 ms | 1.34 s | 1.52 s | 0% |
| Shop page | 1.61 | 1.3 s | 1.51 s | 1.58 s | 0% |
| Category page | 1.61 | 799 ms | 1.38 s | 1.43 s | 0% |
| Product page | 1.61 | 867 ms | 1.05 s | 1.09 s | 0% |
| Product search | 1.61 | 757 ms | 951 ms | 1.01 s | 0% |
| 32 virtual users | |||||
| Home page | 1.65 | 3.64 s | 4.58 s | 5.77 s | 0% |
| Shop page | 1.64 | 4.58 s | 5.25 s | 5.56 s | 0% |
| Category page | 1.4 | 4.08 s | 4.86 s | 5.04 s | 0% |
| Product page | 1.36 | 3.67 s | 6.8 s | 6.9 s | 0% |
| Product search | 1.36 | 3.38 s | 5.54 s | 6.43 s | 0% |
Cart and checkout
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 8 virtual users | |||||
| Add to cart | 3.08 | 1.07 s | 1.41 s | 1.47 s | 0% |
| Cart | 3.08 | 842 ms | 1.11 s | 1.16 s | 0% |
| Checkout | 3.08 | 637 ms | 875 ms | 899 ms | 0% |
| 32 virtual users | |||||
| Add to cart | 3.12 | 3.36 s | 5.05 s | 5.48 s | 0% |
| Cart | 3.12 | 3.47 s | 4.42 s | 4.92 s | 0% |
| Checkout | 3.12 | 2.84 s | 3.6 s | 3.87 s | 0% |
k6 with a fixed number of virtual users, 62 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.7 | 251 ms | 371 ms | 576 ms | 0% |
| Topic JSON | 0.859 | 132 ms | 170 ms | 404 ms | 0% |
| Home page | 0.859 | 226 ms | 316 ms | 477 ms | 0% |
| Categories page | 0.43 | 254 ms | 456 ms | 519 ms | 0% |
| User activity page | 0.43 | 153 ms | 192 ms | 470 ms | 0% |
| 4 virtual users | |||||
| Topic page | 2.97 | 573 ms | 1.03 s | 1.26 s | 0% |
| Topic JSON | 1.49 | 279 ms | 424 ms | 509 ms | 0% |
| Home page | 1.47 | 515 ms | 1.01 s | 1.11 s | 0% |
| Categories page | 0.76 | 578 ms | 1.27 s | 1.63 s | 0% |
| User activity page | 0.743 | 373 ms | 953 ms | 1.21 s | 0% |
| 16 virtual users | |||||
| Topic page | 3.2 | 1.68 s | 2.23 s | 3.28 s | 0% |
| Topic JSON | 1.65 | 1.43 s | 2.01 s | 2.25 s | 0% |
| Home page | 1.59 | 1.63 s | 2.3 s | 3.02 s | 0% |
| Categories page | 0.809 | 1.7 s | 2.58 s | 2.97 s | 0% |
| User activity page | 0.809 | 1.49 s | 2.51 s | 3.05 s | 0% |
Anonymous
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 16 virtual users | |||||
| Topic page | 55.8 | 80 ms | 178 ms | 299 ms | 0.149% |
| Topic JSON | 27.9 | 78 ms | 174 ms | 251 ms | 0.178% |
| Home page | 27.9 | 80.6 ms | 171 ms | 329 ms | 0.178% |
| Categories page | 14 | 84 ms | 181 ms | 393 ms | 0% |
| User activity page | 14 | 247 ms | 389 ms | 847 ms | 0.118% |
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 1024 MB of Postgres shared buffers, what its installer picks for a 4 GB box. It added a 2 GB swapfile first, the way its installer does, and didn't need it. The container peaked at 2,131 MB.
Ghost
Readers
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 6.33 | 43.8 ms | 61.2 ms | 107 ms | 0% |
| Post page | 15.8 | 23 ms | 33.3 ms | 66.4 ms | 0% |
| Tag page | 3.16 | 30.5 ms | 42.5 ms | 68.1 ms | 0% |
| Author page | 3.15 | 29.4 ms | 40 ms | 71.7 ms | 0% |
| RSS feed | 3.15 | 34.3 ms | 47.7 ms | 71.3 ms | 0% |
| 4 virtual users | |||||
| Home page | 7.27 | 136 ms | 202 ms | 347 ms | 0% |
| Post page | 18.1 | 97.2 ms | 153 ms | 266 ms | 0% |
| Tag page | 3.64 | 89.7 ms | 157 ms | 223 ms | 0% |
| Author page | 3.59 | 90.6 ms | 140 ms | 209 ms | 0% |
| RSS feed | 3.59 | 93.7 ms | 153 ms | 262 ms | 0% |
| 16 virtual users | |||||
| Home page | 7.68 | 509 ms | 681 ms | 1.17 s | 0% |
| Post page | 19.2 | 421 ms | 593 ms | 974 ms | 0% |
| Tag page | 3.85 | 279 ms | 394 ms | 572 ms | 0% |
| Author page | 3.82 | 277 ms | 397 ms | 707 ms | 0% |
| RSS feed | 3.8 | 286 ms | 404 ms | 658 ms | 0% |
Staff in Ghost Admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Post list | 3.9 | 39 ms | 54.5 ms | 77 ms | 0% |
| Post editor | 11.7 | 14.6 ms | 21.3 ms | 27.9 ms | 0% |
| Saving a draft | 11.7 | 36 ms | 47.2 ms | 60.8 ms | 0% |
| Member list | 3.9 | 47.2 ms | 66.3 ms | 72.3 ms | 0% |
| 4 virtual users | |||||
| Post list | 4.41 | 55.2 ms | 85.3 ms | 134 ms | 0% |
| Post editor | 13.3 | 26.9 ms | 43.4 ms | 78.4 ms | 0% |
| Saving a draft | 13.3 | 214 ms | 320 ms | 614 ms | 0% |
| Member list | 4.45 | 65.3 ms | 99.5 ms | 174 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 361 MB and MySQL at 621 MB.
Wagtail
Visitors
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 1.23 | 106 ms | 141 ms | 247 ms | 0% |
| Blog index | 1.21 | 352 ms | 443 ms | 890 ms | 0% |
| Blog post | 3.64 | 33.2 ms | 51.9 ms | 93.3 ms | 0% |
| Bread page | 3.66 | 36.5 ms | 50.1 ms | 112 ms | 0% |
| Location page | 1.21 | 34.4 ms | 50.4 ms | 80.1 ms | 0% |
| Site search | 1.21 | 55.7 ms | 113 ms | 174 ms | 0% |
| 4 virtual users | |||||
| Home page | 2.05 | 264 ms | 425 ms | 649 ms | 0% |
| Blog index | 2.08 | 917 ms | 1.27 s | 1.57 s | 0% |
| Blog post | 6.16 | 81.1 ms | 143 ms | 216 ms | 0% |
| Bread page | 6.21 | 84.2 ms | 140 ms | 244 ms | 0% |
| Location page | 2.1 | 79.7 ms | 124 ms | 145 ms | 0% |
| Site search | 2.05 | 126 ms | 267 ms | 336 ms | 0% |
| 16 virtual users | |||||
| Home page | 2.29 | 822 ms | 1.05 s | 1.1 s | 0% |
| Blog index | 2.35 | 1.98 s | 2.32 s | 2.38 s | 0% |
| Blog post | 6.86 | 456 ms | 676 ms | 800 ms | 0% |
| Bread page | 6.92 | 497 ms | 722 ms | 835 ms | 0% |
| Location page | 2.3 | 485 ms | 726 ms | 892 ms | 0% |
| Site search | 2.29 | 564 ms | 855 ms | 962 ms | 0% |
Editors in the Wagtail admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Admin dashboard | 0.429 | 115 ms | 212 ms | 391 ms | 0% |
| Page explorer | 0.892 | 505 ms | 966 ms | 1.11 s | 0% |
| Page editor | 1.34 | 234 ms | 446 ms | 722 ms | 0% |
| Image library | 0.446 | 86.9 ms | 164 ms | 836 ms | 0% |
| Admin page search | 0.446 | 53.9 ms | 135 ms | 186 ms | 0% |
| 4 virtual users | |||||
| Admin dashboard | 0.787 | 324 ms | 558 ms | 628 ms | 0% |
| Page explorer | 1.62 | 1.22 s | 1.9 s | 2.08 s | 0% |
| Page editor | 2.46 | 560 ms | 943 ms | 1.05 s | 0% |
| Image library | 0.82 | 238 ms | 508 ms | 537 ms | 0% |
| Admin page search | 0.803 | 109 ms | 348 ms | 406 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 294 MB, Postgres at 160 MB, and Redis at 26 MB.
Advertised vs. measured
| Spec | Advertised | Measured |
|---|---|---|
| vCPU | 2 | 2 |
| CPU | Shared vCPU | 2.7% of busy CPU time stolen |
| RAM | 4 GB | 3.8 GiB |
| Storage | 80 GB SSD | 78.2 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
- AMD EPYC 7713 64-Core Processor
- CPU cores
- 2
- CPU frequency
- 2000 MHz
- AES-NI
- Yes
- VM-x/AMD-V
- No
- RAM reported
- 3.8 GiB
- Swap reported
- 496 MiB
- Disk reported
- 78.2 GiB
- Virtualization reported
- KVM
- CPU steal
- 2.7% of busy CPU time stolen
- Distro
- Ubuntu 24.04.4 LTS
- Kernel
- 6.8.0-134-generic
- Architecture
- x86_64
- IPv4 reachable
- Yes
- IPv6 reachable
- Yes
Advertised at test time
- Plan
- Linode 4GB
- Product line
- Shared CPU
- Location
- Miami, FL
- vCPU
- 2 shared vCPU
- Architecture
- x86_64
- RAM
- 4 GB
- Storage
- 80 GB SSD
- Virtualization
- KVM
- Network
- 4 Gbps
- Transfer
- 4 TB
- Port 25
- On request
- Monthly price at test time
- $24.00
- Hourly price at test time
- $0.036
- YABS version
- v2026-09-20
- Ran at
- Oct 13, 2026, 18:06:00 UTC
- Parser version
- 5
Run timeline
- Queued
- Oct 13, 2026, 18:03:00 UTC
- Server created
- Oct 13, 2026, 18:04:42 UTC
- First update from the server
- Oct 13, 2026, 18:04:42 UTC
- Completed
- Oct 13, 2026, 19:46:32 UTC
- Server deleted
- Oct 13, 2026, 19:46:32 UTC
- Cost of this run
- $0.062
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 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.