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

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Last Benchmarked Mon, 25 Aug 2025 13:00:52 GMT Tue, 26 Aug 2025 17:00:52 GMT
Linux Distro Ubuntu 24.04 LTS x64 Ubuntu 24.04 LTS x64
Kernel Version 6.8.0-71-generic 6.8.0-60-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

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Vendor AuthenticAMD GenuineIntel
Model Name AMD EPYC 7713 64-Core Processor Intel Core Processor (Broadwell, no TSX, IBRS)
Clock Speed (MHz) 2,000.00 2,394.45
CPU Cache Size (KB) 512.00 16,384.00
BogoMips 4,000.00 4,788.90
Events per Second 1,709.10 861.36
Minimum Latency (ms) 0.28 1.14
Average Latency (ms) 0.58 1.16
Maximum Latency (ms) 3.53 2.77
95th Percentile Latency (ms) 2.03 1.21

Memory

Memory Read

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

Memory Write

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

File I/O

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

Mutex

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

MySQL

MySQL Read-only

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

MySQL Write-only

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

MySQL Read/Write

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

MySQL INSERT

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

MySQL Bulk INSERT

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

MySQL SELECT

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

MySQL SELECT (Random Points)

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

MySQL SELECT (Random Ranges)

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

MySQL UPDATE (Indexed)

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

MySQL UPDATE (Non-Indexed)

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

MySQL DELETE

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

Redis

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

Redis Average Latency (ms)

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
PING_INLINE0.730.88
PING_MBULK0.720.88
SET0.740.91
GET0.730.88
INCR0.770.88
LPUSH0.741.08
RPUSH0.730.94
LPOP0.750.90
RPOP0.750.89
SADD0.740.88
HSET0.740.90
SPOP0.730.88
ZADD0.800.90
ZPOPMIN0.730.87
LRANGE_100 (first 100 elements)1.101.41
LRANGE_300 (first 300 elements)1.992.74
LRANGE_500 (first 500 elements)2.803.90
LRANGE_600 (first 600 elements)3.214.41
MSET (10 keys)0.811.02

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.