Skip to main content

Linode Linode 4GB

Chicago, IL

Benchmark complete
Finished Oct 12, 2026
Geekbench 7 single-core
857
Faster than 30% of 2 vCPU plans
Geekbench 7 multi-core
1,671
Faster than 42% of 2 vCPU plans
Disk 4K IOPS
13,453
fio random read and write, 50/50
Monthly price at test time
$24.00
70 multi-core points per dollar
Same price today

Server

  • Provider
    Linode
  • Plan
    Linode 4GB
  • Location
    Chicago, IL
  • vCPU
    2
  • RAM
    4 GB
  • Storage
    80 GB SSD
  • Network
    4 Gbps
  • OS image
    linode/ubuntu24.04
  • Trigger
    Scheduled
  • Queued at
    Oct 12, 2026, 15:18:00 UTC
Visit Linode

Referral link. If you sign up through it, I may get paid. How this works

CPU

Version Single-core Multi-core Result link
Geekbench 7 857 1,671 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
918
109th of 129
1,462
83rd of 103
Navigation
854
121st of 129
Single-core only
HTML5 Browser
792
113th of 129
Single-core only
PDF Viewer
848
115th of 129
Single-core only
Photo Library
748
100th of 129
1,529
78th of 103
Clang
739
115th of 129
1,564
79th of 103
Text Processing
673
116th of 129
1,367
83rd of 103
Asset Compression
917
101st of 129
1,933
74th of 103
HDR
738
115th of 129
1,548
76th of 103
Photo Editor
929
95th of 129
2,336
58th of 103
Ray Tracer
834
111th of 129
1,819
81st of 103
Structure from Motion
900
105th of 129
Single-core only
Game Physics
953
99th of 129
Single-core only
Video Encoder
948
91st of 129
Single-core only
Audio Encoder
1,025
92nd of 129
Single-core only
Video Player
980
90th of 129
Single-core only

Rank among the 129 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 43.1 GB/s 3 1.4%
Scale higher is better 32.8 GB/s 3 0.869%
Add higher is better 34 GB/s 3 0.585%
Triad higher is better 34.9 GB/s 3 1.89%

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 337/s 3 1.21%
RSA 4096 verifies higher is better 22,363/s 3 3.52%
SHA-256 higher is better 1.18 GB/s 3 1.83%
AES-256-GCM higher is better 5.57 GB/s 3 1.56%
ChaCha20-Poly1305 higher is better 3.89 GB/s 3 0.787%

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 6.09 ms 3 1.2%
Requests per second, 90th percentile higher is better 346/s 3 0.289%
Request latency, 99.9th percentile lower is better 24.1 ms 3 51.7%
Requests per second, average higher is better 308/s 3 4.45%

Average of 3 runs. Spread is the standard deviation as a share of the average.

Disk

Block size Read Write Total
4K 26.3 MB/s (6,724 IOPS) 26.3 MB/s (6,729 IOPS) 52.6 MB/s (13,453 IOPS)
64K 251 MB/s (4,016 IOPS) 252.3 MB/s (4,037 IOPS) 503.4 MB/s (8,053 IOPS)
512K 486.7 MB/s (973 IOPS) 512.6 MB/s (1,025 IOPS) 999.3 MB/s (1,998 IOPS)
1M 449.8 MB/s (449 IOPS) 479.8 MB/s (479 IOPS) 929.6 MB/s (928 IOPS)

fio random read and write, 50/50, run by YABS against the boot disk.

Network

IPv4 transfer speed

Loading...
Target Protocol Send Receive
Clouvider, London, UK (10G) IPv4 1.98 Gbps 2.5 Gbps
Eranium, Amsterdam, NL (100G) IPv4 2.11 Gbps 2.02 Gbps
Leaseweb, Singapore, SG (10G) IPv4 830 Mbps 1 Gbps
Clouvider, Los Angeles, CA, US (10G) IPv4 2.06 Gbps 3.83 Gbps
Leaseweb, NYC, NY, US (10G) IPv4 4.26 Gbps 9.26 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 6,943 0.144 ms
fdatasync 4,002 0.25 ms
fsync 2,015 0.496 ms
fsync_writethrough Not supported here n/a
open_sync 2,025 0.494 ms
Two 8 kB writes
open_datasync 3,013 0.332 ms
fdatasync 3,477 0.288 ms
fsync 2,221 0.45 ms
fsync_writethrough Not supported here n/a
open_sync 1,460 0.685 ms
open_sync at different write sizes
1 * 16kB open_sync write 2,312 0.432 ms
2 * 8kB open_sync writes 1,367 0.732 ms
4 * 4kB open_sync writes 737 1.36 ms
8 * 2kB open_sync writes 254 3.94 ms
16 * 1kB open_sync writes 125 7.97 ms
fsync on a non-write descriptor
write, fsync, close 2,486 0.402 ms
write, close, fsync 2,387 0.419 ms
Non-synced 8 kB writes
write 319,934 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,100 0.854 ms 1.12 ms 1.94 ms 8.52 ms 0
Read/write (TPC-B like) 8 2,935 2.53 ms 4.45 ms 6.04 ms 9.94 ms 0
Read/write (TPC-B like) 32 2,677 9.19 ms 28.3 ms 52.1 ms 107 ms 0
Read only 1 12,225 0.077 ms 0.114 ms 0.139 ms 0.223 ms 0
Read only 8 31,920 0.217 ms 0.384 ms 0.498 ms 1.99 ms 0
Read only 32 33,099 0.783 ms 1.38 ms 1.88 ms 4.94 ms 0

Scale 10 (1,000,000 accounts), loaded in 2.06 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 969 0.952 ms 1.35 ms 2.19 ms 5.88 ms 0
Read/write (TPC-B like) 8 2,456 2.95 ms 5.07 ms 9.22 ms 42.6 ms 0
Read/write (TPC-B like) 32 2,846 10.3 ms 17.6 ms 27.5 ms 66.4 ms 0
Read only 1 7,723 0.109 ms 0.193 ms 0.541 ms 1.95 ms 0
Read only 8 23,196 0.305 ms 0.546 ms 0.803 ms 2.61 ms 0
Read only 32 24,255 1.12 ms 2.08 ms 2.93 ms 6.18 ms 0

Scale 100 (10,000,000 accounts), loaded in 21.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 220 4,400 4.1 ms 6.55 ms 10.5 ms 0
Read/write 8 468 9,358 16.4 ms 26.7 ms 41.9 ms 0
Read/write 32 452 9,030 68.1 ms 121 ms 174 ms 0
Read only 1 407 6,520 2.22 ms 3.75 ms 6.32 ms 0
Read only 8 931 14,893 8.28 ms 11.9 ms 15 ms 0
Read only 32 913 14,606 33.7 ms 45 ms 60 ms 0

10 tables of 100,000 rows, loaded in 13.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 35,198 31,998 1.5 ms 5.18 ms 16.9 ms
1:1 set:get 36,327 18,163 1.42 ms 4.45 ms 6.78 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 402 1,467 2,154 1.17 s
Express express-postgresjs 5,533 6,693 16,144 156 ms
Fastify fastify-postgres 5,311 8,102 17,330 302 ms
NestJS nestjs 2,826 3,506 10,861 242 ms
Nuxt nuxt 4,437 6,844 15,790 122 ms
FastAPI fastapi 2,136 2,771 10,215 604 ms
Django django-postgresql 1,020 1,239 2,658 651 ms
Rails rails 1,806 2,491 7,853 204 ms
Laravel laravel 444 478 913 619 ms
Symfony symfony 625 658 1,713 443 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.3 1.24 s 1.4 s 1.49 s 0%
Shop page 1.3 1.66 s 1.88 s 1.99 s 0%
Category page 1.3 1.04 s 1.66 s 1.74 s 0%
Product page 1.3 1.09 s 1.31 s 1.36 s 0%
Product search 1.3 952 ms 1.15 s 1.27 s 0%
32 virtual users
Home page 1.35 4.27 s 4.97 s 5.11 s 0%
Shop page 1.35 5.83 s 7.26 s 7.38 s 0%
Category page 1.35 5.71 s 6.99 s 7.36 s 0%
Product page 1.32 4.36 s 4.82 s 4.98 s 0%
Product search 0.916 4.16 s 4.54 s 4.65 s 0%

Cart and checkout

Step Requests/s Median p95 p99 Error rate
8 virtual users
Add to cart 2.54 1.27 s 1.54 s 1.64 s 0%
Cart 2.54 997 ms 1.19 s 1.27 s 0%
Checkout 2.54 768 ms 937 ms 1 s 0%
32 virtual users
Add to cart 2.42 4.42 s 5.8 s 6.12 s 0%
Cart 2.42 4.75 s 5.66 s 5.85 s 0%
Checkout 2.42 3.56 s 4.46 s 5.04 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.22 350 ms 513 ms 830 ms 0%
Topic JSON 0.609 175 ms 287 ms 538 ms 0%
Home page 0.609 309 ms 484 ms 735 ms 0%
Categories page 0.313 366 ms 480 ms 616 ms 0%
User activity page 0.296 211 ms 518 ms 519 ms 0%
4 virtual users
Topic page 2.1 830 ms 1.08 s 1.83 s 0%
Topic JSON 1.03 444 ms 575 ms 626 ms 0%
Home page 1.03 755 ms 987 ms 1.92 s 0%
Categories page 0.524 854 ms 1.54 s 2.07 s 0%
User activity page 0.524 484 ms 729 ms 1.8 s 0%
16 virtual users
Topic page 2 2.14 s 2.81 s 3.22 s 0%
Topic JSON 0.975 1.7 s 2.52 s 2.76 s 0%
Home page 0.991 1.97 s 2.83 s 3.7 s 0%
Categories page 0.495 2.15 s 2.95 s 3.22 s 0%
User activity page 0.527 1.62 s 2.18 s 2.25 s 0%

Anonymous

Step Requests/s Median p95 p99 Error rate
16 virtual users
Topic page 43.1 104 ms 247 ms 332 ms 0.0767%
Topic JSON 21.6 101 ms 251 ms 381 ms 0.0765%
Home page 21.6 107 ms 254 ms 339 ms 0%
Categories page 10.8 101 ms 247 ms 409 ms 0.152%
User activity page 10.8 318 ms 542 ms 705 ms 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. 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,019 MB.

Ghost

Readers

Step Requests/s Median p95 p99 Error rate
1 virtual user
Home page 5.38 51.3 ms 64 ms 123 ms 0%
Post page 13.4 27.8 ms 36.7 ms 67.1 ms 0%
Tag page 2.7 34.6 ms 46 ms 75.2 ms 0%
Author page 2.68 35 ms 45.2 ms 72.5 ms 0%
RSS feed 2.68 43.3 ms 55.1 ms 68.5 ms 0%
4 virtual users
Home page 6.74 151 ms 210 ms 313 ms 0%
Post page 16.8 109 ms 159 ms 234 ms 0%
Tag page 3.38 94.1 ms 131 ms 182 ms 0%
Author page 3.38 95.6 ms 134 ms 188 ms 0%
RSS feed 3.33 107 ms 143 ms 197 ms 0%
16 virtual users
Home page 6.56 596 ms 785 ms 1.29 s 0%
Post page 16.4 501 ms 646 ms 1.15 s 0%
Tag page 3.28 327 ms 447 ms 529 ms 0%
Author page 3.28 323 ms 440 ms 746 ms 0%
RSS feed 3.28 332 ms 449 ms 647 ms 0%

Staff in Ghost Admin

Step Requests/s Median p95 p99 Error rate
1 virtual user
Post list 3.02 50.4 ms 65.2 ms 143 ms 0%
Post editor 9.08 18.1 ms 27.3 ms 46.7 ms 0%
Saving a draft 9.08 44.9 ms 60.8 ms 147 ms 0%
Member list 3.02 59.2 ms 84.7 ms 118 ms 0%
4 virtual users
Post list 3.47 70.5 ms 97.4 ms 155 ms 0%
Post editor 10.5 36.2 ms 49.7 ms 68.7 ms 0%
Saving a draft 10.5 274 ms 383 ms 536 ms 0%
Member list 3.5 79 ms 106 ms 198 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. 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 366 MB and MySQL at 620 MB.

Wagtail

Visitors

Step Requests/s Median p95 p99 Error rate
1 virtual user
Home page 0.98 140 ms 170 ms 175 ms 0%
Blog index 0.964 467 ms 547 ms 580 ms 0%
Blog post 2.91 42.8 ms 63.7 ms 81.1 ms 0%
Bread page 2.92 46.9 ms 59.7 ms 67.5 ms 0%
Location page 0.98 46.2 ms 52.7 ms 56.9 ms 0%
Site search 0.964 72.2 ms 116 ms 128 ms 0%
4 virtual users
Home page 1.65 362 ms 480 ms 677 ms 0%
Blog index 1.67 1.09 s 1.73 s 2.09 s 0%
Blog post 4.96 99.6 ms 156 ms 225 ms 0%
Bread page 4.98 110 ms 161 ms 212 ms 0%
Location page 1.69 105 ms 141 ms 170 ms 0%
Site search 1.64 166 ms 341 ms 382 ms 0%
16 virtual users
Home page 1.78 1.06 s 1.41 s 2.33 s 0%
Blog index 1.79 2.58 s 3.02 s 3.54 s 0%
Blog post 5.24 580 ms 945 ms 1.16 s 0%
Bread page 5.24 607 ms 1.04 s 1.34 s 0%
Location page 1.76 611 ms 872 ms 1.09 s 0%
Site search 1.76 720 ms 1.15 s 1.6 s 0%

Editors in the Wagtail admin

Step Requests/s Median p95 p99 Error rate
1 virtual user
Admin dashboard 0.343 151 ms 217 ms 270 ms 0%
Page explorer 0.703 684 ms 924 ms 1.37 s 0%
Page editor 1.03 309 ms 414 ms 561 ms 0%
Image library 0.343 114 ms 353 ms 1.21 s 0%
Admin page search 0.343 61 ms 129 ms 134 ms 0%
4 virtual users
Admin dashboard 0.54 456 ms 1.04 s 1.2 s 0%
Page explorer 1.13 1.55 s 2.65 s 3.01 s 0%
Page editor 1.67 881 ms 1.56 s 1.8 s 0%
Image library 0.54 522 ms 874 ms 1.16 s 0%
Admin page search 0.54 176 ms 390 ms 576 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 292 MB, Postgres at 157 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
Chicago, IL
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, 15:21:28 UTC
Parser version
5

Run timeline

Queued
Oct 12, 2026, 15:18:00 UTC
Server created
Oct 12, 2026, 15:19:51 UTC
First update from the server
Oct 12, 2026, 15:19:51 UTC
Completed
Oct 12, 2026, 17:06:25 UTC
Server deleted
Oct 12, 2026, 17:06:25 UTC
Cost of this run
$0.065
Watch party 0 watching

This party closed at . It's read only now.

Watch party

Loading the party