Linode Linode (8 GB) vs. Vultr High Performance AMD (2 GB, 2 Cores)

vs.

Welcome to another round of the VPS Showdown. Today I've spun up brand new instance from Linode and Vultr and did some benchmarking. Each instance was spun up with Ubuntu 24.04 LTS x64 and were created in the New York area (or close to it). Time to see who showed up today.

Overview

Linode – (8 GB) Vultr – High Performance AMD (2 GB, 2 Cores)
Last Benchmarked Thu, 28 May 2026 22:00:52 GMT Sun, 31 May 2026 07:00:52 GMT
Linux Distro Ubuntu 24.04 LTS x64 Ubuntu 24.04 LTS x64
Kernel Version 6.8.0-111-generic 6.8.0-117-generic
MySQL Version 8.0.45-0ubuntu0.24.04.1 8.0.45-0ubuntu0.24.04.1
Redis Version 7.0.15 7.0.15
Location Newark, NJ Newark, NJ
Monthly Price $48.00 $18.00
RAM (GB) 8 2
CPU Cores 4 2
Storage (TB) 160 60
Storage Type SSD NVMe
Transfer (TB) 5 4

CPU

Linode – (8 GB) Vultr – High Performance AMD (2 GB, 2 Cores)
Vendor AuthenticAMD AuthenticAMD
Model Name AMD EPYC 7542 32-Core Processor AMD EPYC-Genoa Processor
Clock Speed (MHz) 2,900.00 2,899.99
CPU Cache Size (KB) 512.00 1,024.00
BogoMips 5,799.99 5,799.98
Events per Second 1,662.84 4,648.14
Minimum Latency (ms) 0.58 0.2
Average Latency (ms) 0.6 0.21
Maximum Latency (ms) 0.98 1.26
95th Percentile Latency (ms) 0.62 0.23

Memory

Memory Read

Linode – (8 GB) Vultr – High Performance AMD (2 GB, 2 Cores)
Operations per second 5,572,840.65 7,548,502.85
Mebibytes per second 5,442.23 7,371.58
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 2.95 0.08
95th Percentile Latency (ms) 0 0

Memory Write

Linode – (8 GB) Vultr – High Performance AMD (2 GB, 2 Cores)
Operations per second 5,535,027.02 7,544,807.09
Mebibytes per second 5,405.30 7,367.98
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 2.85 0.12
95th Percentile Latency (ms) 0 0

File I/O

Linode – (8 GB) Vultr – High Performance AMD (2 GB, 2 Cores)
Reads per Second 5,424.55 5,114.79
Writes per Second 3,616.37 3,409.86
Fsyncs per Second 11,573.28 10,914.44
Read Mebibytes per Second 84.76 79.92
Written Mebibytes per Second 56.51 53.28
Minimum Latency (ms) 0 0
Average Latency (ms) 0.05 0.05
Maximum Latency (ms) 14.28 3.7
95th Percentile Latency (ms) 0.17 0.12

Mutex

Linode – (8 GB) Vultr – High Performance AMD (2 GB, 2 Cores)
Minimum Latency (ms) 346.89 574.03
Average Latency (ms) 384.62 637.47
Maximum Latency (ms) 426.97 663.74
95th Percentile Latency (ms) 427.07 657.93

MySQL

MySQL Read-only

Linode – (8 GB) Vultr – High Performance AMD (2 GB, 2 Cores)
Transactions per second 7,160.00 9,622.00
Queries per second 71,600.00 96,220.00
Minimum Latency (ms) 1.14 0.73
Average Latency (ms) 1.4 1.04
Maximum Latency (ms) 6.16 2.22
95th Percentile Latency (ms) 1.52 1.12

MySQL Write-only

Linode – (8 GB) Vultr – High Performance AMD (2 GB, 2 Cores)
Transactions per second 7,032.00 9,585.00
Queries per second 70,320.00 95,850.00
Minimum Latency (ms) 1.02 0.8
Average Latency (ms) 1.42 1.04
Maximum Latency (ms) 6.43 2.18
95th Percentile Latency (ms) 1.73 1.32

MySQL Read/Write

Linode – (8 GB) Vultr – High Performance AMD (2 GB, 2 Cores)
Transactions per second 3,426.00 4,686.00
Queries per second 34,260.00 46,860.00
Minimum Latency (ms) 2.23 1.57
Average Latency (ms) 2.92 2.13
Maximum Latency (ms) 21.84 4.26
95th Percentile Latency (ms) 3.3 2.52

MySQL INSERT

Linode – (8 GB) Vultr – High Performance AMD (2 GB, 2 Cores)
Transactions per second 10,087.00 15,965.00
Queries per second 100,870.00 159,650.00
Minimum Latency (ms) 0.62 0.45
Average Latency (ms) 0.99 0.62
Maximum Latency (ms) 7.62 2.23
95th Percentile Latency (ms) 1.16 0.74

MySQL Bulk INSERT

Linode – (8 GB) Vultr – High Performance AMD (2 GB, 2 Cores)
Transactions per second 1,783,592.00 3,065,092.00
Queries per second 17,835,920.00 30,650,920.00
Minimum Latency (ms) 0 0
Average Latency (ms) 0.01 0
Maximum Latency (ms) 286.34 208.51
95th Percentile Latency (ms) 0 0

MySQL SELECT

Linode – (8 GB) Vultr – High Performance AMD (2 GB, 2 Cores)
Transactions per second 159,757.00 217,035.00
Queries per second 1,597,570.00 2,170,350.00
Minimum Latency (ms) 0.04 0.02
Average Latency (ms) 0.06 0.05
Maximum Latency (ms) 3.06 0.61
95th Percentile Latency (ms) 0.08 0.06

MySQL SELECT (Random Points)

Linode – (8 GB) Vultr – High Performance AMD (2 GB, 2 Cores)
Transactions per second 9,238.00 14,818.00
Queries per second 92,380.00 148,180.00
Minimum Latency (ms) 0.37 0.24
Average Latency (ms) 1.08 0.67
Maximum Latency (ms) 5.01 1.94
95th Percentile Latency (ms) 1.37 0.86

MySQL SELECT (Random Ranges)

Linode – (8 GB) Vultr – High Performance AMD (2 GB, 2 Cores)
Transactions per second 7,423.00 14,341.00
Queries per second 74,230.00 143,410.00
Minimum Latency (ms) 0.53 0.27
Average Latency (ms) 1.35 0.7
Maximum Latency (ms) 4.76 1.67
95th Percentile Latency (ms) 1.73 0.89

MySQL UPDATE (Indexed)

Linode – (8 GB) Vultr – High Performance AMD (2 GB, 2 Cores)
Transactions per second 9,202.00 14,864.00
Queries per second 92,020.00 148,640.00
Minimum Latency (ms) 0.65 0.47
Average Latency (ms) 1.09 0.67
Maximum Latency (ms) 19.01 2.36
95th Percentile Latency (ms) 1.44 0.87

MySQL UPDATE (Non-Indexed)

Linode – (8 GB) Vultr – High Performance AMD (2 GB, 2 Cores)
Transactions per second 9,940.00 15,284.00
Queries per second 99,400.00 152,840.00
Minimum Latency (ms) 0.64 0.46
Average Latency (ms) 1.01 0.65
Maximum Latency (ms) 5.77 1.65
95th Percentile Latency (ms) 1.18 0.83

MySQL DELETE

Linode – (8 GB) Vultr – High Performance AMD (2 GB, 2 Cores)
Transactions per second 93,447.00 151,536.00
Queries per second 934,470.00 1,515,360.00
Minimum Latency (ms) 0.04 0.02
Average Latency (ms) 0.11 0.07
Maximum Latency (ms) 4.55 4.83
95th Percentile Latency (ms) 0.12 0.08

Redis

Linode – (8 GB) Vultr – High Performance AMD (2 GB, 2 Cores)
PING_INLINE per Second 59,171.59 55,991.04
PING_MBULK per Second 52,465.90 57,903.88
SET per Second 59,952.04 57,703.40
GET per Second 61,199.51 57,703.40
INCR per Second 62,111.80 57,372.34
LPUSH per Second 60,422.96 57,836.90
RPUSH per Second 66,979.23 58,173.36
LPOP per Second 60,753.34 58,343.06
RPOP per Second 61,274.51 58,343.06
SADD per Second 61,425.06 58,241.12
HSET per Second 61,425.06 58,858.15
SPOP per Second 62,073.25 58,892.82
ZADD per Second 61,538.46 57,504.31
ZPOPMIN per Second 60,496.07 57,870.37
LRANGE_100 (first 100 elements) per Second 49,455.98 49,236.83
LRANGE_300 (first 300 elements) per Second 28,768.70 34,818.94
LRANGE_500 (first 500 elements) per Second 21,008.40 26,766.60
LRANGE_600 (first 600 elements) per Second 18,765.25 24,207.21
MSET (10 keys) per Second 61,996.28 58,548.01

Redis Average Latency (ms)

Linode – (8 GB) Vultr – High Performance AMD (2 GB, 2 Cores)
PING_INLINE0.440.48
PING_MBULK0.490.44
SET0.430.45
GET0.420.45
INCR0.420.45
LPUSH0.430.44
RPUSH0.390.44
LPOP0.430.44
RPOP0.420.44
SADD0.420.44
HSET0.430.44
SPOP0.420.44
ZADD0.420.45
ZPOPMIN0.430.44
LRANGE_100 (first 100 elements)0.520.53
LRANGE_300 (first 300 elements)0.910.74
LRANGE_500 (first 500 elements)1.220.95
LRANGE_600 (first 600 elements)1.371.05
MSET (10 keys)0.420.44

Conclusion

From the friendly robots:

After analyzing the benchmark results for both Linode and Vultr instances, it's clear that the Linode (8 GB) outperforms the Vultr High Performance AMD (2 GB, 2 Cores) in most metrics. The Linode instance shows superior performance in CPU-intensive tasks, memory operations, and I/O throughput, with higher requests per second for Redis operations and lower latencies. While Vultr’s instance has a better thread fairness and lower average latencies for some tasks, Linode’s higher RAM, CPU cores, and storage capacity make it more suitable for demanding applications requiring high throughput and low latency, such as large-scale web applications, data analytics, and high-performance computing workloads. Vultr’s instance, though less powerful, may be more appropriate for smaller, less resource-intensive applications where cost and simplicity are prioritized.

From the friendly human:

If you found this VPS Showdown helpful in your search for a hosting provider, please consider supporting my efforts by signing up using my referral links for Linode and Vultr.

You can also support me directly by buying me a coffee.