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

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

Memory

Memory Read

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

Memory Write

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

File I/O

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

Mutex

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

MySQL

MySQL Read-only

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

MySQL Write-only

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

MySQL Read/Write

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

MySQL INSERT

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

MySQL Bulk INSERT

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

MySQL SELECT

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

MySQL SELECT (Random Points)

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

MySQL SELECT (Random Ranges)

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

MySQL UPDATE (Indexed)

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

MySQL UPDATE (Non-Indexed)

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

MySQL DELETE

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

Redis

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

Redis Average Latency (ms)

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
PING_INLINE0.990.61
PING_MBULK0.910.59
SET0.950.60
GET0.880.59
INCR0.930.59
LPUSH0.930.62
RPUSH0.930.62
LPOP0.910.63
RPOP0.940.61
SADD0.900.59
HSET0.910.63
SPOP0.880.60
ZADD0.930.61
ZPOPMIN0.890.60
LRANGE_100 (first 100 elements)1.390.91
LRANGE_300 (first 300 elements)2.661.70
LRANGE_500 (first 500 elements)4.012.36
LRANGE_600 (first 600 elements)4.622.65
MSET (10 keys)1.060.67

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.