Linode Nanode (1 GB) vs. Vultr Cloud Compute (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
Linode – Nanode (1 GB)
Vultr – Cloud Compute (1 GB)
Last Benchmarked
Mon, 06 Apr 2026 20:00:52 GMT
Wed, 08 Apr 2026 21:00:52 GMT
Linux Distro
Ubuntu 24.04 LTS x64
Ubuntu 24.04 LTS x64
Kernel Version
6.8.0-71-generic
6.8.0-107-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
Linode – Nanode (1 GB)
Vultr – Cloud Compute (1 GB)
Vendor
AuthenticAMD
GenuineIntel
Model Name
AMD EPYC 7713 64-Core Processor
Intel Core Processor (Haswell, no TSX, IBRS)
Clock Speed (MHz)
2,000.00
2,400.00
CPU Cache Size (KB)
512.00
16,384.00
BogoMips
3,999.99
4,799.99
Events per Second
1,620.95
820.77
Minimum Latency (ms)
0.28
1
Average Latency (ms)
0.61
1.22
Maximum Latency (ms)
16.58
3.71
95th Percentile Latency (ms)
2.97
1.32
Memory
Memory Read
Linode – Nanode (1 GB)
Vultr – Cloud Compute (1 GB)
Operations per second
2,785,205.91
4,183,460.82
Mebibytes per second
2,719.93
4,085.41
Minimum Latency (ms)
0
0
Average Latency (ms)
0
0
Maximum Latency (ms)
3.98
0.32
95th Percentile Latency (ms)
0
0
Memory Write
Linode – Nanode (1 GB)
Vultr – Cloud Compute (1 GB)
Operations per second
5,247,741.79
4,091,149.16
Mebibytes per second
5,124.75
3,995.26
Minimum Latency (ms)
0
0
Average Latency (ms)
0
0
Maximum Latency (ms)
4.41
0.91
95th Percentile Latency (ms)
0
0
File I/O
Linode – Nanode (1 GB)
Vultr – Cloud Compute (1 GB)
Reads per Second
2,319.13
2,036.96
Writes per Second
1,546.08
1,357.97
Fsyncs per Second
4,957.36
4,346.01
Read Mebibytes per Second
36.24
31.83
Written Mebibytes per Second
24.16
21.22
Minimum Latency (ms)
0
0
Average Latency (ms)
0.11
0.13
Maximum Latency (ms)
8.17
4.89
95th Percentile Latency (ms)
0.25
0.3
Mutex
Linode – Nanode (1 GB)
Vultr – Cloud Compute (1 GB)
Minimum Latency (ms)
2,349.38
1,927.10
Average Latency (ms)
2,390.79
1,939.45
Maximum Latency (ms)
2,412.13
1,950.93
95th Percentile Latency (ms)
2,405.65
1,938.16
MySQL
MySQL Read-only
Linode – Nanode (1 GB)
Vultr – Cloud Compute (1 GB)
Transactions per second
6,608.00
5,023.00
Queries per second
66,080.00
50,230.00
Minimum Latency (ms)
1.28
1.72
Average Latency (ms)
1.51
1.99
Maximum Latency (ms)
8.96
6.42
95th Percentile Latency (ms)
1.79
2.18
MySQL Write-only
Linode – Nanode (1 GB)
Vultr – Cloud Compute (1 GB)
Transactions per second
4,539.00
3,626.00
Queries per second
45,390.00
36,260.00
Minimum Latency (ms)
1.33
1.75
Average Latency (ms)
2.2
2.76
Maximum Latency (ms)
18.39
26.81
95th Percentile Latency (ms)
3.25
4.41
MySQL Read/Write
Linode – Nanode (1 GB)
Vultr – Cloud Compute (1 GB)
Transactions per second
2,306.00
1,959.00
Queries per second
23,060.00
19,590.00
Minimum Latency (ms)
3.11
4.12
Average Latency (ms)
4.33
5.1
Maximum Latency (ms)
10.82
10.97
95th Percentile Latency (ms)
5.67
6.21
MySQL INSERT
Linode – Nanode (1 GB)
Vultr – Cloud Compute (1 GB)
Transactions per second
7,556.00
6,524.00
Queries per second
75,560.00
65,240.00
Minimum Latency (ms)
0.83
1.08
Average Latency (ms)
1.32
1.53
Maximum Latency (ms)
8.91
15.83
95th Percentile Latency (ms)
1.82
2.03
MySQL Bulk INSERT
Linode – Nanode (1 GB)
Vultr – Cloud Compute (1 GB)
Transactions per second
1,171,967.00
996,869.00
Queries per second
11,719,670.00
9,968,690.00
Minimum Latency (ms)
0
0
Average Latency (ms)
0.01
0.01
Maximum Latency (ms)
511.73
477.16
95th Percentile Latency (ms)
0
0
MySQL SELECT
Linode – Nanode (1 GB)
Vultr – Cloud Compute (1 GB)
Transactions per second
127,249.00
104,020.00
Queries per second
1,272,490.00
1,040,200.00
Minimum Latency (ms)
0.05
0.07
Average Latency (ms)
0.08
0.1
Maximum Latency (ms)
7.66
2.02
95th Percentile Latency (ms)
0.11
0.14
MySQL SELECT (Random Points)
Linode – Nanode (1 GB)
Vultr – Cloud Compute (1 GB)
Transactions per second
8,151.00
5,526.00
Queries per second
81,510.00
55,260.00
Minimum Latency (ms)
0.39
0.63
Average Latency (ms)
1.22
1.81
Maximum Latency (ms)
5.53
6.77
95th Percentile Latency (ms)
1.7
2.35
MySQL SELECT (Random Ranges)
Linode – Nanode (1 GB)
Vultr – Cloud Compute (1 GB)
Transactions per second
9,239.00
6,273.00
Queries per second
92,390.00
62,730.00
Minimum Latency (ms)
0.33
0.5
Average Latency (ms)
1.08
1.59
Maximum Latency (ms)
8.4
3.53
95th Percentile Latency (ms)
1.42
2.07
MySQL UPDATE (Indexed)
Linode – Nanode (1 GB)
Vultr – Cloud Compute (1 GB)
Transactions per second
7,280.00
6,371.00
Queries per second
72,800.00
63,710.00
Minimum Latency (ms)
0.71
1.03
Average Latency (ms)
1.37
1.57
Maximum Latency (ms)
23.45
7.68
95th Percentile Latency (ms)
2.03
2.14
MySQL UPDATE (Non-Indexed)
Linode – Nanode (1 GB)
Vultr – Cloud Compute (1 GB)
Transactions per second
7,428.00
6,541.00
Queries per second
74,280.00
65,410.00
Minimum Latency (ms)
0.72
0.91
Average Latency (ms)
1.34
1.53
Maximum Latency (ms)
6.56
24.84
95th Percentile Latency (ms)
1.86
1.96
MySQL DELETE
Linode – Nanode (1 GB)
Vultr – Cloud Compute (1 GB)
Transactions per second
54,792.00
43,573.00
Queries per second
547,920.00
435,730.00
Minimum Latency (ms)
0.05
0.07
Average Latency (ms)
0.18
0.23
Maximum Latency (ms)
11.29
7.55
95th Percentile Latency (ms)
1.14
1.42
Redis
Linode – Nanode (1 GB)
Vultr – Cloud Compute (1 GB)
PING_INLINE per Second
28,910.09
35,050.82
PING_MBULK per Second
34,328.87
33,534.54
SET per Second
33,178.50
36,010.08
GET per Second
33,670.04
35,149.38
INCR per Second
34,650.04
36,523.01
LPUSH per Second
32,992.41
37,369.21
RPUSH per Second
32,992.41
38,774.72
LPOP per Second
33,068.79
36,982.25
RPOP per Second
33,388.98
36,724.20
SADD per Second
33,014.20
36,563.07
HSET per Second
33,967.39
32,701.11
SPOP per Second
35,549.23
36,205.65
ZADD per Second
34,071.55
37,467.22
ZPOPMIN per Second
34,364.26
37,495.31
LRANGE_100 (first 100 elements) per Second
20,876.83
24,801.59
LRANGE_300 (first 300 elements) per Second
13,976.24
13,208.29
LRANGE_500 (first 500 elements) per Second
10,399.33
9,684.29
LRANGE_600 (first 600 elements) per Second
8,848.77
7,718.43
MSET (10 keys) per Second
31,240.24
33,602.15
Redis Average Latency (ms)
Linode – Nanode (1 GB)
Vultr – Cloud Compute (1 GB)
PING_INLINE
1.11
0.93
PING_MBULK
0.97
0.96
SET
0.99
0.91
GET
0.97
0.92
INCR
0.95
0.90
LPUSH
0.99
0.88
RPUSH
0.99
0.85
LPOP
1.00
0.89
RPOP
0.98
0.90
SADD
0.98
0.89
HSET
0.96
1.01
SPOP
0.93
0.89
ZADD
0.96
0.88
ZPOPMIN
0.94
0.87
LRANGE_100 (first 100 elements)
1.61
1.35
LRANGE_300 (first 300 elements)
2.39
2.57
LRANGE_500 (first 500 elements)
3.26
3.54
LRANGE_600 (first 600 elements)
3.83
4.41
MSET (10 keys)
1.08
1.02
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.