Linode Nanode (1 GB) vs. Vultr High Frequency Intel (2 GB, 2 Cores)

vs.

Welcome to another round of the VPS Showdown. Today I've spun up some brand new instance from Linode and Vultr and ran some benchmarks. Each instance was running Ubuntu 24.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, 2 Cores)
Last Benchmarked Fri, 29 May 2026 15:00:53 GMT Thu, 28 May 2026 12: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-117-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 $18.00
RAM (GB) 1 2
CPU Cores 1 2
Storage (TB) 25 80
Storage Type SSD NVMe
Transfer (TB) 1 3

CPU

Linode – Nanode (1 GB) Vultr – High Frequency Intel (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,791.97
CPU Cache Size (KB) 512.00 16,384.00
BogoMips 4,599.99 7,583.94
Events per Second 1,022.23 1,620.67
Minimum Latency (ms) 0.61 0.6
Average Latency (ms) 0.98 0.62
Maximum Latency (ms) 5.4 2.65
95th Percentile Latency (ms) 2.39 0.65

Memory

Memory Read

Linode – Nanode (1 GB) Vultr – High Frequency Intel (2 GB, 2 Cores)
Operations per second 5,296,233.64 8,063,058.47
Mebibytes per second 5,172.10 7,874.08
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 3.05 0.17
95th Percentile Latency (ms) 0 0

Memory Write

Linode – Nanode (1 GB) Vultr – High Frequency Intel (2 GB, 2 Cores)
Operations per second 5,154,651.90 8,051,875.89
Mebibytes per second 5,033.84 7,863.16
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 3.06 0.09
95th Percentile Latency (ms) 0 0

File I/O

Linode – Nanode (1 GB) Vultr – High Frequency Intel (2 GB, 2 Cores)
Reads per Second 2,055.76 4,504.72
Writes per Second 1,370.51 3,003.08
Fsyncs per Second 4,389.22 9,619.45
Read Mebibytes per Second 32.12 70.39
Written Mebibytes per Second 21.41 46.92
Minimum Latency (ms) 0 0
Average Latency (ms) 0.13 0.06
Maximum Latency (ms) 12.79 2.28
95th Percentile Latency (ms) 0.35 0.19

Mutex

Linode – Nanode (1 GB) Vultr – High Frequency Intel (2 GB, 2 Cores)
Minimum Latency (ms) 1,633.32 491.88
Average Latency (ms) 1,644.62 531.71
Maximum Latency (ms) 1,653.29 553.44
95th Percentile Latency (ms) 1,648.20 549.52

MySQL

MySQL Read-only

Linode – Nanode (1 GB) Vultr – High Frequency Intel (2 GB, 2 Cores)
Transactions per second 7,575.00 10,761.00
Queries per second 75,750.00 107,610.00
Minimum Latency (ms) 1.22 0.86
Average Latency (ms) 1.32 0.93
Maximum Latency (ms) 4.67 2.78
95th Percentile Latency (ms) 1.42 0.99

MySQL Write-only

Linode – Nanode (1 GB) Vultr – High Frequency Intel (2 GB, 2 Cores)
Transactions per second 5,800.00 10,581.00
Queries per second 58,000.00 105,810.00
Minimum Latency (ms) 1.15 0.65
Average Latency (ms) 1.72 0.94
Maximum Latency (ms) 12.35 2.18
95th Percentile Latency (ms) 2.39 1.16

MySQL Read/Write

Linode – Nanode (1 GB) Vultr – High Frequency Intel (2 GB, 2 Cores)
Transactions per second 2,955.00 5,226.00
Queries per second 29,550.00 52,260.00
Minimum Latency (ms) 2.64 1.58
Average Latency (ms) 3.38 1.91
Maximum Latency (ms) 22.69 3.73
95th Percentile Latency (ms) 4.41 2.18

MySQL INSERT

Linode – Nanode (1 GB) Vultr – High Frequency Intel (2 GB, 2 Cores)
Transactions per second 8,921.00 17,000.00
Queries per second 89,210.00 170,000.00
Minimum Latency (ms) 0.65 0.37
Average Latency (ms) 1.12 0.59
Maximum Latency (ms) 8.92 11.6
95th Percentile Latency (ms) 1.42 0.75

MySQL Bulk INSERT

Linode – Nanode (1 GB) Vultr – High Frequency Intel (2 GB, 2 Cores)
Transactions per second 1,288,467.00 2,569,967.00
Queries per second 12,884,670.00 25,699,670.00
Minimum Latency (ms) 0 0
Average Latency (ms) 0.01 0
Maximum Latency (ms) 398.24 200.07
95th Percentile Latency (ms) 0 0

MySQL SELECT

Linode – Nanode (1 GB) Vultr – High Frequency Intel (2 GB, 2 Cores)
Transactions per second 170,179.00 242,396.00
Queries per second 1,701,790.00 2,423,960.00
Minimum Latency (ms) 0.05 0.03
Average Latency (ms) 0.06 0.04
Maximum Latency (ms) 7.27 1.23
95th Percentile Latency (ms) 0.08 0.05

MySQL SELECT (Random Points)

Linode – Nanode (1 GB) Vultr – High Frequency Intel (2 GB, 2 Cores)
Transactions per second 7,819.00 12,257.00
Queries per second 78,190.00 122,570.00
Minimum Latency (ms) 0.42 0.29
Average Latency (ms) 1.28 0.82
Maximum Latency (ms) 6.03 3.45
95th Percentile Latency (ms) 1.64 1.04

MySQL SELECT (Random Ranges)

Linode – Nanode (1 GB) Vultr – High Frequency Intel (2 GB, 2 Cores)
Transactions per second 7,328.00 10,662.00
Queries per second 73,280.00 106,620.00
Minimum Latency (ms) 0.3 0.37
Average Latency (ms) 1.36 0.94
Maximum Latency (ms) 4.97 3.73
95th Percentile Latency (ms) 1.76 1.21

MySQL UPDATE (Indexed)

Linode – Nanode (1 GB) Vultr – High Frequency Intel (2 GB, 2 Cores)
Transactions per second 8,603.00 17,977.00
Queries per second 86,030.00 179,770.00
Minimum Latency (ms) 0.69 0.39
Average Latency (ms) 1.16 0.56
Maximum Latency (ms) 6.97 1.84
95th Percentile Latency (ms) 1.7 0.72

MySQL UPDATE (Non-Indexed)

Linode – Nanode (1 GB) Vultr – High Frequency Intel (2 GB, 2 Cores)
Transactions per second 7,719.00 17,717.00
Queries per second 77,190.00 177,170.00
Minimum Latency (ms) 0.65 0.37
Average Latency (ms) 1.29 0.56
Maximum Latency (ms) 54.76 11.15
95th Percentile Latency (ms) 1.73 0.73

MySQL DELETE

Linode – Nanode (1 GB) Vultr – High Frequency Intel (2 GB, 2 Cores)
Transactions per second 80,451.00 160,036.00
Queries per second 804,510.00 1,600,360.00
Minimum Latency (ms) 0.05 0.03
Average Latency (ms) 0.12 0.06
Maximum Latency (ms) 16.14 7.55
95th Percentile Latency (ms) 0.42 0.06

Redis

Linode – Nanode (1 GB) Vultr – High Frequency Intel (2 GB, 2 Cores)
PING_INLINE per Second 44,052.86 90,991.81
PING_MBULK per Second 44,563.28 90,579.71
SET per Second 44,072.28 91,407.68
GET per Second 44,345.89 91,491.30
INCR per Second 42,535.09 91,157.70
LPUSH per Second 41,545.49 92,421.44
RPUSH per Second 37,299.52 90,497.73
LPOP per Second 43,327.55 91,743.12
RPOP per Second 43,103.45 91,407.68
SADD per Second 43,994.72 91,407.68
HSET per Second 43,956.04 93,283.58
SPOP per Second 44,130.62 91,911.76
ZADD per Second 42,390.84 92,678.41
ZPOPMIN per Second 43,159.26 92,506.94
LRANGE_100 (first 100 elements) per Second 28,843.38 69,108.50
LRANGE_300 (first 300 elements) per Second 15,153.81 38,124.29
LRANGE_500 (first 500 elements) per Second 10,595.47 26,824.04
LRANGE_600 (first 600 elements) per Second 9,122.42 24,044.24
MSET (10 keys) per Second 40,112.31 93,984.96

Redis Average Latency (ms)

Linode – Nanode (1 GB) Vultr – High Frequency Intel (2 GB, 2 Cores)
PING_INLINE0.780.29
PING_MBULK0.770.28
SET0.780.28
GET0.770.28
INCR0.800.28
LPUSH0.820.28
RPUSH0.900.28
LPOP0.800.28
RPOP0.800.28
SADD0.780.28
HSET0.790.28
SPOP0.770.28
ZADD0.810.28
ZPOPMIN0.790.28
LRANGE_100 (first 100 elements)1.230.37
LRANGE_300 (first 300 elements)2.380.67
LRANGE_500 (first 500 elements)3.440.96
LRANGE_600 (first 600 elements)3.961.06
MSET (10 keys)0.880.28

Conclusion

From the friendly robots:

The Linode Nanode (1 GB) instance shows impressive throughput for Redis commands, particularly in high request per second (rps) metrics and low latency, though its performance declines significantly when handling larger data sets for commands like LRANGE. It also has excellent file I/O performance with high throughput rates for both read and write operations. However, its CPU and memory benchmarks, despite strong performance metrics, lack the raw multi-core processing power found in other instances. On the other hand, the Vultr High Frequency Intel (2 GB, 2 Cores) instance provides stellar Redis performance with significantly higher rps metrics and lower latencies across a variety of operations, and it handles bulk insert and point select operations with ease. While its file I/O and memory benchmarks also show strong performance, its multi-threading capabilities and overall CPU performance are slightly less impressive than the Linode instance when it comes to multi-threading fairness and lower thread execution times. In summary, the Linode Nanode is ideal for applications requiring high I/O performance and moderate multi-core processing, while the Vultr High Frequency Intel excels in scenarios that demand high concurrency and multi-core processing efficiency.

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.

You can also support me directly by buying me a coffee.