Linode Nanode (1 GB) vs. Vultr High Performance AMD (4 GB, 2 Cores)

vs.

My friend, I'm so glad you're here! Today I've spun up brand new instance from Linode and Vultr and ran my world famous suite of benchmarking scripts. All instances were running Ubuntu 24.04 LTS x64 and all resided in or around the New York / New Jersey area. Time to see who showed up today.

Overview

Linode – Nanode (1 GB) Vultr – High Performance AMD (4 GB, 2 Cores)
Last Benchmarked Fri, 29 May 2026 15:00:53 GMT Fri, 29 May 2026 10: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 $24.00
RAM (GB) 1 4
CPU Cores 1 2
Storage (TB) 25 100
Storage Type SSD NVMe
Transfer (TB) 1 5

CPU

Linode – Nanode (1 GB) Vultr – High Performance AMD (4 GB, 2 Cores)
Vendor AuthenticAMD AuthenticAMD
Model Name AMD EPYC 7642 48-Core Processor AMD EPYC-Genoa Processor
Clock Speed (MHz) 2,300.00 2,899.97
CPU Cache Size (KB) 512.00 1,024.00
BogoMips 4,599.99 5,799.93
Events per Second 1,022.23 4,654.86
Minimum Latency (ms) 0.61 0.2
Average Latency (ms) 0.98 0.21
Maximum Latency (ms) 5.4 0.47
95th Percentile Latency (ms) 2.39 0.22

Memory

Memory Read

Linode – Nanode (1 GB) Vultr – High Performance AMD (4 GB, 2 Cores)
Operations per second 5,296,233.64 7,333,962.29
Mebibytes per second 5,172.10 7,162.07
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 3.05 0.08
95th Percentile Latency (ms) 0 0

Memory Write

Linode – Nanode (1 GB) Vultr – High Performance AMD (4 GB, 2 Cores)
Operations per second 5,154,651.90 7,479,289.21
Mebibytes per second 5,033.84 7,303.99
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 3.06 12.21
95th Percentile Latency (ms) 0 0

File I/O

Linode – Nanode (1 GB) Vultr – High Performance AMD (4 GB, 2 Cores)
Reads per Second 2,055.76 7,562.64
Writes per Second 1,370.51 5,041.76
Fsyncs per Second 4,389.22 16,143.13
Read Mebibytes per Second 32.12 118.17
Written Mebibytes per Second 21.41 78.78
Minimum Latency (ms) 0 0
Average Latency (ms) 0.13 0.03
Maximum Latency (ms) 12.79 6.84
95th Percentile Latency (ms) 0.35 0.1

Mutex

Linode – Nanode (1 GB) Vultr – High Performance AMD (4 GB, 2 Cores)
Minimum Latency (ms) 1,633.32 595.39
Average Latency (ms) 1,644.62 638.90
Maximum Latency (ms) 1,653.29 672.95
95th Percentile Latency (ms) 1,648.20 669.89

MySQL

MySQL Read-only

Linode – Nanode (1 GB) Vultr – High Performance AMD (4 GB, 2 Cores)
Transactions per second 7,575.00 9,985.00
Queries per second 75,750.00 99,850.00
Minimum Latency (ms) 1.22 0.74
Average Latency (ms) 1.32 1
Maximum Latency (ms) 4.67 2.48
95th Percentile Latency (ms) 1.42 1.06

MySQL Write-only

Linode – Nanode (1 GB) Vultr – High Performance AMD (4 GB, 2 Cores)
Transactions per second 5,800.00 9,768.00
Queries per second 58,000.00 97,680.00
Minimum Latency (ms) 1.15 0.74
Average Latency (ms) 1.72 1.02
Maximum Latency (ms) 12.35 7.74
95th Percentile Latency (ms) 2.39 1.3

MySQL Read/Write

Linode – Nanode (1 GB) Vultr – High Performance AMD (4 GB, 2 Cores)
Transactions per second 2,955.00 4,671.00
Queries per second 29,550.00 46,710.00
Minimum Latency (ms) 2.64 1.72
Average Latency (ms) 3.38 2.14
Maximum Latency (ms) 22.69 8.85
95th Percentile Latency (ms) 4.41 2.57

MySQL INSERT

Linode – Nanode (1 GB) Vultr – High Performance AMD (4 GB, 2 Cores)
Transactions per second 8,921.00 16,537.00
Queries per second 89,210.00 165,370.00
Minimum Latency (ms) 0.65 0.43
Average Latency (ms) 1.12 0.6
Maximum Latency (ms) 8.92 7.37
95th Percentile Latency (ms) 1.42 0.73

MySQL Bulk INSERT

Linode – Nanode (1 GB) Vultr – High Performance AMD (4 GB, 2 Cores)
Transactions per second 1,288,467.00 2,948,592.00
Queries per second 12,884,670.00 29,485,920.00
Minimum Latency (ms) 0 0
Average Latency (ms) 0.01 0
Maximum Latency (ms) 398.24 206.98
95th Percentile Latency (ms) 0 0

MySQL SELECT

Linode – Nanode (1 GB) Vultr – High Performance AMD (4 GB, 2 Cores)
Transactions per second 170,179.00 229,032.00
Queries per second 1,701,790.00 2,290,320.00
Minimum Latency (ms) 0.05 0.02
Average Latency (ms) 0.06 0.04
Maximum Latency (ms) 7.27 0.42
95th Percentile Latency (ms) 0.08 0.05

MySQL SELECT (Random Points)

Linode – Nanode (1 GB) Vultr – High Performance AMD (4 GB, 2 Cores)
Transactions per second 7,819.00 15,101.00
Queries per second 78,190.00 151,010.00
Minimum Latency (ms) 0.42 0.21
Average Latency (ms) 1.28 0.66
Maximum Latency (ms) 6.03 1.85
95th Percentile Latency (ms) 1.64 0.83

MySQL SELECT (Random Ranges)

Linode – Nanode (1 GB) Vultr – High Performance AMD (4 GB, 2 Cores)
Transactions per second 7,328.00 14,515.00
Queries per second 73,280.00 145,150.00
Minimum Latency (ms) 0.3 0.23
Average Latency (ms) 1.36 0.69
Maximum Latency (ms) 4.97 1.72
95th Percentile Latency (ms) 1.76 0.89

MySQL UPDATE (Indexed)

Linode – Nanode (1 GB) Vultr – High Performance AMD (4 GB, 2 Cores)
Transactions per second 8,603.00 15,565.00
Queries per second 86,030.00 155,650.00
Minimum Latency (ms) 0.69 0.45
Average Latency (ms) 1.16 0.64
Maximum Latency (ms) 6.97 7.44
95th Percentile Latency (ms) 1.7 0.86

MySQL UPDATE (Non-Indexed)

Linode – Nanode (1 GB) Vultr – High Performance AMD (4 GB, 2 Cores)
Transactions per second 7,719.00 16,035.00
Queries per second 77,190.00 160,350.00
Minimum Latency (ms) 0.65 0.43
Average Latency (ms) 1.29 0.62
Maximum Latency (ms) 54.76 7.21
95th Percentile Latency (ms) 1.73 0.8

MySQL DELETE

Linode – Nanode (1 GB) Vultr – High Performance AMD (4 GB, 2 Cores)
Transactions per second 80,451.00 160,573.00
Queries per second 804,510.00 1,605,730.00
Minimum Latency (ms) 0.05 0.02
Average Latency (ms) 0.12 0.06
Maximum Latency (ms) 16.14 7.8
95th Percentile Latency (ms) 0.42 0.08

Redis

Linode – Nanode (1 GB) Vultr – High Performance AMD (4 GB, 2 Cores)
PING_INLINE per Second 44,052.86 56,465.27
PING_MBULK per Second 44,563.28 58,105.75
SET per Second 44,072.28 58,651.02
GET per Second 44,345.89 58,651.02
INCR per Second 42,535.09 58,275.06
LPUSH per Second 41,545.49 58,445.36
RPUSH per Second 37,299.52 58,858.15
LPOP per Second 43,327.55 58,892.82
RPOP per Second 43,103.45 58,582.31
SADD per Second 43,994.72 58,788.95
HSET per Second 43,956.04 58,207.21
SPOP per Second 44,130.62 57,836.90
ZADD per Second 42,390.84 58,513.75
ZPOPMIN per Second 43,159.26 58,479.53
LRANGE_100 (first 100 elements) per Second 28,843.38 49,652.43
LRANGE_300 (first 300 elements) per Second 15,153.81 34,340.66
LRANGE_500 (first 500 elements) per Second 10,595.47 26,441.04
LRANGE_600 (first 600 elements) per Second 9,122.42 24,236.55
MSET (10 keys) per Second 40,112.31 58,754.41

Redis Average Latency (ms)

Linode – Nanode (1 GB) Vultr – High Performance AMD (4 GB, 2 Cores)
PING_INLINE0.780.47
PING_MBULK0.770.44
SET0.780.44
GET0.770.44
INCR0.800.44
LPUSH0.820.44
RPUSH0.900.44
LPOP0.800.44
RPOP0.800.44
SADD0.780.44
HSET0.790.44
SPOP0.770.44
ZADD0.810.44
ZPOPMIN0.790.44
LRANGE_100 (first 100 elements)1.230.52
LRANGE_300 (first 300 elements)2.380.74
LRANGE_500 (first 500 elements)3.440.96
LRANGE_600 (first 600 elements)3.961.04
MSET (10 keys)0.880.44

Conclusion

From the friendly robots:

After thorough analysis, the Vultr High Performance AMD instance (2 cores, 4 GB RAM) outperforms the Linode Nanode (1 GB) across most benchmarks, especially in Redis and MySQL operations where it achieves higher requests per second and lower latencies. The Vultr instance also shows better file I/O performance with higher read and write speeds and lower latencies, along with better CPU performance. The Linode Nanode, though more affordable and suitable for minimal tasks and development environments, struggles with more resource-intensive operations, particularly in handling longer list ranges in Redis. Therefore, the Vultr instance is ideal for CPU-intensive and I/O-heavy workloads, while the Linode Nanode is better for lighter usage scenarios or development purposes.

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.