New day, new benchmarks. Today I've spun up brand new instance from Linode and Vultr and did some benchmarking. Each instance was running Ubuntu 24.04 LTS x64 and were created in the New York area (or close to it). Enough talk. Here's the data.
Overview
Linode – (2 GB)
Vultr – Cloud Compute (2 GB, 2 Cores)
Last Benchmarked
Sun, 10 May 2026 21:00:56 GMT
Mon, 11 May 2026 04: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-111-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
$12.00
$15.00
RAM (GB)
2
2
CPU Cores
1
2
Storage (TB)
50
65
Storage Type
SSD
SSD
Transfer (TB)
2
3
CPU
Linode – (2 GB)
Vultr – Cloud Compute (2 GB, 2 Cores)
Vendor
AuthenticAMD
GenuineIntel
Model Name
AMD EPYC 7642 48-Core Processor
Intel Core Processor (Skylake, IBRS, no TSX)
Clock Speed (MHz)
2,300.00
3,792.00
CPU Cache Size (KB)
512.00
16,384.00
BogoMips
4,600.00
7,583.99
Events per Second
765.10
1,481.60
Minimum Latency (ms)
0.61
0.63
Average Latency (ms)
1.3
0.67
Maximum Latency (ms)
35.81
1.95
95th Percentile Latency (ms)
2.35
0.77
Memory
Memory Read
Linode – (2 GB)
Vultr – Cloud Compute (2 GB, 2 Cores)
Operations per second
2,970,961.88
6,401,389.08
Mebibytes per second
2,901.33
6,251.36
Minimum Latency (ms)
0
0
Average Latency (ms)
0
0
Maximum Latency (ms)
9.03
0.23
95th Percentile Latency (ms)
0
0
Memory Write
Linode – (2 GB)
Vultr – Cloud Compute (2 GB, 2 Cores)
Operations per second
5,197,117.30
6,411,085.35
Mebibytes per second
5,075.31
6,260.83
Minimum Latency (ms)
0
0
Average Latency (ms)
0
0
Maximum Latency (ms)
2.74
0.18
95th Percentile Latency (ms)
0
0
File I/O
Linode – (2 GB)
Vultr – Cloud Compute (2 GB, 2 Cores)
Reads per Second
2,661.20
4,345.71
Writes per Second
1,774.13
2,897.07
Fsyncs per Second
5,678.72
9,273.19
Read Mebibytes per Second
41.58
67.90
Written Mebibytes per Second
27.72
45.27
Minimum Latency (ms)
0
0
Average Latency (ms)
0.1
0.06
Maximum Latency (ms)
63.92
2.92
95th Percentile Latency (ms)
0.33
0.17
Mutex
Linode – (2 GB)
Vultr – Cloud Compute (2 GB, 2 Cores)
Minimum Latency (ms)
1,634.87
214.63
Average Latency (ms)
1,644.40
569.72
Maximum Latency (ms)
1,652.34
636.55
95th Percentile Latency (ms)
1,648.20
634.66
MySQL
MySQL Read-only
Linode – (2 GB)
Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second
6,265.00
8,015.00
Queries per second
62,650.00
80,150.00
Minimum Latency (ms)
1.38
0.92
Average Latency (ms)
1.59
1.25
Maximum Latency (ms)
6.6
5.5
95th Percentile Latency (ms)
2.39
1.86
MySQL Write-only
Linode – (2 GB)
Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second
5,494.00
8,497.00
Queries per second
54,940.00
84,970.00
Minimum Latency (ms)
1.1
0.76
Average Latency (ms)
1.82
1.17
Maximum Latency (ms)
15.54
3.04
95th Percentile Latency (ms)
2.52
1.55
MySQL Read/Write
Linode – (2 GB)
Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second
2,670.00
3,726.00
Queries per second
26,700.00
37,260.00
Minimum Latency (ms)
2.94
1.78
Average Latency (ms)
3.74
2.68
Maximum Latency (ms)
14.72
5.82
95th Percentile Latency (ms)
4.82
3.43
MySQL INSERT
Linode – (2 GB)
Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second
9,139.00
15,028.00
Queries per second
91,390.00
150,280.00
Minimum Latency (ms)
0.67
0.41
Average Latency (ms)
1.09
0.66
Maximum Latency (ms)
8.4
2.42
95th Percentile Latency (ms)
1.42
0.86
MySQL Bulk INSERT
Linode – (2 GB)
Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second
1,142,842.00
1,696,217.00
Queries per second
11,428,420.00
16,962,170.00
Minimum Latency (ms)
0
0
Average Latency (ms)
0.01
0.01
Maximum Latency (ms)
447.65
283.37
95th Percentile Latency (ms)
0
0
MySQL SELECT
Linode – (2 GB)
Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second
148,728.00
201,989.00
Queries per second
1,487,280.00
2,019,890.00
Minimum Latency (ms)
0.05
0.03
Average Latency (ms)
0.07
0.05
Maximum Latency (ms)
4.91
0.51
95th Percentile Latency (ms)
0.09
0.07
MySQL SELECT (Random Points)
Linode – (2 GB)
Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second
7,446.00
8,025.00
Queries per second
74,460.00
80,250.00
Minimum Latency (ms)
0.45
0.35
Average Latency (ms)
1.34
1.24
Maximum Latency (ms)
6.58
3.55
95th Percentile Latency (ms)
1.73
2.07
MySQL SELECT (Random Ranges)
Linode – (2 GB)
Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second
7,227.00
8,336.00
Queries per second
72,270.00
83,360.00
Minimum Latency (ms)
0.49
0.4
Average Latency (ms)
1.38
1.2
Maximum Latency (ms)
6.65
4.25
95th Percentile Latency (ms)
1.79
2.22
MySQL UPDATE (Indexed)
Linode – (2 GB)
Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second
7,935.00
13,858.00
Queries per second
79,350.00
138,580.00
Minimum Latency (ms)
0.74
0.42
Average Latency (ms)
1.26
0.72
Maximum Latency (ms)
22.04
6.33
95th Percentile Latency (ms)
1.82
0.95
MySQL UPDATE (Non-Indexed)
Linode – (2 GB)
Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second
8,591.00
14,587.00
Queries per second
85,910.00
145,870.00
Minimum Latency (ms)
0.69
0.4
Average Latency (ms)
1.16
0.68
Maximum Latency (ms)
7.91
11.69
95th Percentile Latency (ms)
1.58
0.9
MySQL DELETE
Linode – (2 GB)
Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second
65,409.00
129,013.00
Queries per second
654,090.00
1,290,130.00
Minimum Latency (ms)
0.05
0.03
Average Latency (ms)
0.15
0.08
Maximum Latency (ms)
12.01
2.61
95th Percentile Latency (ms)
0.94
0.09
Redis
Linode – (2 GB)
Vultr – Cloud Compute (2 GB, 2 Cores)
PING_INLINE per Second
40,518.64
78,247.26
PING_MBULK per Second
40,799.68
74,738.41
SET per Second
39,292.73
77,041.60
GET per Second
41,050.90
83,333.33
INCR per Second
40,816.32
80,971.66
LPUSH per Second
40,733.20
79,113.92
RPUSH per Second
41,237.11
77,160.49
LPOP per Second
38,565.37
81,499.59
RPOP per Second
40,338.84
82,440.23
SADD per Second
33,344.45
80,192.46
HSET per Second
39,447.73
83,612.04
SPOP per Second
41,254.12
85,034.02
ZADD per Second
39,308.18
83,263.95
ZPOPMIN per Second
40,420.37
82,987.55
LRANGE_100 (first 100 elements) per Second
27,063.60
55,555.56
LRANGE_300 (first 300 elements) per Second
15,021.78
28,851.70
LRANGE_500 (first 500 elements) per Second
10,577.53
19,391.12
LRANGE_600 (first 600 elements) per Second
9,311.85
17,211.71
MSET (10 keys) per Second
38,461.54
80,256.82
Redis Average Latency (ms)
Linode – (2 GB)
Vultr – Cloud Compute (2 GB, 2 Cores)
PING_INLINE
0.84
0.34
PING_MBULK
0.83
0.35
SET
0.87
0.34
GET
0.83
0.32
INCR
0.84
0.32
LPUSH
0.84
0.34
RPUSH
0.83
0.34
LPOP
0.91
0.32
RPOP
0.85
0.32
SADD
0.99
0.32
HSET
0.86
0.31
SPOP
0.82
0.30
ZADD
0.86
0.31
ZPOPMIN
0.84
0.31
LRANGE_100 (first 100 elements)
1.28
0.54
LRANGE_300 (first 300 elements)
2.39
1.11
LRANGE_500 (first 500 elements)
3.42
1.62
LRANGE_600 (first 600 elements)
3.86
1.84
MSET (10 keys)
0.91
0.38
Conclusion
From the friendly robots:
Comparing the Linode and Vultr instances, both perform similarly in CPU-intensive tasks, though Vultr has a slight edge in raw processing rate and fairness. Linode excels in memory operations and shows better latency across a range of Redis commands, particularly for LRANGE operations. File I/O operations indicate both providers perform well but slightly favor Linode in read throughput. In terms of ideal use cases, Linode is better suited for memory-intensive applications and database operations with a focus on lower latency and better handling of complex queries, while Vultr shines in environments that benefit from higher CPU counts and processing throughput at a marginally lower cost.
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.