Linode Linode 4GB
Tokyo 2, JP
Server
-
ProviderLinode
-
PlanLinode 4GB
-
LocationTokyo 2, JP
-
vCPU2
-
RAM4 GB
-
Storage80 GB SSD
-
Network4 Gbps
-
OS imagelinode/ubuntu24.04
-
TriggerManual
-
Queued atOct 12, 2026, 01:06:45 UTC
Referral link. If you sign up through it, I may get paid. How this works
Latest runs of this plan
Full history of this planCPU
| Version | Single-core | Multi-core | Result link |
|---|---|---|---|
| Geekbench 7 | 1,256 | 2,318 | 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,384
|
2,350
|
| Navigation |
1,416
|
Single-core only |
| HTML5 Browser |
1,146
|
Single-core only |
| PDF Viewer |
1,338
|
Single-core only |
| Photo Library |
1,130
|
2,252
|
| Clang |
1,173
|
2,298
|
| Text Processing |
1,076
|
2,022
|
| Asset Compression |
1,248
|
2,438
|
| HDR |
1,028
|
1,929
|
| Photo Editor |
1,399
|
2,738
|
| Ray Tracer |
1,305
|
2,636
|
| Structure from Motion |
1,395
|
Single-core only |
| Game Physics |
1,301
|
Single-core only |
| Video Encoder |
1,193
|
Single-core only |
| Audio Encoder |
1,287
|
Single-core only |
| Video Player |
1,377
|
Single-core only |
Rank among the 106 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 | 51.8 GB/s | 3 | 21.8% |
| Scale higher is better | 37.2 GB/s | 3 | 14.8% |
| Add higher is better | 39.8 GB/s | 3 | 17.5% |
| Triad higher is better | 40.9 GB/s | 3 | 18.5% |
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 | 445/s | 3 | 1.86% |
| RSA 4096 verifies higher is better | 29,708/s | 3 | 0.575% |
| SHA-256 higher is better | 1.37 GB/s | 3 | 0.872% |
| AES-256-GCM higher is better | 6.87 GB/s | 3 | 1.39% |
| ChaCha20-Poly1305 higher is better | 3.51 GB/s | 3 | 0.406% |
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.16 ms | 3 | 0.587% |
| Requests per second, 90th percentile higher is better | 474/s | 3 | 1.06% |
| Request latency, 99.9th percentile lower is better | 7.87 ms | 3 | 3.78% |
| Requests per second, average higher is better | 469/s | 3 | 1.04% |
Average of 3 runs. Spread is the standard deviation as a share of the average.
Disk
| Block size | Read | Write | Total |
|---|---|---|---|
| 4K | 145 MB/s (37,110 IOPS) | 145.3 MB/s (37,208 IOPS) | 290.3 MB/s (74,318 IOPS) |
| 64K | 1.54 GB/s (25,198 IOPS) | 1.55 GB/s (25,330 IOPS) | 3.08 GB/s (50,528 IOPS) |
| 512K | 4.66 GB/s (9,545 IOPS) | 4.91 GB/s (10,052 IOPS) | 9.57 GB/s (19,597 IOPS) |
| 1M | 5.51 GB/s (5,646 IOPS) | 5.88 GB/s (6,022 IOPS) | 11.4 GB/s (11,668 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 | 597 Mbps | 788 Mbps |
| Eranium, Amsterdam, NL (100G) | IPv4 | 768 Mbps | 824 Mbps |
| Leaseweb, Singapore, SG (10G) | IPv4 | 1.97 Gbps | 3.24 Gbps |
| Clouvider, Los Angeles, CA, US (10G) | IPv4 | 1.59 Gbps | 2.04 Gbps |
| Leaseweb, NYC, NY, US (10G) | IPv4 | 1.15 Gbps | 1.37 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 | 11,736 | 0.085 ms |
| fdatasync | 6,699 | 0.149 ms |
| fsync | 4,672 | 0.214 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 4,660 | 0.215 ms |
| Two 8 kB writes | ||
| open_datasync | 5,588 | 0.179 ms |
| fdatasync | 6,267 | 0.16 ms |
| fsync | 4,673 | 0.214 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 2,789 | 0.359 ms |
| open_sync at different write sizes | ||
| 1 * 16kB open_sync write | 5,073 | 0.197 ms |
| 2 * 8kB open_sync writes | 2,518 | 0.397 ms |
| 4 * 4kB open_sync writes | 1,421 | 0.704 ms |
| 8 * 2kB open_sync writes | 473 | 2.12 ms |
| 16 * 1kB open_sync writes | 241 | 4.15 ms |
| fsync on a non-write descriptor | ||
| write, fsync, close | 4,769 | 0.21 ms |
| write, close, fsync | 4,501 | 0.222 ms |
| Non-synced 8 kB writes | ||
| write | 533,458 | 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,757 | 0.551 ms | 0.683 ms | 0.918 ms | 2.14 ms | 0 |
| Read/write (TPC-B like) | 8 | 4,234 | 1.78 ms | 3.01 ms | 3.95 ms | 5.96 ms | 0 |
| Read/write (TPC-B like) | 32 | 4,279 | 6.01 ms | 16.7 ms | 27.7 ms | 44.6 ms | 0 |
| Read only | 1 | 18,744 | 0.051 ms | 0.067 ms | 0.078 ms | 0.222 ms | 0 |
| Read only | 8 | 47,569 | 0.15 ms | 0.238 ms | 0.295 ms | 0.604 ms | 0 |
| Read only | 32 | 49,335 | 0.528 ms | 0.82 ms | 1.14 ms | 2.86 ms | 0 |
Scale 10 (1,000,000 accounts), loaded in 1.45 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 | 1,488 | 0.621 ms | 0.99 ms | 1.29 ms | 4.12 ms | 0 |
| Read/write (TPC-B like) | 8 | 3,974 | 1.88 ms | 2.96 ms | 4.49 ms | 15.7 ms | 0 |
| Read/write (TPC-B like) | 32 | 4,886 | 6.03 ms | 9.94 ms | 14.2 ms | 43.9 ms | 0 |
| Read only | 1 | 14,132 | 0.061 ms | 0.088 ms | 0.172 ms | 0.805 ms | 0 |
| Read only | 8 | 37,543 | 0.192 ms | 0.314 ms | 0.401 ms | 1.3 ms | 0 |
| Read only | 32 | 40,499 | 0.691 ms | 1.02 ms | 1.42 ms | 3.1 ms | 0 |
Scale 100 (10,000,000 accounts), loaded in 15.1 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 | 376 | 7,523 | 2.52 ms | 3.49 ms | 5.77 ms | 0 |
| Read/write | 8 | 721 | 14,429 | 11 ms | 17.3 ms | 21.9 ms | 0 |
| Read/write | 32 | 828 | 16,563 | 37.6 ms | 61.1 ms | 78.6 ms | 0 |
| Read only | 1 | 784 | 12,552 | 1.25 ms | 1.44 ms | 1.73 ms | 0 |
| Read only | 8 | 1,635 | 26,162 | 4.65 ms | 7.04 ms | 7.99 ms | 0 |
| Read only | 32 | 1,557 | 24,916 | 20 ms | 26.2 ms | 29.2 ms | 0 |
10 tables of 100,000 rows, loaded in 7.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 | 54,084 | 49,166 | 0.743 ms | 3.26 ms | 4.99 ms |
| 1:1 set:get | 52,747 | 26,373 | 0.647 ms | 3.33 ms | 5.09 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 | 668 | 2,420 | 3,293 | 580 ms |
| Express express-postgresjs | 7,663 | 11,085 | 30,688 | 63.7 ms |
| Fastify fastify-postgres | 7,562 | 11,656 | 34,332 | 57.9 ms |
| NestJS nestjs | 4,980 | 5,699 | 18,098 | 89.6 ms |
| Nuxt nuxt | 6,894 | 10,688 | 28,481 | 71 ms |
| FastAPI fastapi | 3,885 | 4,734 | 17,018 | 294 ms |
| Django django-postgresql | 1,894 | 2,183 | 4,748 | 245 ms |
| Rails rails | 3,096 | 4,205 | 13,769 | 164 ms |
| Laravel laravel | 853 | 915 | 1,704 | 399 ms |
| Symfony symfony | 1,083 | 1,200 | 3,241 | 260 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 | 2.28 | 689 ms | 753 ms | 780 ms | 0% |
| Shop page | 2.28 | 934 ms | 1.03 s | 1.12 s | 0% |
| Category page | 2.28 | 596 ms | 920 ms | 964 ms | 0% |
| Product page | 2.28 | 653 ms | 731 ms | 833 ms | 0% |
| Product search | 2.28 | 565 ms | 652 ms | 685 ms | 0% |
| 32 virtual users | |||||
| Home page | 2.29 | 2.55 s | 2.86 s | 2.93 s | 0% |
| Shop page | 2.29 | 3.36 s | 3.86 s | 4.02 s | 0% |
| Category page | 2.29 | 2.95 s | 3.5 s | 3.62 s | 0% |
| Product page | 2.29 | 2.59 s | 2.76 s | 2.82 s | 0% |
| Product search | 2.29 | 2.38 s | 2.62 s | 2.7 s | 0% |
Cart and checkout
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 8 virtual users | |||||
| Add to cart | 4.38 | 740 ms | 880 ms | 917 ms | 0% |
| Cart | 4.38 | 607 ms | 727 ms | 756 ms | 0% |
| Checkout | 4.38 | 474 ms | 575 ms | 602 ms | 0% |
| 32 virtual users | |||||
| Add to cart | 4.41 | 2.44 s | 2.94 s | 3.04 s | 0% |
| Cart | 4.41 | 2.62 s | 2.96 s | 3.05 s | 0% |
| Checkout | 4.41 | 2.08 s | 2.37 s | 2.49 s | 0% |
k6 with a fixed number of virtual users, 61 to 70 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 | 2.12 | 205 ms | 288 ms | 509 ms | 0% |
| Topic JSON | 1.08 | 103 ms | 158 ms | 195 ms | 0% |
| Home page | 1.08 | 183 ms | 218 ms | 308 ms | 0% |
| Categories page | 0.529 | 208 ms | 284 ms | 305 ms | 0% |
| User activity page | 0.529 | 122 ms | 239 ms | 372 ms | 0% |
| 4 virtual users | |||||
| Topic page | 3.96 | 436 ms | 715 ms | 1.05 s | 0% |
| Topic JSON | 2 | 225 ms | 355 ms | 493 ms | 0% |
| Home page | 1.98 | 383 ms | 558 ms | 589 ms | 0% |
| Categories page | 1.02 | 463 ms | 713 ms | 773 ms | 0% |
| User activity page | 0.991 | 264 ms | 529 ms | 906 ms | 0% |
| 16 virtual users | |||||
| Topic page | 3.71 | 1.61 s | 1.98 s | 2.23 s | 0% |
| Topic JSON | 1.85 | 1.4 s | 1.78 s | 1.85 s | 0% |
| Home page | 1.86 | 1.57 s | 2.03 s | 2.18 s | 0% |
| Categories page | 0.924 | 1.6 s | 1.98 s | 2.11 s | 0% |
| User activity page | 0.956 | 1.45 s | 1.74 s | 1.9 s | 0% |
Anonymous
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 16 virtual users | |||||
| Topic page | 78.6 | 58.5 ms | 137 ms | 193 ms | 0% |
| Topic JSON | 39.3 | 57.1 ms | 131 ms | 184 ms | 0% |
| Home page | 39.3 | 60.3 ms | 141 ms | 217 ms | 0% |
| Categories page | 19.6 | 55.8 ms | 132 ms | 211 ms | 0% |
| User activity page | 19.6 | 179 ms | 308 ms | 437 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. 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,139 MB.
Ghost
Readers
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 8.73 | 33.9 ms | 41.1 ms | 56.5 ms | 0% |
| Post page | 21.8 | 16.4 ms | 21.1 ms | 29 ms | 0% |
| Tag page | 4.36 | 21.7 ms | 27 ms | 33.1 ms | 0% |
| Author page | 4.36 | 22.9 ms | 27.2 ms | 33.1 ms | 0% |
| RSS feed | 4.35 | 27.4 ms | 33.6 ms | 40 ms | 0% |
| 4 virtual users | |||||
| Home page | 10.4 | 105 ms | 145 ms | 171 ms | 0% |
| Post page | 25.9 | 67.9 ms | 97.5 ms | 122 ms | 0% |
| Tag page | 5.18 | 62.1 ms | 92.2 ms | 113 ms | 0% |
| Author page | 5.19 | 68.2 ms | 97.5 ms | 142 ms | 0% |
| RSS feed | 5.19 | 71.9 ms | 104 ms | 149 ms | 0% |
| 16 virtual users | |||||
| Home page | 10.5 | 388 ms | 469 ms | 517 ms | 0% |
| Post page | 26.2 | 317 ms | 405 ms | 448 ms | 0% |
| Tag page | 5.21 | 213 ms | 292 ms | 324 ms | 0% |
| Author page | 5.23 | 209 ms | 279 ms | 311 ms | 0% |
| RSS feed | 5.21 | 215 ms | 286 ms | 325 ms | 0% |
Staff in Ghost Admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Post list | 5.3 | 29.7 ms | 37.1 ms | 48.9 ms | 0% |
| Post editor | 15.9 | 10.7 ms | 14.4 ms | 19.1 ms | 0% |
| Saving a draft | 15.9 | 25.9 ms | 32.7 ms | 39.7 ms | 0% |
| Member list | 5.3 | 37.1 ms | 44.5 ms | 53.2 ms | 0% |
| 4 virtual users | |||||
| Post list | 6.48 | 40.1 ms | 48.5 ms | 80.6 ms | 0% |
| Post editor | 19.5 | 19 ms | 24.7 ms | 31.5 ms | 0% |
| Saving a draft | 19.6 | 155 ms | 200 ms | 257 ms | 0% |
| Member list | 6.53 | 47.9 ms | 56.3 ms | 69.7 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 331 MB and MySQL at 623 MB.
Wagtail
Visitors
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Home page | 1.85 | 71.1 ms | 81.1 ms | 97.1 ms | 0% |
| Blog index | 1.85 | 241 ms | 261 ms | 272 ms | 0% |
| Blog post | 5.53 | 23 ms | 36.5 ms | 42.5 ms | 0% |
| Bread page | 5.53 | 25.5 ms | 30.7 ms | 32.7 ms | 0% |
| Location page | 1.85 | 24.5 ms | 28.8 ms | 33.1 ms | 0% |
| Site search | 1.85 | 39.4 ms | 66.4 ms | 73.7 ms | 0% |
| 4 virtual users | |||||
| Home page | 3.07 | 185 ms | 264 ms | 319 ms | 0% |
| Blog index | 3.09 | 603 ms | 877 ms | 951 ms | 0% |
| Blog post | 9.21 | 52.3 ms | 90 ms | 117 ms | 0% |
| Bread page | 9.25 | 58.1 ms | 88.6 ms | 106 ms | 0% |
| Location page | 3.1 | 56.9 ms | 82.2 ms | 92.3 ms | 0% |
| Site search | 3.07 | 83.1 ms | 173 ms | 203 ms | 0% |
| 16 virtual users | |||||
| Home page | 3.54 | 513 ms | 711 ms | 752 ms | 0% |
| Blog index | 3.62 | 1.28 s | 1.52 s | 1.69 s | 0% |
| Blog post | 10.7 | 298 ms | 498 ms | 706 ms | 0% |
| Bread page | 10.7 | 300 ms | 490 ms | 704 ms | 0% |
| Location page | 3.57 | 286 ms | 500 ms | 777 ms | 0% |
| Site search | 3.56 | 368 ms | 595 ms | 735 ms | 0% |
Editors in the Wagtail admin
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 1 virtual user | |||||
| Admin dashboard | 0.707 | 76.5 ms | 100 ms | 150 ms | 0% |
| Page explorer | 1.43 | 332 ms | 435 ms | 478 ms | 0% |
| Page editor | 2.12 | 157 ms | 196 ms | 276 ms | 0% |
| Image library | 0.707 | 58.8 ms | 69.7 ms | 510 ms | 0% |
| Admin page search | 0.707 | 34.5 ms | 79 ms | 83.5 ms | 0% |
| 4 virtual users | |||||
| Admin dashboard | 1.15 | 285 ms | 585 ms | 668 ms | 0% |
| Page explorer | 2.36 | 805 ms | 1.32 s | 1.45 s | 0% |
| Page editor | 3.51 | 370 ms | 694 ms | 763 ms | 0% |
| Image library | 1.17 | 229 ms | 477 ms | 550 ms | 0% |
| Admin page search | 1.15 | 97.4 ms | 275 ms | 485 ms | 0% |
k6 with a fixed number of virtual users, 60 to 61 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 298 MB, Postgres at 161 MB, and Redis at 26 MB.
Advertised vs. measured
| Spec | Advertised | Measured |
|---|---|---|
| vCPU | 2 | 2 |
| CPU | Shared vCPU | 0% 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 7642 48-Core Processor
- CPU cores
- 2
- CPU frequency
- 2300 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
- 0% 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
- Tokyo 2, JP
- 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 12, 2026, 04:08:47 UTC
- Parser version
- 5
Run timeline
- Queued
- Oct 12, 2026, 01:06:45 UTC
- Server created
- Oct 12, 2026, 04:08:41 UTC
- First update from the server
- Oct 12, 2026, 04:08:41 UTC
- Completed
- Oct 12, 2026, 05:47:29 UTC
- Server deleted
- Oct 12, 2026, 05:47:29 UTC
- Cost of this run
- $0.060
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.