Skip to main content

Linode Linode 8GB

Newark, NJ

Benchmark complete
Finished Oct 15, 2026
Geekbench 7 single-core
915
Faster than 22% of 4 vCPU plans
Geekbench 7 multi-core
2,821
Faster than 31% of 4 vCPU plans
Disk 4K IOPS
58,911
fio random read and write, 50/50
Monthly price at test time
$48.00
59 multi-core points per dollar
Same price today

Server

  • Provider
    Linode
  • Plan
    Linode 8GB
  • Location
    Newark, NJ
  • vCPU
    4
  • RAM
    8 GB
  • Storage
    160 GB SSD
  • Network
    5 Gbps
  • OS image
    linode/ubuntu24.04
  • Trigger
    Scheduled
  • Queued at
    Oct 15, 2026, 13:55: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 915 2,821 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,049
127th of 186
3,180
39th of 131
Navigation
958
152nd of 186
Single-core only
HTML5 Browser
930
128th of 186
Single-core only
PDF Viewer
872
154th of 186
Single-core only
Photo Library
774
136th of 186
2,961
55th of 131
Clang
944
129th of 186
3,836
41st of 131
Text Processing
844
142nd of 186
2,412
64th of 131
Asset Compression
1,021
129th of 186
4,196
43rd of 131
HDR
829
137th of 186
2,355
67th of 131
Photo Editor
579
170th of 186
1,143
116th of 131
Ray Tracer
1,000
118th of 186
4,081
45th of 131
Structure from Motion
1,029
135th of 186
Single-core only
Game Physics
995
122nd of 186
Single-core only
Video Encoder
898
131st of 186
Single-core only
Audio Encoder
1,088
119th of 186
Single-core only
Video Player
988
123rd of 186
Single-core only

Rank among the 186 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 36.8 GB/s 3 3.49%
Scale higher is better 29.5 GB/s 3 0.934%
Add higher is better 29.5 GB/s 3 1.6%
Triad higher is better 30.1 GB/s 3 1.48%

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 702/s 3 24.4%
RSA 4096 verifies higher is better 54,233/s 3 1.92%
SHA-256 higher is better 2.52 GB/s 3 0.892%
AES-256-GCM higher is better 11.9 GB/s 3 2.64%
ChaCha20-Poly1305 higher is better 6.66 GB/s 3 1.11%

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.04 ms 3 1.5%
Requests per second, 90th percentile higher is better 790/s 3 4.5%
Request latency, 99.9th percentile lower is better 32 ms 3 48.7%
Requests per second, average higher is better 674/s 3 5.88%

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

Disk

Block size Read Write Total
4K 114.9 MB/s (29,417 IOPS) 115.2 MB/s (29,494 IOPS) 230.1 MB/s (58,911 IOPS)
64K 973.6 MB/s (15,577 IOPS) 978.7 MB/s (15,659 IOPS) 1.91 GB/s (31,236 IOPS)
512K 2.36 GB/s (4,842 IOPS) 2.49 GB/s (5,099 IOPS) 4.85 GB/s (9,941 IOPS)
1M 3.01 GB/s (3,082 IOPS) 3.21 GB/s (3,287 IOPS) 6.22 GB/s (6,369 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 2.23 Gbps 2.68 Gbps
Eranium, Amsterdam, NL (100G) IPv4 2.04 Gbps 3.12 Gbps
Leaseweb, Singapore, SG (10G) IPv4 377 Mbps 885 Mbps
Clouvider, Los Angeles, CA, US (10G) IPv4 2 Gbps 3.58 Gbps
Leaseweb, NYC, NY, US (10G) IPv4 5.51 Gbps 7.68 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,218 0.192 ms
fdatasync 5,700 0.175 ms
fsync 3,719 0.269 ms
fsync_writethrough Not supported here n/a
open_sync 4,237 0.236 ms
Two 8 kB writes
open_datasync 4,973 0.201 ms
fdatasync 5,114 0.196 ms
fsync 3,326 0.301 ms
fsync_writethrough Not supported here n/a
open_sync 2,088 0.479 ms
open_sync at different write sizes
1 * 16kB open_sync write 3,828 0.261 ms
2 * 8kB open_sync writes 1,502 0.666 ms
4 * 4kB open_sync writes 700 1.43 ms
8 * 2kB open_sync writes 316 3.16 ms
16 * 1kB open_sync writes 176 5.67 ms
fsync on a non-write descriptor
write, fsync, close 3,155 0.317 ms
write, close, fsync 3,576 0.28 ms
Non-synced 8 kB writes
write 496,249 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,285 0.723 ms 1.02 ms 1.75 ms 14.1 ms 0
Read/write (TPC-B like) 8 5,213 1.28 ms 2.7 ms 4.67 ms 26.1 ms 0
Read/write (TPC-B like) 32 5,139 4.56 ms 15 ms 28.3 ms 69.1 ms 0
Read only 1 13,787 0.065 ms 0.099 ms 0.219 ms 0.438 ms 0
Read only 8 59,001 0.117 ms 0.233 ms 0.353 ms 0.881 ms 0
Read only 32 69,806 0.378 ms 0.681 ms 0.952 ms 3.09 ms 0

Scale 10 (1,000,000 accounts), loaded in 1.92 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 979 0.904 ms 1.51 ms 3.03 ms 13.5 ms 0
Read/write (TPC-B like) 8 4,515 1.49 ms 2.62 ms 5.45 ms 43.1 ms 0
Read/write (TPC-B like) 32 5,992 4.66 ms 8.73 ms 18.1 ms 59.1 ms 0
Read only 1 10,725 0.085 ms 0.133 ms 0.239 ms 0.541 ms 0
Read only 8 46,920 0.148 ms 0.295 ms 0.426 ms 1.63 ms 0
Read only 32 56,555 0.485 ms 0.85 ms 1.19 ms 3.9 ms 0

Scale 100 (10,000,000 accounts), loaded in 35.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.

MySQL

sysbench OLTP

Workload Threads Transactions/s Queries/s Median p95 p99 Errors
Read/write 1 271 5,416 3.36 ms 5.28 ms 9.56 ms 0
Read/write 8 904 18,086 8.28 ms 14.2 ms 21.5 ms 0
Read/write 32 1,038 20,756 28.7 ms 53.9 ms 78.6 ms 0
Read only 1 501 8,013 1.79 ms 3.02 ms 5.88 ms 0
Read only 8 2,449 39,188 3.13 ms 4.57 ms 6.55 ms 0
Read only 32 2,196 35,132 14 ms 19.3 ms 25.3 ms 0

10 tables of 100,000 rows, loaded in 6.4 s. 60 s per run, one connection per thread.

Redis

memtier

Mix Operations/s Hits/s Median p99 p99.9
1:10 set:get 50,117 45,560 1.18 ms 2.85 ms 15 ms
1:1 set:get 52,815 26,407 1.14 ms 2.45 ms 11.3 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 894 3,319 5,079 1.66 s
Express express-postgresjs 9,479 15,369 44,039 220 ms
Fastify fastify-postgres 11,534 15,655 45,480 55.8 ms
NestJS nestjs 5,381 7,538 29,188 79.2 ms
Nuxt nuxt 9,296 13,807 36,513 70.1 ms
FastAPI fastapi 5,553 6,806 21,725 202 ms
Django django-postgresql 2,637 2,948 7,310 288 ms
Rails rails 3,913 5,815 21,448 120 ms
Laravel laravel 1,187 1,259 2,405 258 ms
Symfony symfony 1,280 1,558 4,672 233 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 3 520 ms 706 ms 873 ms 0%
Shop page 3 658 ms 926 ms 1 s 0%
Category page 3 459 ms 757 ms 887 ms 0%
Product page 3 473 ms 676 ms 1.06 s 0%
Product search 3 426 ms 594 ms 831 ms 0%
32 virtual users
Home page 3.17 1.9 s 2.16 s 2.21 s 0%
Shop page 3.17 2.34 s 3.52 s 4.01 s 0%
Category page 3.17 1.9 s 3.1 s 3.4 s 0%
Product page 3.17 1.82 s 2.11 s 2.24 s 0%
Product search 3.17 1.68 s 1.91 s 2.01 s 0%

Cart and checkout

Step Requests/s Median p95 p99 Error rate
8 virtual users
Add to cart 5.79 543 ms 732 ms 1.02 s 0%
Cart 5.79 458 ms 638 ms 829 ms 0%
Checkout 5.79 351 ms 475 ms 571 ms 0%
32 virtual users
Add to cart 5.93 1.93 s 2.52 s 2.96 s 0%
Cart 5.93 1.79 s 2.19 s 2.39 s 0%
Checkout 5.93 1.49 s 2.16 s 2.77 s 0%

k6 with a fixed number of virtual users, 61 to 69 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.67 255 ms 585 ms 747 ms 0%
Topic JSON 0.842 127 ms 170 ms 227 ms 0%
Home page 0.842 228 ms 302 ms 446 ms 0%
Categories page 0.413 262 ms 323 ms 948 ms 0%
User activity page 0.413 156 ms 358 ms 493 ms 0%
4 virtual users
Topic page 5.25 330 ms 481 ms 851 ms 0%
Topic JSON 2.64 179 ms 244 ms 357 ms 0%
Home page 2.63 295 ms 465 ms 770 ms 0%
Categories page 1.34 341 ms 774 ms 1.08 s 0%
User activity page 1.3 199 ms 278 ms 566 ms 0%
16 virtual users
Topic page 4.49 1.42 s 2.4 s 2.88 s 0%
Topic JSON 2.24 1.09 s 1.64 s 1.96 s 0%
Home page 2.24 1.35 s 2.03 s 2.58 s 0%
Categories page 1.11 1.45 s 2.45 s 3.65 s 0%
User activity page 1.12 1.08 s 1.4 s 2.22 s 0%

Anonymous

Step Requests/s Median p95 p99 Error rate
16 virtual users
Topic page 83.2 45.6 ms 97.5 ms 166 ms 0%
Topic JSON 41.6 42.7 ms 94.9 ms 176 ms 0%
Home page 41.6 45.1 ms 98.8 ms 172 ms 0%
Categories page 20.8 46.8 ms 104 ms 192 ms 0%
User activity page 20.8 272 ms 464 ms 764 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 8 app workers and 2048 MB of Postgres shared buffers, what its installer picks for a 8 GB box. Its installer adds no swap on a box this big. The container peaked at 2,459 MB.

Ghost

Readers

Step Requests/s Median p95 p99 Error rate
1 virtual user
Home page 5.78 50.7 ms 65.5 ms 80 ms 0%
Post page 14.4 25.9 ms 35.3 ms 43.9 ms 0%
Tag page 2.88 29.8 ms 40.9 ms 49 ms 0%
Author page 2.88 33.7 ms 45.3 ms 55.2 ms 0%
RSS feed 2.88 34.4 ms 49.2 ms 59.7 ms 0%
4 virtual users
Home page 7.99 132 ms 174 ms 216 ms 0%
Post page 20 88.6 ms 132 ms 169 ms 0%
Tag page 3.99 78.9 ms 122 ms 138 ms 0%
Author page 3.99 86.4 ms 129 ms 262 ms 0%
RSS feed 3.99 86.2 ms 128 ms 189 ms 0%
16 virtual users
Home page 8.72 457 ms 553 ms 1.03 s 0%
Post page 21.7 380 ms 471 ms 769 ms 0%
Tag page 4.33 256 ms 323 ms 731 ms 0%
Author page 4.31 259 ms 325 ms 436 ms 0%
RSS feed 4.33 256 ms 328 ms 361 ms 0%

Staff in Ghost Admin

Step Requests/s Median p95 p99 Error rate
1 virtual user
Post list 3.74 39.8 ms 51.4 ms 72.3 ms 0%
Post editor 11.3 14.9 ms 21.4 ms 32.7 ms 0%
Saving a draft 11.2 37.1 ms 50.9 ms 72.1 ms 0%
Member list 3.75 48.1 ms 62.3 ms 84.5 ms 0%
4 virtual users
Post list 4.6 53.3 ms 75.1 ms 108 ms 0%
Post editor 13.8 27.5 ms 37.7 ms 62.6 ms 0%
Saving a draft 13.9 209 ms 273 ms 393 ms 0%
Member list 4.61 64.3 ms 85 ms 158 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 540 MB and MySQL at 625 MB.

Wagtail

Visitors

Step Requests/s Median p95 p99 Error rate
1 virtual user
Home page 1.11 122 ms 166 ms 248 ms 0%
Blog index 1.11 389 ms 518 ms 840 ms 0%
Blog post 3.31 36.7 ms 67.3 ms 81.3 ms 0%
Bread page 3.32 39.1 ms 58.2 ms 77.5 ms 0%
Location page 1.11 37.6 ms 54 ms 67.2 ms 0%
Site search 1.1 62.2 ms 111 ms 136 ms 0%
4 virtual users
Home page 2.2 232 ms 388 ms 740 ms 0%
Blog index 2.25 827 ms 1.4 s 1.83 s 0%
Blog post 6.59 67.7 ms 138 ms 226 ms 0%
Bread page 6.64 73.9 ms 139 ms 258 ms 0%
Location page 2.25 61.6 ms 132 ms 196 ms 0%
Site search 2.18 106 ms 228 ms 288 ms 0%
16 virtual users
Home page 2.61 678 ms 975 ms 1.1 s 0%
Blog index 2.69 1.84 s 2.48 s 3.19 s 0%
Blog post 7.93 389 ms 597 ms 726 ms 0%
Bread page 7.95 387 ms 587 ms 892 ms 0%
Location page 2.67 375 ms 598 ms 1.36 s 0%
Site search 2.65 466 ms 821 ms 1.08 s 0%

Editors in the Wagtail admin

Step Requests/s Median p95 p99 Error rate
1 virtual user
Admin dashboard 0.494 106 ms 140 ms 162 ms 0%
Page explorer 1.02 444 ms 630 ms 1.46 s 0%
Page editor 1.5 212 ms 279 ms 453 ms 0%
Image library 0.494 81 ms 164 ms 787 ms 0%
Admin page search 0.494 48.8 ms 92.8 ms 105 ms 0%
4 virtual users
Admin dashboard 0.807 379 ms 741 ms 810 ms 0%
Page explorer 1.63 1.1 s 2.08 s 3.5 s 0%
Page editor 2.49 507 ms 928 ms 1.1 s 0%
Image library 0.84 249 ms 616 ms 706 ms 0%
Admin page search 0.807 139 ms 323 ms 396 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 293 MB, Postgres at 151 MB, and Redis at 26 MB.

Advertised vs. measured

Spec Advertised Measured
vCPU 4 4
CPU Shared vCPU 2.2% of busy CPU time stolen
RAM 8 GB 7.8 GiB
Storage 160 GB SSD 156.9 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
4
CPU frequency
2300 MHz
AES-NI
Yes
VM-x/AMD-V
No
RAM reported
7.8 GiB
Swap reported
496 MiB
Disk reported
156.9 GiB
Virtualization reported
KVM
CPU steal
2.2% 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 8GB
Product line
Shared CPU
Location
Newark, NJ
vCPU
4 shared vCPU
Architecture
x86_64
RAM
8 GB
Storage
160 GB SSD
Virtualization
KVM
Network
5 Gbps
Transfer
5 TB
Port 25
On request
Monthly price at test time
$48.00
Hourly price at test time
$0.072
YABS version
v2026-09-20
Ran at
Oct 15, 2026, 13:56:59 UTC
Parser version
5

Run timeline

Queued
Oct 15, 2026, 13:55:00 UTC
Server created
Oct 15, 2026, 13:56:54 UTC
First update from the server
Oct 15, 2026, 13:56:54 UTC
Completed
Oct 15, 2026, 15:35:47 UTC
Server deleted
Oct 15, 2026, 15:35:47 UTC
Cost of this run
$0.12
Watch party 0 watching

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

Watch party

Loading the party