Linode Linode 4GB
Server
-
ProviderLinode
-
PlanLinode 4GB
-
LocationFremont, CA
-
vCPU2
-
RAM4 GB
-
Storage80 GB SSD
-
Network4 Gbps
-
OS imagelinode/ubuntu24.04
-
TriggerScheduled
-
Queued atOct 11, 2026, 14:04:00 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,219 | 2,154 | 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,268
|
1,859
|
| Navigation |
1,301
|
Single-core only |
| HTML5 Browser |
1,128
|
Single-core only |
| PDF Viewer |
1,328
|
Single-core only |
| Photo Library |
1,070
|
2,100
|
| Clang |
1,108
|
2,288
|
| Text Processing |
1,067
|
2,000
|
| Asset Compression |
1,196
|
2,351
|
| HDR |
864
|
1,583
|
| Photo Editor |
1,353
|
2,704
|
| Ray Tracer |
1,359
|
2,580
|
| Structure from Motion |
1,583
|
Single-core only |
| Game Physics |
1,321
|
Single-core only |
| Video Encoder |
1,111
|
Single-core only |
| Audio Encoder |
1,307
|
Single-core only |
| Video Player |
1,313
|
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 | 44.2 GB/s | 3 | 25.5% |
| Scale higher is better | 30.1 GB/s | 3 | 15.3% |
| Add higher is better | 32.8 GB/s | 3 | 21.1% |
| Triad higher is better | 33.5 GB/s | 3 | 22.9% |
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 | 463/s | 3 | 0.0659% |
| RSA 4096 verifies higher is better | 30,107/s | 3 | 0.424% |
| SHA-256 higher is better | 1.41 GB/s | 3 | 0.566% |
| AES-256-GCM higher is better | 7.13 GB/s | 3 | 0.569% |
| ChaCha20-Poly1305 higher is better | 3.64 GB/s | 3 | 0.0772% |
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.575% |
| Requests per second, 90th percentile higher is better | 484/s | 3 | 0.207% |
| Request latency, 99.9th percentile lower is better | 7.22 ms | 3 | 6.03% |
| Requests per second, average higher is better | 480/s | 3 | 0.473% |
Average of 3 runs. Spread is the standard deviation as a share of the average.
Disk
| Block size | Read | Write | Total |
|---|---|---|---|
| 4K | 138.1 MB/s (35,366 IOPS) | 138.5 MB/s (35,459 IOPS) | 276.7 MB/s (70,825 IOPS) |
| 64K | 1.49 GB/s (24,480 IOPS) | 1.5 GB/s (24,609 IOPS) | 3 GB/s (49,089 IOPS) |
| 512K | 2.14 GB/s (4,375 IOPS) | 2.25 GB/s (4,607 IOPS) | 4.39 GB/s (8,982 IOPS) |
| 1M | 2.22 GB/s (2,270 IOPS) | 2.36 GB/s (2,421 IOPS) | 4.58 GB/s (4,691 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.26 Gbps | 1.58 Gbps |
| Eranium, Amsterdam, NL (100G) | IPv4 | 1.62 Gbps | 1.68 Gbps |
| Leaseweb, Singapore, SG (10G) | IPv4 | 951 Mbps | 1.28 Gbps |
| Clouvider, Los Angeles, CA, US (10G) | IPv4 | 4.35 Gbps | 8.56 Gbps |
| Leaseweb, NYC, NY, US (10G) | IPv4 | 2 Gbps | 3.81 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 | 13,371 | 0.075 ms |
| fdatasync | 7,640 | 0.131 ms |
| fsync | 6,031 | 0.166 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 6,715 | 0.149 ms |
| Two 8 kB writes | ||
| open_datasync | 6,603 | 0.151 ms |
| fdatasync | 7,111 | 0.141 ms |
| fsync | 5,642 | 0.177 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 3,048 | 0.328 ms |
| open_sync at different write sizes | ||
| 1 * 16kB open_sync write | 5,891 | 0.17 ms |
| 2 * 8kB open_sync writes | 2,938 | 0.34 ms |
| 4 * 4kB open_sync writes | 1,377 | 0.726 ms |
| 8 * 2kB open_sync writes | 489 | 2.05 ms |
| 16 * 1kB open_sync writes | 283 | 3.53 ms |
| fsync on a non-write descriptor | ||
| write, fsync, close | 5,600 | 0.179 ms |
| write, close, fsync | 5,524 | 0.181 ms |
| Non-synced 8 kB writes | ||
| write | 1,153,697 | 0.001 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,991 | 0.49 ms | 0.573 ms | 0.72 ms | 1.77 ms | 0 |
| Read/write (TPC-B like) | 8 | 5,170 | 1.46 ms | 2.44 ms | 3.2 ms | 4.52 ms | 0 |
| Read/write (TPC-B like) | 32 | 5,128 | 5.04 ms | 14.1 ms | 22.9 ms | 37.4 ms | 0 |
| Read only | 1 | 21,904 | 0.044 ms | 0.055 ms | 0.064 ms | 0.092 ms | 0 |
| Read only | 8 | 55,744 | 0.13 ms | 0.209 ms | 0.25 ms | 0.609 ms | 0 |
| Read only | 32 | 62,032 | 0.452 ms | 0.64 ms | 0.856 ms | 1.56 ms | 0 |
Scale 10 (1,000,000 accounts), loaded in 1.24 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,727 | 0.519 ms | 0.874 ms | 1.3 ms | 2.84 ms | 0 |
| Read/write (TPC-B like) | 8 | 4,827 | 1.56 ms | 2.53 ms | 4.41 ms | 9.61 ms | 0 |
| Read/write (TPC-B like) | 32 | 6,325 | 4.79 ms | 7.69 ms | 10.6 ms | 16.8 ms | 0 |
| Read only | 1 | 17,682 | 0.052 ms | 0.07 ms | 0.093 ms | 0.491 ms | 0 |
| Read only | 8 | 44,836 | 0.165 ms | 0.261 ms | 0.318 ms | 0.766 ms | 0 |
| Read only | 32 | 48,444 | 0.598 ms | 0.898 ms | 1.2 ms | 2.2 ms | 0 |
Scale 100 (10,000,000 accounts), loaded in 11.9 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 | 401 | 8,011 | 2.31 ms | 3.43 ms | 6.1 ms | 0 |
| Read/write | 8 | 865 | 17,299 | 9.22 ms | 14 ms | 17.3 ms | 0 |
| Read/write | 32 | 958 | 19,168 | 33.1 ms | 51.9 ms | 63.3 ms | 0 |
| Read only | 1 | 844 | 13,505 | 1.16 ms | 1.34 ms | 1.7 ms | 0 |
| Read only | 8 | 1,747 | 27,957 | 4.33 ms | 6.43 ms | 7.17 ms | 0 |
| Read only | 32 | 1,722 | 27,559 | 18 ms | 24.4 ms | 26.7 ms | 0 |
10 tables of 100,000 rows, loaded in 7 s. 60 s per run, one connection per thread.
Redis
memtier
| Mix | Operations/s | Hits/s | Median | p99 | p99.9 |
|---|---|---|---|---|---|
| 1:10 set:get | 73,852 | 67,137 | 0.511 ms | 2.99 ms | 4.45 ms |
| 1:1 set:get | 75,397 | 37,698 | 0.487 ms | 2.99 ms | 4.48 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 | 693 | 2,636 | 3,470 | 1.17 s |
| Express express-postgresjs | 8,112 | 12,103 | 34,520 | 54.5 ms |
| Fastify fastify-postgres | 7,868 | 12,834 | 37,522 | 67.7 ms |
| NestJS nestjs | 5,551 | 6,109 | 19,160 | 87.8 ms |
| Nuxt nuxt | 7,112 | 11,918 | 32,582 | 85 ms |
| FastAPI fastapi | 4,016 | 5,027 | 18,455 | 206 ms |
| Django django-postgresql | 2,029 | 2,403 | 5,360 | 212 ms |
| Rails rails | 3,544 | 4,807 | 16,892 | 107 ms |
| Laravel laravel | 907 | 948 | 1,736 | 331 ms |
| Symfony symfony | 1,183 | 1,303 | 3,599 | 225 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.3 | 702 ms | 783 ms | 812 ms | 0% |
| Shop page | 2.3 | 946 ms | 1.06 s | 1.08 s | 0% |
| Category page | 2.3 | 597 ms | 921 ms | 981 ms | 0% |
| Product page | 2.3 | 635 ms | 755 ms | 764 ms | 0% |
| Product search | 2.3 | 556 ms | 668 ms | 695 ms | 0% |
| 32 virtual users | |||||
| Home page | 2.32 | 2.52 s | 2.85 s | 3 s | 0% |
| Shop page | 2.32 | 3.35 s | 3.77 s | 3.85 s | 0% |
| Category page | 2.32 | 2.91 s | 3.51 s | 3.65 s | 0% |
| Product page | 2.32 | 2.5 s | 2.74 s | 2.85 s | 0% |
| Product search | 2.32 | 2.35 s | 2.55 s | 2.64 s | 0% |
Cart and checkout
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 8 virtual users | |||||
| Add to cart | 4.47 | 731 ms | 848 ms | 866 ms | 0% |
| Cart | 4.47 | 605 ms | 694 ms | 705 ms | 0% |
| Checkout | 4.47 | 468 ms | 536 ms | 548 ms | 0% |
| 32 virtual users | |||||
| Add to cart | 4.41 | 2.46 s | 2.96 s | 3.07 s | 0% |
| Cart | 4.41 | 2.61 s | 2.87 s | 2.98 s | 0% |
| Checkout | 4.41 | 2.05 s | 2.35 s | 2.47 s | 0% |
k6 with a fixed number of virtual users, 62 to 69 s per level. The error rate counts responses that weren't a 200.
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 7542 32-Core Processor
- CPU cores
- 2
- CPU frequency
- 2900 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
- Fremont, CA
- 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 11, 2026, 14:05:33 UTC
- Parser version
- 5
Run timeline
- Queued
- Oct 11, 2026, 14:04:00 UTC
- Server created
- Oct 11, 2026, 14:05:29 UTC
- First update from the server
- Oct 11, 2026, 14:05:29 UTC
- Completed
- Oct 11, 2026, 15:21:10 UTC
- Server deleted
- Oct 11, 2026, 15:21:10 UTC
- Cost of this run
- $0.046
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.