Linode Nanode (1 GB) vs. Vultr Cloud Compute (1 GB)
Fresh benchmarks coming at ya. Today I've spun up some brand new instance from Linode and Vultr to run some benchmarks on. All instances were 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 – Nanode (1 GB)
Vultr – Cloud Compute (1 GB)
Last Benchmarked
Wed, 29 Oct 2025 11:00:52 GMT
Tue, 28 Oct 2025 11:00:51 GMT
Linux Distro
Ubuntu 24.04 LTS x64
Ubuntu 24.04 LTS x64
Kernel Version
6.8.0-71-generic
6.8.0-79-generic
MySQL Version
8.0.43-0ubuntu0.24.04.2
8.0.43-0ubuntu0.24.04.2
Redis Version
7.0.15
7.0.15
Location
Newark, NJ
Newark, NJ
Monthly Price
$5.00
$5.00
RAM (GB)
1
1
CPU Cores
1
1
Storage (TB)
25
25
Storage Type
SSD
SSD
Transfer (TB)
1
1
CPU
Linode – Nanode (1 GB)
Vultr – Cloud Compute (1 GB)
Vendor
AuthenticAMD
GenuineIntel
Model Name
AMD EPYC 7601 32-Core Processor
Intel Core Processor (Broadwell, no TSX, IBRS)
Clock Speed (MHz)
2,200.00
2,394.45
CPU Cache Size (KB)
512.00
16,384.00
BogoMips
4,399.99
4,788.90
Events per Second
626.39
615.53
Minimum Latency (ms)
0.67
0.88
Average Latency (ms)
1.6
1.62
Maximum Latency (ms)
8.53
5.49
95th Percentile Latency (ms)
4.25
2.61
Memory
Memory Read
Linode – Nanode (1 GB)
Vultr – Cloud Compute (1 GB)
Operations per second
1,992,468.11
3,650,861.12
Mebibytes per second
1,945.77
3,565.29
Minimum Latency (ms)
0
0
Average Latency (ms)
0
0
Maximum Latency (ms)
4.79
0.86
95th Percentile Latency (ms)
0
0
Memory Write
Linode – Nanode (1 GB)
Vultr – Cloud Compute (1 GB)
Operations per second
2,048,078.98
3,964,071.36
Mebibytes per second
2,000.08
3,871.16
Minimum Latency (ms)
0
0
Average Latency (ms)
0
0
Maximum Latency (ms)
7.36
0.65
95th Percentile Latency (ms)
0
0
File I/O
Linode – Nanode (1 GB)
Vultr – Cloud Compute (1 GB)
Reads per Second
1,569.23
1,335.03
Writes per Second
1,046.16
890.02
Fsyncs per Second
3,352.99
2,849.25
Read Mebibytes per Second
24.52
20.86
Written Mebibytes per Second
16.35
13.91
Minimum Latency (ms)
0
0.01
Average Latency (ms)
0.17
0.2
Maximum Latency (ms)
6.62
12
95th Percentile Latency (ms)
0.4
0.51
Mutex
Linode – Nanode (1 GB)
Vultr – Cloud Compute (1 GB)
Minimum Latency (ms)
2,118.43
2,016.43
Average Latency (ms)
2,136.64
2,026.59
Maximum Latency (ms)
2,147.24
2,036.58
95th Percentile Latency (ms)
2,159.29
2,045.74
MySQL
MySQL Read-only
Linode – Nanode (1 GB)
Vultr – Cloud Compute (1 GB)
Transactions per second
4,513.00
4,681.00
Queries per second
45,130.00
46,810.00
Minimum Latency (ms)
1.69
1.57
Average Latency (ms)
2.21
2.13
Maximum Latency (ms)
14.39
22.59
95th Percentile Latency (ms)
2.48
3.75
MySQL Write-only
Linode – Nanode (1 GB)
Vultr – Cloud Compute (1 GB)
Transactions per second
3,583.00
2,680.00
Queries per second
35,830.00
26,800.00
Minimum Latency (ms)
1.87
1.66
Average Latency (ms)
2.79
3.73
Maximum Latency (ms)
27.89
34.94
95th Percentile Latency (ms)
4.03
6.67
MySQL Read/Write
Linode – Nanode (1 GB)
Vultr – Cloud Compute (1 GB)
Transactions per second
1,726.00
1,752.00
Queries per second
17,260.00
17,520.00
Minimum Latency (ms)
4.55
4.22
Average Latency (ms)
5.8
5.71
Maximum Latency (ms)
20.42
16.45
95th Percentile Latency (ms)
7.04
8.28
MySQL INSERT
Linode – Nanode (1 GB)
Vultr – Cloud Compute (1 GB)
Transactions per second
6,224.00
4,351.00
Queries per second
62,240.00
43,510.00
Minimum Latency (ms)
1.13
1.34
Average Latency (ms)
1.6
2.29
Maximum Latency (ms)
9.35
26.21
95th Percentile Latency (ms)
2.03
3.36
MySQL Bulk INSERT
Linode – Nanode (1 GB)
Vultr – Cloud Compute (1 GB)
Transactions per second
734,741.00
865,805.00
Queries per second
7,347,410.00
8,658,050.00
Minimum Latency (ms)
0
0
Average Latency (ms)
0.01
0.01
Maximum Latency (ms)
693.48
955.84
95th Percentile Latency (ms)
0
0
MySQL SELECT
Linode – Nanode (1 GB)
Vultr – Cloud Compute (1 GB)
Transactions per second
96,019.00
105,481.00
Queries per second
960,190.00
1,054,810.00
Minimum Latency (ms)
0.07
0.06
Average Latency (ms)
0.1
0.09
Maximum Latency (ms)
4.17
9.22
95th Percentile Latency (ms)
0.14
0.16
MySQL SELECT (Random Points)
Linode – Nanode (1 GB)
Vultr – Cloud Compute (1 GB)
Transactions per second
5,082.00
3,665.00
Queries per second
50,820.00
36,650.00
Minimum Latency (ms)
0.71
0.5
Average Latency (ms)
1.97
2.73
Maximum Latency (ms)
13.24
13.84
95th Percentile Latency (ms)
2.61
5
MySQL SELECT (Random Ranges)
Linode – Nanode (1 GB)
Vultr – Cloud Compute (1 GB)
Transactions per second
5,444.00
5,236.00
Queries per second
54,440.00
52,360.00
Minimum Latency (ms)
0.49
0.72
Average Latency (ms)
1.84
1.91
Maximum Latency (ms)
7.22
10.33
95th Percentile Latency (ms)
2.57
2.76
MySQL UPDATE (Indexed)
Linode – Nanode (1 GB)
Vultr – Cloud Compute (1 GB)
Transactions per second
5,363.00
4,511.00
Queries per second
53,630.00
45,110.00
Minimum Latency (ms)
1.08
1.26
Average Latency (ms)
1.86
2.21
Maximum Latency (ms)
7.65
14.93
95th Percentile Latency (ms)
2.86
3.55
MySQL UPDATE (Non-Indexed)
Linode – Nanode (1 GB)
Vultr – Cloud Compute (1 GB)
Transactions per second
6,025.00
5,148.00
Queries per second
60,250.00
51,480.00
Minimum Latency (ms)
1.23
1.25
Average Latency (ms)
1.66
1.94
Maximum Latency (ms)
7.39
19.95
95th Percentile Latency (ms)
2.22
2.81
MySQL DELETE
Linode – Nanode (1 GB)
Vultr – Cloud Compute (1 GB)
Transactions per second
32,847.00
19,636.00
Queries per second
328,470.00
196,360.00
Minimum Latency (ms)
0.07
0.08
Average Latency (ms)
0.3
0.51
Maximum Latency (ms)
13.38
33.94
95th Percentile Latency (ms)
1.64
2.48
Redis
Linode – Nanode (1 GB)
Vultr – Cloud Compute (1 GB)
PING_INLINE per Second
31,162.36
34,270.05
PING_MBULK per Second
32,414.91
34,638.03
SET per Second
32,488.63
35,211.27
GET per Second
31,979.53
34,977.27
INCR per Second
32,082.13
34,965.04
LPUSH per Second
31,847.13
36,443.15
RPUSH per Second
32,195.75
33,898.30
LPOP per Second
31,959.09
35,855.14
RPOP per Second
31,426.78
34,831.07
SADD per Second
32,030.75
35,829.45
HSET per Second
31,585.60
34,977.27
SPOP per Second
32,123.36
34,423.41
ZADD per Second
31,347.96
35,174.11
ZPOPMIN per Second
32,061.56
35,410.77
LRANGE_100 (first 100 elements) per Second
19,459.04
23,364.48
LRANGE_300 (first 300 elements) per Second
10,030.09
12,325.90
LRANGE_500 (first 500 elements) per Second
6,825.94
8,369.60
LRANGE_600 (first 600 elements) per Second
5,909.47
7,555.15
MSET (10 keys) per Second
29,931.16
33,123.55
Redis Average Latency (ms)
Linode – Nanode (1 GB)
Vultr – Cloud Compute (1 GB)
PING_INLINE
1.05
0.96
PING_MBULK
1.00
0.92
SET
1.02
0.93
GET
1.02
0.94
INCR
1.02
0.92
LPUSH
1.03
0.92
RPUSH
1.02
0.95
LPOP
1.04
0.93
RPOP
1.05
0.93
SADD
1.02
0.92
HSET
1.04
0.93
SPOP
1.01
0.94
ZADD
1.05
0.93
ZPOPMIN
1.01
0.92
LRANGE_100 (first 100 elements)
1.70
1.43
LRANGE_300 (first 300 elements)
3.22
2.77
LRANGE_500 (first 500 elements)
4.67
4.07
LRANGE_600 (first 600 elements)
5.25
4.48
MSET (10 keys)
1.16
1.03
Conclusion
From the friendly robots:
After analyzing the benchmark results for both Linode's Nanode (1 GB) and Vultr's Cloud Compute (1 GB), it's clear that Vultr's instance outperforms Linode's in most metrics, particularly in Redis operations where it achieves higher requests per second and lower latencies across various commands. Vultr's CPU also shows better performance with slightly higher BogoMIPS and a more substantial cache. However, Linode's instance excels in handling file I/O operations, with higher throughput and lower latency. For workloads that prioritize high Redis performance and CPU efficiency, Vultr's Cloud Compute (1 GB) is the better choice, while Linode's Nanode (1 GB) is more suitable for tasks that demand superior file I/O performance.
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.