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

vs.

Same showdown, different day. Today I've spun up brand new instance from Linode and Vultr to run some benchmarks on. Each instance was running Ubuntu 24.04 LTS x64 and were created in the New York area (or close to it). Enough talk. Here's the data.

Overview

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Last Benchmarked Wed, 18 Feb 2026 22:00:52 GMT Wed, 18 Feb 2026 07:00:51 GMT
Linux Distro Ubuntu 24.04 LTS x64 Ubuntu 24.04 LTS x64
Kernel Version 6.8.0-71-generic 6.8.0-100-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 7713 64-Core Processor Intel Core Processor (Haswell, no TSX, IBRS)
Clock Speed (MHz) 2,000.00 2,400.00
CPU Cache Size (KB) 512.00 16,384.00
BogoMips 3,999.99 4,799.99
Events per Second 1,796.69 789.59
Minimum Latency (ms) 0.24 1.16
Average Latency (ms) 0.56 1.27
Maximum Latency (ms) 33.29 3.45
95th Percentile Latency (ms) 2.52 1.34

Memory

Memory Read

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Operations per second 2,781,893.45 3,918,177.35
Mebibytes per second 2,716.69 3,826.35
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 8.48 0.23
95th Percentile Latency (ms) 0 0

Memory Write

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Operations per second 3,003,981.67 3,908,567.36
Mebibytes per second 2,933.58 3,816.96
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 31.65 0.45
95th Percentile Latency (ms) 0 0

File I/O

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Reads per Second 2,901.52 1,594.63
Writes per Second 1,934.35 1,063.09
Fsyncs per Second 6,191.21 3,407.62
Read Mebibytes per Second 45.34 24.92
Written Mebibytes per Second 30.22 16.61
Minimum Latency (ms) 0 0
Average Latency (ms) 0.09 0.16
Maximum Latency (ms) 15.73 32.52
95th Percentile Latency (ms) 0.24 0.42

Mutex

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Minimum Latency (ms) 1,404.10 2,039.00
Average Latency (ms) 1,411.48 2,047.18
Maximum Latency (ms) 1,422.33 2,058.11
95th Percentile Latency (ms) 1,427.08 2,045.74

MySQL

MySQL Read-only

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Transactions per second 9,135.00 4,857.00
Queries per second 91,350.00 48,570.00
Minimum Latency (ms) 0.98 1.84
Average Latency (ms) 1.09 2.06
Maximum Latency (ms) 10.15 8.4
95th Percentile Latency (ms) 1.27 2.18

MySQL Write-only

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Transactions per second 6,708.00 2,825.00
Queries per second 67,080.00 28,250.00
Minimum Latency (ms) 0.87 1.95
Average Latency (ms) 1.49 3.54
Maximum Latency (ms) 37.92 32.06
95th Percentile Latency (ms) 2.03 6.32

MySQL Read/Write

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Transactions per second 3,482.00 1,532.00
Queries per second 34,820.00 15,320.00
Minimum Latency (ms) 2.16 4.34
Average Latency (ms) 2.87 6.52
Maximum Latency (ms) 9.8 35
95th Percentile Latency (ms) 3.55 10.27

MySQL INSERT

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Transactions per second 10,885.00 4,892.00
Queries per second 108,850.00 48,920.00
Minimum Latency (ms) 0.58 1.12
Average Latency (ms) 0.92 2.04
Maximum Latency (ms) 6.79 19.75
95th Percentile Latency (ms) 1.12 3.96

MySQL Bulk INSERT

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Transactions per second 1,887,810.00 833,039.00
Queries per second 18,878,100.00 8,330,390.00
Minimum Latency (ms) 0 0
Average Latency (ms) 0.01 0.01
Maximum Latency (ms) 322.52 655.03
95th Percentile Latency (ms) 0 0

MySQL SELECT

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Transactions per second 203,558.00 102,586.00
Queries per second 2,035,580.00 1,025,860.00
Minimum Latency (ms) 0.04 0.07
Average Latency (ms) 0.05 0.1
Maximum Latency (ms) 13.04 2.33
95th Percentile Latency (ms) 0.06 0.13

MySQL SELECT (Random Points)

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Transactions per second 11,192.00 5,155.00
Queries per second 111,920.00 51,550.00
Minimum Latency (ms) 0.21 0.65
Average Latency (ms) 0.89 1.94
Maximum Latency (ms) 6.53 10.67
95th Percentile Latency (ms) 1.18 2.52

MySQL SELECT (Random Ranges)

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Transactions per second 11,116.00 5,999.00
Queries per second 111,160.00 59,990.00
Minimum Latency (ms) 0.24 0.53
Average Latency (ms) 0.9 1.67
Maximum Latency (ms) 7.03 7.75
95th Percentile Latency (ms) 1.16 2.18

MySQL UPDATE (Indexed)

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Transactions per second 9,976.00 3,979.00
Queries per second 99,760.00 39,790.00
Minimum Latency (ms) 0.56 1.1
Average Latency (ms) 1 2.51
Maximum Latency (ms) 4.74 36.68
95th Percentile Latency (ms) 1.34 4.91

MySQL UPDATE (Non-Indexed)

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Transactions per second 10,150.00 4,131.00
Queries per second 101,500.00 41,310.00
Minimum Latency (ms) 0.54 1.21
Average Latency (ms) 0.98 2.42
Maximum Latency (ms) 41.86 24.52
95th Percentile Latency (ms) 1.27 4.91

MySQL DELETE

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Transactions per second 101,100.00 30,696.00
Queries per second 1,011,000.00 306,960.00
Minimum Latency (ms) 0.04 0.08
Average Latency (ms) 0.1 0.32
Maximum Latency (ms) 8.67 51.16
95th Percentile Latency (ms) 0.16 1.76

Redis

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
PING_INLINE per Second 54,734.54 33,715.44
PING_MBULK per Second 55,493.89 35,663.34
SET per Second 55,248.62 34,602.07
GET per Second 55,218.11 37,243.95
INCR per Second 55,648.30 35,310.73
LPUSH per Second 54,200.54 35,549.23
RPUSH per Second 54,141.85 35,739.81
LPOP per Second 53,418.80 36,818.85
RPOP per Second 54,525.63 35,460.99
SADD per Second 55,524.71 36,589.83
HSET per Second 53,078.56 36,114.12
SPOP per Second 54,614.96 37,299.52
ZADD per Second 54,975.26 35,511.36
ZPOPMIN per Second 55,066.08 37,009.62
LRANGE_100 (first 100 elements) per Second 38,022.81 23,986.57
LRANGE_300 (first 300 elements) per Second 20,230.63 12,658.23
LRANGE_500 (first 500 elements) per Second 14,701.56 8,469.55
LRANGE_600 (first 600 elements) per Second 13,066.77 7,245.33
MSET (10 keys) per Second 52,659.29 32,819.17

Redis Average Latency (ms)

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
PING_INLINE0.610.99
PING_MBULK0.590.91
SET0.600.95
GET0.590.88
INCR0.590.93
LPUSH0.620.93
RPUSH0.620.93
LPOP0.630.91
RPOP0.610.94
SADD0.590.90
HSET0.630.91
SPOP0.600.88
ZADD0.610.93
ZPOPMIN0.600.89
LRANGE_100 (first 100 elements)0.911.39
LRANGE_300 (first 300 elements)1.702.66
LRANGE_500 (first 500 elements)2.364.01
LRANGE_600 (first 600 elements)2.654.62
MSET (10 keys)0.671.06

Conclusion

From the friendly robots:

After analyzing the benchmarks from both Linode's Nanode and Vultr's Cloud Compute instances, it's evident that Linode's Nanode excels in high-throughput operations, especially in Redis benchmarks, where it offers significantly higher requests per second and lower latency across various commands compared to Vultr's Cloud Compute. Linode's instance also demonstrates superior CPU and I/O performance, which translates into better handling of memory operations and thread fairness. On the other hand, Vultr's Cloud Compute shows better performance in MySQL OLTP operations, with faster read-write latencies and more efficient bulk insert operations. However, overall, Linode's Nanode stands out in CPU-intensive and I/O-heavy workloads, making it ideal for developers and sysadmins looking for higher throughput and lower latencies, whereas Vultr's Cloud Compute might be more suitable for users focusing on database-intensive tasks.

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.