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

vs.

My friend, I'm so glad you're here! Today I've spun up brand new instance from Linode and Vultr and did some benchmarking. All instances were running Ubuntu 24.04 LTS x64 and were created in or around the New York / New Jersey area. Enough talk. Here's the data.

Overview

Linode – Nanode (1 GB) Vultr – Cloud Compute (2 GB)
Last Benchmarked Fri, 29 May 2026 15:00:53 GMT Wed, 27 May 2026 01:00:53 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 $10.00
RAM (GB) 1 2
CPU Cores 1 1
Storage (TB) 25 50
Storage Type SSD SSD
Transfer (TB) 1 2

CPU

Linode – Nanode (1 GB) Vultr – Cloud Compute (2 GB)
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,792.06
CPU Cache Size (KB) 512.00 16,384.00
BogoMips 4,599.99 7,584.11
Events per Second 1,022.23 1,579.21
Minimum Latency (ms) 0.61 0.61
Average Latency (ms) 0.98 0.63
Maximum Latency (ms) 5.4 2.7
95th Percentile Latency (ms) 2.39 0.67

Memory

Memory Read

Linode – Nanode (1 GB) Vultr – Cloud Compute (2 GB)
Operations per second 5,296,233.64 7,790,367.02
Mebibytes per second 5,172.10 7,607.78
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 3.05 0.91
95th Percentile Latency (ms) 0 0

Memory Write

Linode – Nanode (1 GB) Vultr – Cloud Compute (2 GB)
Operations per second 5,154,651.90 7,835,681.73
Mebibytes per second 5,033.84 7,652.03
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 3.06 0.31
95th Percentile Latency (ms) 0 0

File I/O

Linode – Nanode (1 GB) Vultr – Cloud Compute (2 GB)
Reads per Second 2,055.76 4,719.27
Writes per Second 1,370.51 3,146.18
Fsyncs per Second 4,389.22 10,070.17
Read Mebibytes per Second 32.12 73.74
Written Mebibytes per Second 21.41 49.16
Minimum Latency (ms) 0 0
Average Latency (ms) 0.13 0.06
Maximum Latency (ms) 12.79 2.06
95th Percentile Latency (ms) 0.35 0.19

Mutex

Linode – Nanode (1 GB) Vultr – Cloud Compute (2 GB)
Minimum Latency (ms) 1,633.32 1,164.11
Average Latency (ms) 1,644.62 1,170.51
Maximum Latency (ms) 1,653.29 1,177.20
95th Percentile Latency (ms) 1,648.20 1,170.65

MySQL

MySQL Read-only

Linode – Nanode (1 GB) Vultr – Cloud Compute (2 GB)
Transactions per second 7,575.00 10,424.00
Queries per second 75,750.00 104,240.00
Minimum Latency (ms) 1.22 0.9
Average Latency (ms) 1.32 0.96
Maximum Latency (ms) 4.67 2.66
95th Percentile Latency (ms) 1.42 1.01

MySQL Write-only

Linode – Nanode (1 GB) Vultr – Cloud Compute (2 GB)
Transactions per second 5,800.00 9,720.00
Queries per second 58,000.00 97,200.00
Minimum Latency (ms) 1.15 0.66
Average Latency (ms) 1.72 1.03
Maximum Latency (ms) 12.35 2.53
95th Percentile Latency (ms) 2.39 1.34

MySQL Read/Write

Linode – Nanode (1 GB) Vultr – Cloud Compute (2 GB)
Transactions per second 2,955.00 4,493.00
Queries per second 29,550.00 44,930.00
Minimum Latency (ms) 2.64 1.75
Average Latency (ms) 3.38 2.22
Maximum Latency (ms) 22.69 5.2
95th Percentile Latency (ms) 4.41 2.61

MySQL INSERT

Linode – Nanode (1 GB) Vultr – Cloud Compute (2 GB)
Transactions per second 8,921.00 16,702.00
Queries per second 89,210.00 167,020.00
Minimum Latency (ms) 0.65 0.37
Average Latency (ms) 1.12 0.6
Maximum Latency (ms) 8.92 10.4
95th Percentile Latency (ms) 1.42 0.81

MySQL Bulk INSERT

Linode – Nanode (1 GB) Vultr – Cloud Compute (2 GB)
Transactions per second 1,288,467.00 1,841,842.00
Queries per second 12,884,670.00 18,418,420.00
Minimum Latency (ms) 0 0
Average Latency (ms) 0.01 0.01
Maximum Latency (ms) 398.24 296.53
95th Percentile Latency (ms) 0 0

MySQL SELECT

Linode – Nanode (1 GB) Vultr – Cloud Compute (2 GB)
Transactions per second 170,179.00 227,412.00
Queries per second 1,701,790.00 2,274,120.00
Minimum Latency (ms) 0.05 0.04
Average Latency (ms) 0.06 0.04
Maximum Latency (ms) 7.27 0.93
95th Percentile Latency (ms) 0.08 0.05

MySQL SELECT (Random Points)

Linode – Nanode (1 GB) Vultr – Cloud Compute (2 GB)
Transactions per second 7,819.00 10,667.00
Queries per second 78,190.00 106,670.00
Minimum Latency (ms) 0.42 0.21
Average Latency (ms) 1.28 0.94
Maximum Latency (ms) 6.03 2.7
95th Percentile Latency (ms) 1.64 1.21

MySQL SELECT (Random Ranges)

Linode – Nanode (1 GB) Vultr – Cloud Compute (2 GB)
Transactions per second 7,328.00 11,119.00
Queries per second 73,280.00 111,190.00
Minimum Latency (ms) 0.3 0.34
Average Latency (ms) 1.36 0.9
Maximum Latency (ms) 4.97 2.64
95th Percentile Latency (ms) 1.76 1.16

MySQL UPDATE (Indexed)

Linode – Nanode (1 GB) Vultr – Cloud Compute (2 GB)
Transactions per second 8,603.00 16,436.00
Queries per second 86,030.00 164,360.00
Minimum Latency (ms) 0.69 0.39
Average Latency (ms) 1.16 0.61
Maximum Latency (ms) 6.97 11.62
95th Percentile Latency (ms) 1.7 0.83

MySQL UPDATE (Non-Indexed)

Linode – Nanode (1 GB) Vultr – Cloud Compute (2 GB)
Transactions per second 7,719.00 16,970.00
Queries per second 77,190.00 169,700.00
Minimum Latency (ms) 0.65 0.36
Average Latency (ms) 1.29 0.59
Maximum Latency (ms) 54.76 1.67
95th Percentile Latency (ms) 1.73 0.78

MySQL DELETE

Linode – Nanode (1 GB) Vultr – Cloud Compute (2 GB)
Transactions per second 80,451.00 149,661.00
Queries per second 804,510.00 1,496,610.00
Minimum Latency (ms) 0.05 0.04
Average Latency (ms) 0.12 0.07
Maximum Latency (ms) 16.14 1.85
95th Percentile Latency (ms) 0.42 0.1

Redis

Linode – Nanode (1 GB) Vultr – Cloud Compute (2 GB)
PING_INLINE per Second 44,052.86 55,617.35
PING_MBULK per Second 44,563.28 56,022.41
SET per Second 44,072.28 55,340.34
GET per Second 44,345.89 55,586.44
INCR per Second 42,535.09 55,617.35
LPUSH per Second 41,545.49 54,347.82
RPUSH per Second 37,299.52 55,005.50
LPOP per Second 43,327.55 54,674.69
RPOP per Second 43,103.45 54,945.05
SADD per Second 43,994.72 55,741.36
HSET per Second 43,956.04 55,157.20
SPOP per Second 44,130.62 56,179.78
ZADD per Second 42,390.84 54,854.64
ZPOPMIN per Second 43,159.26 55,772.45
LRANGE_100 (first 100 elements) per Second 28,843.38 37,160.91
LRANGE_300 (first 300 elements) per Second 15,153.81 20,424.84
LRANGE_500 (first 500 elements) per Second 10,595.47 14,198.49
LRANGE_600 (first 600 elements) per Second 9,122.42 12,430.08
MSET (10 keys) per Second 40,112.31 51,840.33

Redis Average Latency (ms)

Linode – Nanode (1 GB) Vultr – Cloud Compute (2 GB)
PING_INLINE0.780.58
PING_MBULK0.770.57
SET0.780.59
GET0.770.58
INCR0.800.58
LPUSH0.820.60
RPUSH0.900.59
LPOP0.800.59
RPOP0.800.59
SADD0.780.57
HSET0.790.59
SPOP0.770.57
ZADD0.810.59
ZPOPMIN0.790.57
LRANGE_100 (first 100 elements)1.230.93
LRANGE_300 (first 300 elements)2.381.71
LRANGE_500 (first 500 elements)3.442.54
LRANGE_600 (first 600 elements)3.962.90
MSET (10 keys)0.880.67

Conclusion

From the friendly robots:

Comparing the benchmarks for Linode's Nanode (1 GB) and Vultr's Cloud Compute (2 GB), we see that Vultr's instance outperforms Linode's in most categories, especially in Redis operations where the Vultr instance shows higher request rates per second (rps) and lower latency across various commands. The Vultr instance also shows stronger performance in CPU, file I/O, and memory operations, with higher throughput and lower latencies. The Linode instance, while more cost-effective, does not match Vultr's benchmark metrics across the board, indicating that the Vultr instance is better suited for CPU-intensive and I/O-heavy workloads. Therefore, for developers seeking higher performance at a modest price increase, the Vultr Cloud Compute (2 GB) is the recommended choice.

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.