Linode Nanode (1 GB) vs. Vultr Cloud Compute (1 GB)

vs.

New day, new benchmarks. Today I've spun up brand new instance from Linode and Vultr and did some benchmarking. Each instance was spun up with 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 – Cloud Compute (1 GB)
Last Benchmarked Sun, 19 Apr 2026 14:00:52 GMT Tue, 21 Apr 2026 04: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-110-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 7642 48-Core Processor Intel Core Processor (Broadwell, no TSX, IBRS)
Clock Speed (MHz) 2,300.00 2,400.00
CPU Cache Size (KB) 512.00 16,384.00
BogoMips 4,600.00 4,799.99
Events per Second 870.55 826.34
Minimum Latency (ms) 0.61 1.1
Average Latency (ms) 1.15 1.21
Maximum Latency (ms) 5.82 3.76
95th Percentile Latency (ms) 2.39 1.32

Memory

Memory Read

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Operations per second 5,322,238.86 4,008,171.55
Mebibytes per second 5,197.50 3,914.23
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 3.04 1.03
95th Percentile Latency (ms) 0 0

Memory Write

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Operations per second 5,331,891.74 3,870,938.62
Mebibytes per second 5,206.93 3,780.21
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 2.25 0.49
95th Percentile Latency (ms) 0 0

File I/O

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Reads per Second 2,182.31 2,271.08
Writes per Second 1,454.87 1,514.06
Fsyncs per Second 4,665.48 4,848.37
Read Mebibytes per Second 34.10 35.49
Written Mebibytes per Second 22.73 23.66
Minimum Latency (ms) 0 0
Average Latency (ms) 0.12 0.12
Maximum Latency (ms) 3.58 3.58
95th Percentile Latency (ms) 0.34 0.31

Mutex

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Minimum Latency (ms) 1,580.75 2,093.90
Average Latency (ms) 1,588.71 2,105.38
Maximum Latency (ms) 1,594.17 2,110.66
95th Percentile Latency (ms) 1,589.90 2,120.76

MySQL

MySQL Read-only

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Transactions per second 7,579.00 5,169.00
Queries per second 75,790.00 51,690.00
Minimum Latency (ms) 1.22 1.68
Average Latency (ms) 1.32 1.93
Maximum Latency (ms) 4.45 11.71
95th Percentile Latency (ms) 1.37 2.18

MySQL Write-only

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Transactions per second 6,181.00 3,484.00
Queries per second 61,810.00 34,840.00
Minimum Latency (ms) 1.04 1.87
Average Latency (ms) 1.62 2.87
Maximum Latency (ms) 16.59 33.82
95th Percentile Latency (ms) 2.3 4.03

MySQL Read/Write

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Transactions per second 3,023.00 1,849.00
Queries per second 30,230.00 18,490.00
Minimum Latency (ms) 2.43 4.08
Average Latency (ms) 3.31 5.4
Maximum Latency (ms) 20.06 13.46
95th Percentile Latency (ms) 4.41 6.67

MySQL INSERT

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Transactions per second 9,947.00 6,034.00
Queries per second 99,470.00 60,340.00
Minimum Latency (ms) 0.63 1.06
Average Latency (ms) 1 1.65
Maximum Latency (ms) 6.06 9.79
95th Percentile Latency (ms) 1.25 2.11

MySQL Bulk INSERT

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Transactions per second 1,259,342.00 931,337.00
Queries per second 12,593,420.00 9,313,370.00
Minimum Latency (ms) 0 0
Average Latency (ms) 0.01 0.01
Maximum Latency (ms) 381.94 589.1
95th Percentile Latency (ms) 0 0

MySQL SELECT

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Transactions per second 177,037.00 116,233.00
Queries per second 1,770,370.00 1,162,330.00
Minimum Latency (ms) 0.05 0.06
Average Latency (ms) 0.06 0.09
Maximum Latency (ms) 3.28 14.32
95th Percentile Latency (ms) 0.07 0.12

MySQL SELECT (Random Points)

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Transactions per second 8,078.00 4,606.00
Queries per second 80,780.00 46,060.00
Minimum Latency (ms) 0.42 0.7
Average Latency (ms) 1.24 2.17
Maximum Latency (ms) 4.46 8.14
95th Percentile Latency (ms) 1.55 2.91

MySQL SELECT (Random Ranges)

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Transactions per second 7,557.00 5,874.00
Queries per second 75,570.00 58,740.00
Minimum Latency (ms) 0.31 0.66
Average Latency (ms) 1.32 1.7
Maximum Latency (ms) 5.2 5.29
95th Percentile Latency (ms) 1.7 2.3

MySQL UPDATE (Indexed)

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Transactions per second 8,784.00 5,285.00
Queries per second 87,840.00 52,850.00
Minimum Latency (ms) 0.67 1.09
Average Latency (ms) 1.14 1.89
Maximum Latency (ms) 9.13 6.88
95th Percentile Latency (ms) 1.67 2.57

MySQL UPDATE (Non-Indexed)

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Transactions per second 10,009.00 5,414.00
Queries per second 100,090.00 54,140.00
Minimum Latency (ms) 0.62 1.31
Average Latency (ms) 1 1.85
Maximum Latency (ms) 5.98 24.95
95th Percentile Latency (ms) 1.3 2.43

MySQL DELETE

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Transactions per second 90,198.00 40,863.00
Queries per second 901,980.00 408,630.00
Minimum Latency (ms) 0.05 0.07
Average Latency (ms) 0.11 0.24
Maximum Latency (ms) 4.51 8.32
95th Percentile Latency (ms) 0.23 1.61

Redis

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
PING_INLINE per Second 42,140.75 32,154.34
PING_MBULK per Second 46,040.52 33,579.59
SET per Second 45,558.09 32,669.06
GET per Second 45,558.09 30,646.64
INCR per Second 45,004.50 31,496.06
LPUSH per Second 45,641.26 32,278.89
RPUSH per Second 45,871.56 32,092.43
LPOP per Second 45,330.91 32,435.94
RPOP per Second 44,843.05 32,258.07
SADD per Second 45,620.44 31,735.96
HSET per Second 44,662.79 32,010.24
SPOP per Second 45,955.88 32,829.94
ZADD per Second 45,228.40 32,851.51
ZPOPMIN per Second 46,189.38 31,816.74
LRANGE_100 (first 100 elements) per Second 30,193.24 20,542.32
LRANGE_300 (first 300 elements) per Second 16,225.86 11,186.93
LRANGE_500 (first 500 elements) per Second 10,879.02 7,990.41
LRANGE_600 (first 600 elements) per Second 9,745.64 6,689.86
MSET (10 keys) per Second 41,928.72 29,086.68

Redis Average Latency (ms)

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
PING_INLINE0.801.02
PING_MBULK0.750.98
SET0.761.00
GET0.761.08
INCR0.761.03
LPUSH0.761.01
RPUSH0.751.01
LPOP0.771.01
RPOP0.771.02
SADD0.761.02
HSET0.771.02
SPOP0.750.99
ZADD0.760.99
ZPOPMIN0.741.01
LRANGE_100 (first 100 elements)1.181.64
LRANGE_300 (first 300 elements)2.243.08
LRANGE_500 (first 500 elements)3.304.26
LRANGE_600 (first 600 elements)3.715.01
MSET (10 keys)0.841.18

Conclusion

From the friendly robots:

When comparing the Linode Nanode (1 GB) and Vultr Cloud Compute (1 GB) instances based on their benchmark results, the Linode instance shows slightly better performance in Redis operations, with higher requests per second (rps) and lower latency across most commands, although the Vultr instance outperforms in SET and GET operations. The Vultr instance generally exhibits lower average latencies in CPU benchmarks, but both instances have similar throughput in file I/O and memory operations. Considering these results, the Linode instance might be more suitable for applications that benefit from faster Redis operations, while the Vultr instance could be preferred for workloads where CPU performance, even with higher latency, is critical and where SET and GET operations are predominant. For use cases that do not heavily favor specific Redis operations or CPU tasks, either instance would suffice given their comparable resource allocations.

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.