Linode Nanode (1 GB) vs. Vultr High Frequency Intel (2 GB)
Welcome to another round of the VPS Showdown. Today I've got brand new instances from Linode and Vultr to run some benchmarks on. Each instance was running Ubuntu 26.04 LTS x64 and all resided in or around the New York / New Jersey area. Without further ado, here's the results.
Overview
Linode – Nanode (1 GB)
Vultr – High Frequency Intel (2 GB)
Last Benchmarked
Thu, 01 Oct 2026 05:01:32 GMT
Tue, 01 Sep 2026 05:09:02 GMT
Linux Distro
Ubuntu 26.04 LTS x64
Ubuntu 26.04 LTS x64
Kernel Version
7.0.0-34-generic
7.0.0-29-generic
MySQL Version
8.4.11-0ubuntu0.26.04.1
8.4.11-0ubuntu0.26.04.1
Redis Version
8.0.5
8.0.5
Location
Newark, NJ
Newark, NJ
Monthly Price
$5.00
$12.00
RAM (GB)
1
2
CPU Cores
1
1
Storage (TB)
25
64
Storage Type
SSD
NVMe
Transfer (TB)
1
2
Head-to-head
Category winners from the latest benchmarks.
Category
Winner
CPU (events/sec)
Linode – Nanode (1 GB)
Memory (read MiB/s)
Vultr – High Frequency Intel (2 GB)
Disk I/O (MiB/s)
Vultr – High Frequency Intel (2 GB)
MySQL (read/write tps)
Vultr – High Frequency Intel (2 GB)
Redis (GET/sec)
Vultr – High Frequency Intel (2 GB)
Value (CPU events per $/mo)
Linode – Nanode (1 GB)
Vultr – High Frequency Intel (2 GB) takes 4 of 6 categories.
CPU
Linode – Nanode (1 GB)
Vultr – High Frequency Intel (2 GB)
Vendor
AuthenticAMD
GenuineIntel
Model Name
AMD EPYC 7713 64-Core Processor
Intel Core Processor (Skylake, IBRS, no TSX)
Clock Speed (MHz)
2,000.00
3,792.05
CPU Cache Size (KB)
512.00
16,384.00
BogoMips
4,000.00
7,584.10
Events per Second
1,548.52
1,433.50
Minimum Latency (ms)
0.3
0.67
Average Latency (ms)
0.64
0.7
Maximum Latency (ms)
21.85
3.42
95th Percentile Latency (ms)
3.13
0.73
Memory
Memory Read
Linode – Nanode (1 GB)
Vultr – High Frequency Intel (2 GB)
Operations per second
4,152,415.63
6,381,196.95
Mebibytes per second
4,055.09
6,231.64
Minimum Latency (ms)
0
0
Average Latency (ms)
0
0
Maximum Latency (ms)
3.82
0.38
95th Percentile Latency (ms)
0
0
Memory Write
Linode – Nanode (1 GB)
Vultr – High Frequency Intel (2 GB)
Operations per second
5,085,089.33
7,590,256.83
Mebibytes per second
4,965.91
7,412.36
Minimum Latency (ms)
0
0
Average Latency (ms)
0
0
Maximum Latency (ms)
3.02
0.75
95th Percentile Latency (ms)
0
0
File I/O
Linode – Nanode (1 GB)
Vultr – High Frequency Intel (2 GB)
Reads per Second
2,243.85
4,797.61
Writes per Second
1,495.90
3,198.41
Fsyncs per Second
4,795.18
10,240.61
Read Mebibytes per Second
35.06
74.96
Written Mebibytes per Second
23.37
49.98
Minimum Latency (ms)
0
0
Average Latency (ms)
0.12
0.05
Maximum Latency (ms)
10.58
19.53
95th Percentile Latency (ms)
0.29
0.15
Mutex
Linode – Nanode (1 GB)
Vultr – High Frequency Intel (2 GB)
Minimum Latency (ms)
2,091.27
1,120.95
Average Latency (ms)
2,118.60
1,127.36
Maximum Latency (ms)
2,135.24
1,132.28
95th Percentile Latency (ms)
2,120.76
1,129.24
MySQL
MySQL Read-only
Linode – Nanode (1 GB)
Vultr – High Frequency Intel (2 GB)
Transactions per second
5,863.00
10,238.00
Queries per second
58,630.00
102,380.00
Minimum Latency (ms)
1.27
0.9
Average Latency (ms)
1.7
0.98
Maximum Latency (ms)
8.4
2.33
95th Percentile Latency (ms)
2.14
1.06
MySQL Write-only
Linode – Nanode (1 GB)
Vultr – High Frequency Intel (2 GB)
Transactions per second
5,483.00
12,564.00
Queries per second
54,830.00
125,640.00
Minimum Latency (ms)
1.12
0.65
Average Latency (ms)
1.82
0.79
Maximum Latency (ms)
17.77
8.86
95th Percentile Latency (ms)
2.3
0.97
MySQL Read/Write
Linode – Nanode (1 GB)
Vultr – High Frequency Intel (2 GB)
Transactions per second
2,888.00
5,279.00
Queries per second
28,880.00
52,790.00
Minimum Latency (ms)
2.56
1.64
Average Latency (ms)
3.46
1.89
Maximum Latency (ms)
14.47
4.39
95th Percentile Latency (ms)
4.25
2.22
MySQL INSERT
Linode – Nanode (1 GB)
Vultr – High Frequency Intel (2 GB)
Transactions per second
9,681.00
22,126.00
Queries per second
96,810.00
221,260.00
Minimum Latency (ms)
0.67
0.37
Average Latency (ms)
1.03
0.45
Maximum Latency (ms)
10.33
2.84
95th Percentile Latency (ms)
1.39
0.53
MySQL Bulk INSERT
Linode – Nanode (1 GB)
Vultr – High Frequency Intel (2 GB)
Transactions per second
1,142,842.00
1,958,342.00
Queries per second
11,428,420.00
19,583,420.00
Minimum Latency (ms)
0
0
Average Latency (ms)
0.01
0
Maximum Latency (ms)
503.09
207.7
95th Percentile Latency (ms)
0
0
MySQL SELECT
Linode – Nanode (1 GB)
Vultr – High Frequency Intel (2 GB)
Transactions per second
129,495.00
216,335.00
Queries per second
1,294,950.00
2,163,350.00
Minimum Latency (ms)
0.06
0.04
Average Latency (ms)
0.08
0.05
Maximum Latency (ms)
6.67
1.11
95th Percentile Latency (ms)
0.11
0.06
MySQL SELECT (Random Points)
Linode – Nanode (1 GB)
Vultr – High Frequency Intel (2 GB)
Transactions per second
6,337.00
8,316.00
Queries per second
63,370.00
83,160.00
Minimum Latency (ms)
0.41
0.4
Average Latency (ms)
1.58
1.2
Maximum Latency (ms)
8.87
3.62
95th Percentile Latency (ms)
2.26
1.55
MySQL SELECT (Random Ranges)
Linode – Nanode (1 GB)
Vultr – High Frequency Intel (2 GB)
Transactions per second
7,456.00
11,393.00
Queries per second
74,560.00
113,930.00
Minimum Latency (ms)
0.49
0.24
Average Latency (ms)
1.34
0.88
Maximum Latency (ms)
8.59
2.81
95th Percentile Latency (ms)
2.11
1.12
MySQL UPDATE (Indexed)
Linode – Nanode (1 GB)
Vultr – High Frequency Intel (2 GB)
Transactions per second
6,797.00
20,610.00
Queries per second
67,970.00
206,100.00
Minimum Latency (ms)
0.65
0.36
Average Latency (ms)
1.47
0.48
Maximum Latency (ms)
65.69
4.53
95th Percentile Latency (ms)
3.3
0.65
MySQL UPDATE (Non-Indexed)
Linode – Nanode (1 GB)
Vultr – High Frequency Intel (2 GB)
Transactions per second
9,777.00
22,150.00
Queries per second
97,770.00
221,500.00
Minimum Latency (ms)
0.67
0.37
Average Latency (ms)
1.02
0.45
Maximum Latency (ms)
8.79
9.44
95th Percentile Latency (ms)
1.34
0.54
MySQL DELETE
Linode – Nanode (1 GB)
Vultr – High Frequency Intel (2 GB)
Transactions per second
48,437.00
162,113.00
Queries per second
484,370.00
1,621,130.00
Minimum Latency (ms)
0.05
0.04
Average Latency (ms)
0.21
0.06
Maximum Latency (ms)
39.37
4.22
95th Percentile Latency (ms)
0.92
0.09
Redis
Linode – Nanode (1 GB)
Vultr – High Frequency Intel (2 GB)
PING_INLINE per Second
32,669.06
50,327.12
PING_MBULK per Second
33,738.19
52,002.08
SET per Second
15,948.96
52,966.10
GET per Second
31,675.64
53,022.27
INCR per Second
34,387.89
53,219.80
LPUSH per Second
34,650.04
52,273.91
RPUSH per Second
31,705.77
52,056.22
LPOP per Second
32,478.08
51,679.59
RPOP per Second
30,883.26
50,890.59
SADD per Second
33,046.93
49,603.17
HSET per Second
31,357.79
51,466.80
SPOP per Second
30,395.14
53,134.96
ZADD per Second
32,894.74
51,948.05
ZPOPMIN per Second
33,456.00
52,742.62
LRANGE_100 (first 100 elements) per Second
25,271.67
36,832.41
LRANGE_300 (first 300 elements) per Second
12,495.31
22,041.00
LRANGE_500 (first 500 elements) per Second
10,815.49
15,622.56
LRANGE_600 (first 600 elements) per Second
9,273.00
13,980.15
MSET (10 keys) per Second
30,066.15
50,025.02
Redis Average Latency (ms)
Linode – Nanode (1 GB)
Vultr – High Frequency Intel (2 GB)
PING_INLINE
0.94
0.61
PING_MBULK
0.90
0.58
SET
2.12
0.59
GET
1.00
0.58
INCR
0.90
0.59
LPUSH
0.90
0.60
RPUSH
0.97
0.60
LPOP
0.96
0.60
RPOP
1.01
0.61
SADD
0.93
0.62
HSET
0.99
0.60
SPOP
1.01
0.58
ZADD
0.95
0.60
ZPOPMIN
0.92
0.59
LRANGE_100 (first 100 elements)
1.29
0.85
LRANGE_300 (first 300 elements)
2.48
1.48
LRANGE_500 (first 500 elements)
2.83
2.02
LRANGE_600 (first 600 elements)
3.28
2.37
MSET (10 keys)
1.09
0.66
Conclusion
From the friendly robots:
Based on the benchmark results, the Vultr High Frequency Intel instance with 1 CPU core and 2 GB RAM outperforms the Linode Nanode with the same configuration in most metrics, especially in Redis SET and GET operations with higher requests per second (rps) and lower latencies. While both instances show similar CPU and memory performance, Vultr's CPU core shows slightly better execution times. For use cases favoring CPU-intensive or high I/O operations, Vultr's instance would generally be the better choice due to its higher benchmark scores in critical metrics.
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.