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

vs.

Fresh benchmarks coming at ya. Today I've spun up some 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. Enough talk. Here's the data.

Overview

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Last Benchmarked Tue, 26 Aug 2025 17:00:52 GMT Mon, 25 Aug 2025 13:00:52 GMT
Linux Distro Ubuntu 24.04 LTS x64 Ubuntu 24.04 LTS x64
Kernel Version 6.8.0-60-generic 6.8.0-71-generic
MySQL Version 8.0.43-0ubuntu0.24.04.1 8.0.43-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 7713 64-Core Processor
Clock Speed (MHz) 2,394.45 2,000.00
CPU Cache Size (KB) 16,384.00 512.00
BogoMips 4,788.90 4,000.00
Events per Second 861.36 1,709.10
Minimum Latency (ms) 1.14 0.28
Average Latency (ms) 1.16 0.58
Maximum Latency (ms) 2.77 3.53
95th Percentile Latency (ms) 1.21 2.03

Memory

Memory Read

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Operations per second 4,189,369.10 5,389,227.66
Mebibytes per second 4,091.18 5,262.92
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 1.75 2.68
95th Percentile Latency (ms) 0 0

Memory Write

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Operations per second 4,222,451.44 5,415,718.29
Mebibytes per second 4,123.49 5,288.79
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 0.72 2.63
95th Percentile Latency (ms) 0 0

File I/O

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Reads per Second 2,500.89 2,297.45
Writes per Second 1,667.19 1,531.64
Fsyncs per Second 5,346.52 4,911.47
Read Mebibytes per Second 39.08 35.90
Written Mebibytes per Second 26.05 23.93
Minimum Latency (ms) 0 0
Average Latency (ms) 0.1 0.11
Maximum Latency (ms) 3.4 4.66
95th Percentile Latency (ms) 0.3 0.29

Mutex

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Minimum Latency (ms) 2,081.46 1,636.97
Average Latency (ms) 2,089.86 1,644.52
Maximum Latency (ms) 2,098.02 1,650.06
95th Percentile Latency (ms) 2,082.91 1,648.20

MySQL

MySQL Read-only

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Transactions per second 5,526.00 7,736.00
Queries per second 55,260.00 77,360.00
Minimum Latency (ms) 1.7 1.18
Average Latency (ms) 1.81 1.29
Maximum Latency (ms) 11.86 5.12
95th Percentile Latency (ms) 1.93 1.47

MySQL Write-only

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Transactions per second 5,084.00 5,729.00
Queries per second 50,840.00 57,290.00
Minimum Latency (ms) 1.45 1.16
Average Latency (ms) 1.96 1.74
Maximum Latency (ms) 10.63 19.56
95th Percentile Latency (ms) 2.61 2.3

MySQL Read/Write

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Transactions per second 2,327.00 2,905.00
Queries per second 23,270.00 29,050.00
Minimum Latency (ms) 3.56 2.54
Average Latency (ms) 4.3 3.44
Maximum Latency (ms) 11.69 9.03
95th Percentile Latency (ms) 5.09 4.25

MySQL INSERT

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Transactions per second 9,678.00 8,887.00
Queries per second 96,780.00 88,870.00
Minimum Latency (ms) 0.71 0.67
Average Latency (ms) 1.03 1.12
Maximum Latency (ms) 5.87 6.15
95th Percentile Latency (ms) 1.27 1.42

MySQL Bulk INSERT

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Transactions per second 964,103.00 1,608,842.00
Queries per second 9,641,030.00 16,088,420.00
Minimum Latency (ms) 0 0
Average Latency (ms) 0.01 0.01
Maximum Latency (ms) 555.35 340.01
95th Percentile Latency (ms) 0 0

MySQL SELECT

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Transactions per second 123,440.00 165,329.00
Queries per second 1,234,400.00 1,653,290.00
Minimum Latency (ms) 0.07 0.05
Average Latency (ms) 0.08 0.06
Maximum Latency (ms) 6.36 10.74
95th Percentile Latency (ms) 0.1 0.08

MySQL SELECT (Random Points)

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Transactions per second 5,660.00 9,736.00
Queries per second 56,600.00 97,360.00
Minimum Latency (ms) 0.7 0.37
Average Latency (ms) 1.77 1.03
Maximum Latency (ms) 5.62 4.34
95th Percentile Latency (ms) 2.3 1.32

MySQL SELECT (Random Ranges)

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Transactions per second 5,897.00 9,526.00
Queries per second 58,970.00 95,260.00
Minimum Latency (ms) 0.59 0.39
Average Latency (ms) 1.69 1.05
Maximum Latency (ms) 5.37 5.19
95th Percentile Latency (ms) 2.22 1.34

MySQL UPDATE (Indexed)

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Transactions per second 8,813.00 8,339.00
Queries per second 88,130.00 83,390.00
Minimum Latency (ms) 0.72 0.7
Average Latency (ms) 1.13 1.2
Maximum Latency (ms) 6.19 5.67
95th Percentile Latency (ms) 1.61 1.58

MySQL UPDATE (Non-Indexed)

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Transactions per second 9,183.00 8,527.00
Queries per second 91,830.00 85,270.00
Minimum Latency (ms) 0.7 0.7
Average Latency (ms) 1.09 1.17
Maximum Latency (ms) 7.93 5.57
95th Percentile Latency (ms) 1.37 1.5

MySQL DELETE

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Transactions per second 60,278.00 80,676.00
Queries per second 602,780.00 806,760.00
Minimum Latency (ms) 0.07 0.05
Average Latency (ms) 0.16 0.12
Maximum Latency (ms) 12.23 10.37
95th Percentile Latency (ms) 0.95 0.34

Redis

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
PING_INLINE per Second 37,678.97 47,528.52
PING_MBULK per Second 37,467.22 48,332.53
SET per Second 36,469.73 46,882.33
GET per Second 38,022.81 47,483.38
INCR per Second 37,907.50 44,228.22
LPUSH per Second 30,238.89 47,058.82
RPUSH per Second 35,561.88 46,948.36
LPOP per Second 37,523.45 45,829.52
RPOP per Second 37,750.09 46,598.32
SADD per Second 37,678.97 46,926.32
HSET per Second 37,313.43 47,192.07
SPOP per Second 37,850.11 47,778.31
ZADD per Second 37,369.21 43,535.05
ZPOPMIN per Second 38,986.36 47,393.37
LRANGE_100 (first 100 elements) per Second 24,125.45 31,836.99
LRANGE_300 (first 300 elements) per Second 12,500.00 17,771.46
LRANGE_500 (first 500 elements) per Second 8,862.11 12,277.47
LRANGE_600 (first 600 elements) per Second 7,744.73 10,720.41
MSET (10 keys) per Second 34,554.25 43,290.04

Redis Average Latency (ms)

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
PING_INLINE0.880.73
PING_MBULK0.880.72
SET0.910.74
GET0.880.73
INCR0.880.77
LPUSH1.080.74
RPUSH0.940.73
LPOP0.900.75
RPOP0.890.75
SADD0.880.74
HSET0.900.74
SPOP0.880.73
ZADD0.900.80
ZPOPMIN0.870.73
LRANGE_100 (first 100 elements)1.411.10
LRANGE_300 (first 300 elements)2.741.99
LRANGE_500 (first 500 elements)3.902.80
LRANGE_600 (first 600 elements)4.413.21
MSET (10 keys)1.020.81

Conclusion

From the friendly robots:

After analyzing the benchmark results for both Linode's Nanode (1 GB) and Vultr's Cloud Compute (1 GB), it's clear that Linode's instance excels in Redis operations, achieving higher requests per second and lower latencies across various commands, which indicates superior performance for memory-intensive tasks. Vultr's instance, while competitive, lags slightly behind in Redis benchmarks but performs comparably in CPU and file I/O operations. Linode's instance also shows better thread fairness and lower latency in MySQL operations, making it a better choice for applications requiring high throughput and low latency, such as real-time data processing or high-frequency trading systems. Conversely, Vultr's instance, with its competitive CPU and file I/O performance, might be better suited for workloads that are more CPU-bound or require substantial disk I/O operations, such as batch processing or large-scale data analytics.

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.