Linode Linode 2GB
Server
-
ProviderLinode
-
PlanLinode 2GB
-
LocationNewark, NJ
-
vCPU1
-
RAM2 GB
-
Storage50 GB SSD
-
Network2 Gbps
-
OS imagelinode/ubuntu24.04
-
TriggerScheduled
-
Queued atOct 11, 2026, 06:46:00 UTC
Referral link. If you sign up through it, I may get paid.
CPU
| Version | Single-core | Multi-core | Result link |
|---|---|---|---|
| Geekbench 7 | 972 | Skipped | Geekbench Browser |
Multi-core was skipped because Geekbench 7 needs about 2.1 GB of free memory to run 1 thread, and this server didn't have that much. Single-core needs much less, so it still ran.
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,001
|
Single-core only |
| Navigation |
1,042
|
Single-core only |
| HTML5 Browser |
900
|
Single-core only |
| PDF Viewer |
990
|
Single-core only |
| Photo Library |
915
|
Single-core only |
| Clang |
815
|
Single-core only |
| Text Processing |
813
|
Single-core only |
| Asset Compression |
1,081
|
Single-core only |
| HDR |
998
|
Single-core only |
| Photo Editor |
691
|
Single-core only |
| Ray Tracer |
987
|
Single-core only |
| Structure from Motion |
1,106
|
Single-core only |
| Game Physics |
1,030
|
Single-core only |
| Video Encoder |
1,007
|
Single-core only |
| Audio Encoder |
1,173
|
Single-core only |
| Video Player |
1,133
|
Single-core only |
Rank among the 70 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 | 33.1 GB/s | 3 | 3.5% |
| Scale higher is better | 23.3 GB/s | 3 | 3.86% |
| Add higher is better | 26.9 GB/s | 3 | 5.11% |
| Triad higher is better | 27.9 GB/s | 3 | 4.92% |
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 | 154/s | 3 | 23.9% |
| RSA 4096 verifies higher is better | 10,201/s | 3 | 22.6% |
| SHA-256 higher is better | 651 MB/s | 3 | 8.27% |
| AES-256-GCM higher is better | 2.9 GB/s | 3 | 8.46% |
| ChaCha20-Poly1305 higher is better | 1.95 GB/s | 3 | 2.91% |
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.51 ms | 3 | 0.605% |
| Requests per second, 90th percentile higher is better | 181/s | 3 | 0% |
| Request latency, 99.9th percentile lower is better | 31.4 ms | 3 | 55.8% |
| Requests per second, average higher is better | 162/s | 3 | 4.01% |
Average of 3 runs. Spread is the standard deviation as a share of the average.
Disk
| Block size | Read | Write | Total |
|---|---|---|---|
| 4K | 102.9 MB/s (26,352 IOPS) | 103.2 MB/s (26,422 IOPS) | 206.1 MB/s (52,774 IOPS) |
| 64K | 1.11 GB/s (18,217 IOPS) | 1.12 GB/s (18,313 IOPS) | 2.23 GB/s (36,530 IOPS) |
| 512K | 2.02 GB/s (4,130 IOPS) | 2.12 GB/s (4,349 IOPS) | 4.14 GB/s (8,479 IOPS) |
| 1M | 2.48 GB/s (2,534 IOPS) | 2.64 GB/s (2,703 IOPS) | 5.12 GB/s (5,237 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 | 2.04 Gbps | 2.9 Gbps |
| Eranium, Amsterdam, NL (100G) | IPv4 | 1.43 Gbps | 3.06 Gbps |
| Leaseweb, Singapore, SG (10G) | IPv4 | 834 Mbps | 996 Mbps |
| Clouvider, Los Angeles, CA, US (10G) | IPv4 | 1.58 Gbps | 3.61 Gbps |
| Leaseweb, NYC, NY, US (10G) | IPv4 | 2.2 Gbps | 5.98 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,093 | 0.124 ms |
| fdatasync | 4,106 | 0.244 ms |
| fsync | 1,208 | 0.828 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 963 | 1.04 ms |
| Two 8 kB writes | ||
| open_datasync | 3,967 | 0.252 ms |
| fdatasync | 4,225 | 0.237 ms |
| fsync | 2,980 | 0.336 ms |
| fsync_writethrough | Not supported here | n/a |
| open_sync | 1,888 | 0.53 ms |
| open_sync at different write sizes | ||
| 1 * 16kB open_sync write | 3,645 | 0.274 ms |
| 2 * 8kB open_sync writes | 1,767 | 0.566 ms |
| 4 * 4kB open_sync writes | 930 | 1.08 ms |
| 8 * 2kB open_sync writes | 314 | 3.19 ms |
| 16 * 1kB open_sync writes | 84.1 | 11.9 ms |
| fsync on a non-write descriptor | ||
| write, fsync, close | 489 | 2.04 ms |
| write, close, fsync | 3,104 | 0.322 ms |
| Non-synced 8 kB writes | ||
| write | 331,912 | 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,317 | 0.676 ms | 1.16 ms | 1.92 ms | 6.29 ms | 0 |
| Read/write (TPC-B like) | 8 | 1,503 | 4.52 ms | 9.86 ms | 15.5 ms | 30.9 ms | 0 |
| Read/write (TPC-B like) | 32 | 1,520 | 16.6 ms | 45.5 ms | 82 ms | 172 ms | 0 |
| Read only | 1 | 16,953 | 0.051 ms | 0.089 ms | 0.214 ms | 0.689 ms | 0 |
| Read only | 8 | 16,325 | 0.373 ms | 0.822 ms | 1.3 ms | 4.8 ms | 0 |
| Read only | 32 | 16,703 | 1.47 ms | 2.48 ms | 3.44 ms | 6.05 ms | 0 |
Scale 10 (1,000,000 accounts), loaded in 2.44 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 | 640 | 1.31 ms | 2.75 ms | 6.1 ms | 24.2 ms | 0 |
| Read/write (TPC-B like) | 8 | 1,157 | 6 ms | 11.4 ms | 22.8 ms | 60.8 ms | 0 |
| Read/write (TPC-B like) | 32 | 1,045 | 25.7 ms | 52.6 ms | 91.7 ms | 202 ms | 0 |
| Read only | 1 | 1,726 | 0.482 ms | 1.07 ms | 1.94 ms | 7.07 ms | 0 |
| Read only | 8 | 5,680 | 1.2 ms | 3.02 ms | 4.56 ms | 11.4 ms | 0 |
| Read only | 32 | 6,623 | 3.54 ms | 9.27 ms | 20.3 ms | 47.1 ms | 0 |
Scale 100 (10,000,000 accounts), loaded in 26.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 | 192 | 3,836 | 4.18 ms | 10.7 ms | 20.4 ms | 0 |
| Read/write | 8 | 282 | 5,638 | 26.2 ms | 46.6 ms | 66.8 ms | 0 |
| Read/write | 32 | 297 | 5,936 | 92.4 ms | 180 ms | 467 ms | 0 |
| Read only | 1 | 585 | 9,358 | 1.55 ms | 2.43 ms | 3.96 ms | 0 |
| Read only | 8 | 554 | 8,871 | 13.2 ms | 19.6 ms | 43.4 ms | 0 |
| Read only | 32 | 530 | 8,483 | 54.8 ms | 80 ms | 219 ms | 0 |
10 tables of 100,000 rows, loaded in 26.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 | 19,998 | 18,180 | 2.98 ms | 7.81 ms | 21.9 ms |
| 1:1 set:get | 20,271 | 10,135 | 2.77 ms | 9.09 ms | 35.1 ms |
1,000,000 keys of 32 bytes. 64 connections over 1 thread, 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 | 215 | 808 | 1,164 | 3.63 s |
| Express express-postgresjs | 2,799 | 4,337 | 8,014 | 2.92 s |
| Fastify fastify-postgres | 2,811 | 4,313 | 9,014 | 3.19 s |
| NestJS nestjs | 1,686 | 1,692 | 4,998 | 285 ms |
| Nuxt nuxt | 2,762 | 4,001 | 8,577 | 3.78 s |
| FastAPI fastapi | 1,241 | 1,559 | 5,709 | 981 ms |
| Django django-postgresql | 634 | 722 | 1,592 | 539 ms |
| Rails rails | 1,076 | 1,416 | 4,330 | 274 ms |
| Laravel laravel | 292 | 314 | 533 | 1 s |
| Symfony symfony | 360 | 378 | 988 | 797 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 | 0.772 | 1.84 s | 1.99 s | 2.14 s | 0% |
| Shop page | 0.772 | 2.44 s | 4.77 s | 5.71 s | 0% |
| Category page | 0.772 | 1.96 s | 4.17 s | 5.05 s | 0% |
| Product page | 0.772 | 1.81 s | 2.49 s | 2.8 s | 0% |
| Product search | 0.772 | 1.6 s | 1.77 s | 1.79 s | 0% |
| 32 virtual users | |||||
| Home page | 0.904 | 6.93 s | 8.19 s | 8.42 s | 0% |
| Shop page | 0.904 | 9.43 s | 10.9 s | 11.1 s | 0% |
| Category page | 0.848 | 8.95 s | 10.5 s | 10.6 s | 0% |
| Product page | 0.452 | 8.07 s | 11.6 s | 11.7 s | 0% |
| Product search | 0.452 | 10.7 s | 11.5 s | 11.7 s | 0% |
Cart and checkout
| Step | Requests/s | Median | p95 | p99 | Error rate |
|---|---|---|---|---|---|
| 8 virtual users | |||||
| Add to cart | 1.38 | 1.86 s | 4.82 s | 7.78 s | 0% |
| Cart | 1.38 | 1.7 s | 2.22 s | 5.34 s | 0% |
| Checkout | 1.38 | 1.31 s | 1.56 s | 1.77 s | 0% |
| 32 virtual users | |||||
| Add to cart | 1.61 | 6.66 s | 9.72 s | 10.9 s | 0% |
| Cart | 1.52 | 7.19 s | 8.9 s | 10 s | 0% |
| Checkout | 1.35 | 5.73 s | 6.39 s | 6.45 s | 0% |
k6 with a fixed number of virtual users, 63 to 71 s per level. The error rate counts responses that weren't a 200.
Advertised vs. measured
| Spec | Advertised | Measured |
|---|---|---|
| vCPU | 1 | 1 |
| CPU | Shared vCPU | 3.9% of busy CPU time stolen |
| RAM | 2 GB | 1.9 GiB |
| Storage | 50 GB SSD | 48.6 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
- 1
- CPU frequency
- 2000 MHz
- AES-NI
- Yes
- VM-x/AMD-V
- No
- RAM reported
- 1.9 GiB
- Swap reported
- 496 MiB
- Disk reported
- 48.6 GiB
- Virtualization reported
- KVM
- CPU steal
- 3.9% 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 2GB
- Product line
- Shared CPU
- Location
- Newark, NJ
- vCPU
- 1 shared vCPU
- Architecture
- x86_64
- RAM
- 2 GB
- Storage
- 50 GB SSD
- Virtualization
- KVM
- Network
- 2 Gbps
- Transfer
- 2 TB
- Port 25
- On request
- Monthly price at test time
- $12.00
- Hourly price at test time
- $0.018
- YABS version
- v2026-09-20
- Ran at
- Oct 11, 2026, 06:50:49 UTC
- Parser version
- 5
Run timeline
- Queued
- Oct 11, 2026, 06:46:00 UTC
- First update from the server
- Oct 11, 2026, 06:48:03 UTC
- Completed
- Oct 11, 2026, 08:07:37 UTC
- Server deleted
- Oct 11, 2026, 08:07:37 UTC
- Cost of this run
- $0.024
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.