Vultr Cloud Compute (1 GB) vs. Linode Nanode (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

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Last Benchmarked Tue, 21 Apr 2026 04:00:52 GMT Sun, 19 Apr 2026 14:00:52 GMT
Linux Distro Ubuntu 24.04 LTS x64 Ubuntu 24.04 LTS x64
Kernel Version 6.8.0-110-generic 6.8.0-71-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

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Vendor GenuineIntel AuthenticAMD
Model Name Intel Core Processor (Broadwell, no TSX, IBRS) AMD EPYC 7642 48-Core Processor
Clock Speed (MHz) 2,400.00 2,300.00
CPU Cache Size (KB) 16,384.00 512.00
BogoMips 4,799.99 4,600.00
Events per Second 826.34 870.55
Minimum Latency (ms) 1.1 0.61
Average Latency (ms) 1.21 1.15
Maximum Latency (ms) 3.76 5.82
95th Percentile Latency (ms) 1.32 2.39

Memory

Memory Read

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

Memory Write

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

File I/O

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

Mutex

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

MySQL

MySQL Read-only

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

MySQL Write-only

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

MySQL Read/Write

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

MySQL INSERT

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

MySQL Bulk INSERT

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

MySQL SELECT

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

MySQL SELECT (Random Points)

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

MySQL SELECT (Random Ranges)

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

MySQL UPDATE (Indexed)

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

MySQL UPDATE (Non-Indexed)

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

MySQL DELETE

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

Redis

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

Redis Average Latency (ms)

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
PING_INLINE1.020.80
PING_MBULK0.980.75
SET1.000.76
GET1.080.76
INCR1.030.76
LPUSH1.010.76
RPUSH1.010.75
LPOP1.010.77
RPOP1.020.77
SADD1.020.76
HSET1.020.77
SPOP0.990.75
ZADD0.990.76
ZPOPMIN1.010.74
LRANGE_100 (first 100 elements)1.641.18
LRANGE_300 (first 300 elements)3.082.24
LRANGE_500 (first 500 elements)4.263.30
LRANGE_600 (first 600 elements)5.013.71
MSET (10 keys)1.180.84

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.