Vultr Cloud Compute (1 GB) vs. Linode Nanode (1 GB)
Same showdown, different day. Today I've spun up some brand new instance from Linode and Vultr and ran my world famous suite of benchmarking scripts. All instances were spun up with Ubuntu 24.04 LTS x64 and all resided in or around the New York / New Jersey area. Enough talk. Here's the data.
Overview
Vultr – Cloud Compute (1 GB)
Linode – Nanode (1 GB)
Last Benchmarked
Wed, 08 Apr 2026 21:00:52 GMT
Mon, 06 Apr 2026 20:00:52 GMT
Linux Distro
Ubuntu 24.04 LTS x64
Ubuntu 24.04 LTS x64
Kernel Version
6.8.0-107-generic
6.8.0-71-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
$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
Vultr – Cloud Compute (1 GB)
Linode – Nanode (1 GB)
Vendor
GenuineIntel
AuthenticAMD
Model Name
Intel Core Processor (Haswell, no TSX, IBRS)
AMD EPYC 7713 64-Core Processor
Clock Speed (MHz)
2,400.00
2,000.00
CPU Cache Size (KB)
16,384.00
512.00
BogoMips
4,799.99
3,999.99
Events per Second
820.77
1,620.95
Minimum Latency (ms)
1
0.28
Average Latency (ms)
1.22
0.61
Maximum Latency (ms)
3.71
16.58
95th Percentile Latency (ms)
1.32
2.97
Memory
Memory Read
Vultr – Cloud Compute (1 GB)
Linode – Nanode (1 GB)
Operations per second
4,183,460.82
2,785,205.91
Mebibytes per second
4,085.41
2,719.93
Minimum Latency (ms)
0
0
Average Latency (ms)
0
0
Maximum Latency (ms)
0.32
3.98
95th Percentile Latency (ms)
0
0
Memory Write
Vultr – Cloud Compute (1 GB)
Linode – Nanode (1 GB)
Operations per second
4,091,149.16
5,247,741.79
Mebibytes per second
3,995.26
5,124.75
Minimum Latency (ms)
0
0
Average Latency (ms)
0
0
Maximum Latency (ms)
0.91
4.41
95th Percentile Latency (ms)
0
0
File I/O
Vultr – Cloud Compute (1 GB)
Linode – Nanode (1 GB)
Reads per Second
2,036.96
2,319.13
Writes per Second
1,357.97
1,546.08
Fsyncs per Second
4,346.01
4,957.36
Read Mebibytes per Second
31.83
36.24
Written Mebibytes per Second
21.22
24.16
Minimum Latency (ms)
0
0
Average Latency (ms)
0.13
0.11
Maximum Latency (ms)
4.89
8.17
95th Percentile Latency (ms)
0.3
0.25
Mutex
Vultr – Cloud Compute (1 GB)
Linode – Nanode (1 GB)
Minimum Latency (ms)
1,927.10
2,349.38
Average Latency (ms)
1,939.45
2,390.79
Maximum Latency (ms)
1,950.93
2,412.13
95th Percentile Latency (ms)
1,938.16
2,405.65
MySQL
MySQL Read-only
Vultr – Cloud Compute (1 GB)
Linode – Nanode (1 GB)
Transactions per second
5,023.00
6,608.00
Queries per second
50,230.00
66,080.00
Minimum Latency (ms)
1.72
1.28
Average Latency (ms)
1.99
1.51
Maximum Latency (ms)
6.42
8.96
95th Percentile Latency (ms)
2.18
1.79
MySQL Write-only
Vultr – Cloud Compute (1 GB)
Linode – Nanode (1 GB)
Transactions per second
3,626.00
4,539.00
Queries per second
36,260.00
45,390.00
Minimum Latency (ms)
1.75
1.33
Average Latency (ms)
2.76
2.2
Maximum Latency (ms)
26.81
18.39
95th Percentile Latency (ms)
4.41
3.25
MySQL Read/Write
Vultr – Cloud Compute (1 GB)
Linode – Nanode (1 GB)
Transactions per second
1,959.00
2,306.00
Queries per second
19,590.00
23,060.00
Minimum Latency (ms)
4.12
3.11
Average Latency (ms)
5.1
4.33
Maximum Latency (ms)
10.97
10.82
95th Percentile Latency (ms)
6.21
5.67
MySQL INSERT
Vultr – Cloud Compute (1 GB)
Linode – Nanode (1 GB)
Transactions per second
6,524.00
7,556.00
Queries per second
65,240.00
75,560.00
Minimum Latency (ms)
1.08
0.83
Average Latency (ms)
1.53
1.32
Maximum Latency (ms)
15.83
8.91
95th Percentile Latency (ms)
2.03
1.82
MySQL Bulk INSERT
Vultr – Cloud Compute (1 GB)
Linode – Nanode (1 GB)
Transactions per second
996,869.00
1,171,967.00
Queries per second
9,968,690.00
11,719,670.00
Minimum Latency (ms)
0
0
Average Latency (ms)
0.01
0.01
Maximum Latency (ms)
477.16
511.73
95th Percentile Latency (ms)
0
0
MySQL SELECT
Vultr – Cloud Compute (1 GB)
Linode – Nanode (1 GB)
Transactions per second
104,020.00
127,249.00
Queries per second
1,040,200.00
1,272,490.00
Minimum Latency (ms)
0.07
0.05
Average Latency (ms)
0.1
0.08
Maximum Latency (ms)
2.02
7.66
95th Percentile Latency (ms)
0.14
0.11
MySQL SELECT (Random Points)
Vultr – Cloud Compute (1 GB)
Linode – Nanode (1 GB)
Transactions per second
5,526.00
8,151.00
Queries per second
55,260.00
81,510.00
Minimum Latency (ms)
0.63
0.39
Average Latency (ms)
1.81
1.22
Maximum Latency (ms)
6.77
5.53
95th Percentile Latency (ms)
2.35
1.7
MySQL SELECT (Random Ranges)
Vultr – Cloud Compute (1 GB)
Linode – Nanode (1 GB)
Transactions per second
6,273.00
9,239.00
Queries per second
62,730.00
92,390.00
Minimum Latency (ms)
0.5
0.33
Average Latency (ms)
1.59
1.08
Maximum Latency (ms)
3.53
8.4
95th Percentile Latency (ms)
2.07
1.42
MySQL UPDATE (Indexed)
Vultr – Cloud Compute (1 GB)
Linode – Nanode (1 GB)
Transactions per second
6,371.00
7,280.00
Queries per second
63,710.00
72,800.00
Minimum Latency (ms)
1.03
0.71
Average Latency (ms)
1.57
1.37
Maximum Latency (ms)
7.68
23.45
95th Percentile Latency (ms)
2.14
2.03
MySQL UPDATE (Non-Indexed)
Vultr – Cloud Compute (1 GB)
Linode – Nanode (1 GB)
Transactions per second
6,541.00
7,428.00
Queries per second
65,410.00
74,280.00
Minimum Latency (ms)
0.91
0.72
Average Latency (ms)
1.53
1.34
Maximum Latency (ms)
24.84
6.56
95th Percentile Latency (ms)
1.96
1.86
MySQL DELETE
Vultr – Cloud Compute (1 GB)
Linode – Nanode (1 GB)
Transactions per second
43,573.00
54,792.00
Queries per second
435,730.00
547,920.00
Minimum Latency (ms)
0.07
0.05
Average Latency (ms)
0.23
0.18
Maximum Latency (ms)
7.55
11.29
95th Percentile Latency (ms)
1.42
1.14
Redis
Vultr – Cloud Compute (1 GB)
Linode – Nanode (1 GB)
PING_INLINE per Second
35,050.82
28,910.09
PING_MBULK per Second
33,534.54
34,328.87
SET per Second
36,010.08
33,178.50
GET per Second
35,149.38
33,670.04
INCR per Second
36,523.01
34,650.04
LPUSH per Second
37,369.21
32,992.41
RPUSH per Second
38,774.72
32,992.41
LPOP per Second
36,982.25
33,068.79
RPOP per Second
36,724.20
33,388.98
SADD per Second
36,563.07
33,014.20
HSET per Second
32,701.11
33,967.39
SPOP per Second
36,205.65
35,549.23
ZADD per Second
37,467.22
34,071.55
ZPOPMIN per Second
37,495.31
34,364.26
LRANGE_100 (first 100 elements) per Second
24,801.59
20,876.83
LRANGE_300 (first 300 elements) per Second
13,208.29
13,976.24
LRANGE_500 (first 500 elements) per Second
9,684.29
10,399.33
LRANGE_600 (first 600 elements) per Second
7,718.43
8,848.77
MSET (10 keys) per Second
33,602.15
31,240.24
Redis Average Latency (ms)
Vultr – Cloud Compute (1 GB)
Linode – Nanode (1 GB)
PING_INLINE
0.93
1.11
PING_MBULK
0.96
0.97
SET
0.91
0.99
GET
0.92
0.97
INCR
0.90
0.95
LPUSH
0.88
0.99
RPUSH
0.85
0.99
LPOP
0.89
1.00
RPOP
0.90
0.98
SADD
0.89
0.98
HSET
1.01
0.96
SPOP
0.89
0.93
ZADD
0.88
0.96
ZPOPMIN
0.87
0.94
LRANGE_100 (first 100 elements)
1.35
1.61
LRANGE_300 (first 300 elements)
2.57
2.39
LRANGE_500 (first 500 elements)
3.54
3.26
LRANGE_600 (first 600 elements)
4.41
3.83
MSET (10 keys)
1.02
1.08
Conclusion
From the friendly robots:
The Linode Nanode instance and the Vultr Cloud Compute instance both offer 1 CPU core and 1 GB of RAM, but their benchmark results vary significantly across different metrics. The Vultr instance generally outperforms the Linode instance in terms of Redis operations, achieving higher requests per second with lower average latencies across most commands. The Vultr instance also demonstrates superior file I/O performance with higher throughput and lower latencies. However, the Linode instance has more competitive results in MySQL OLTP operations and slightly better memory read/write latencies and operations. Given these benchmarks, the Vultr instance is better suited for workloads that benefit from high I/O performance and Redis operations, while the Linode instance might be more appropriate for workloads where MySQL performance and lower memory latencies are priorities.
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.