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

Fresh benchmarks coming at ya. Today I've spun up some brand new instance from Linode and Vultr to run some benchmarks on. All instances were spun up with Ubuntu 24.04 LTS x64 and were created in the New York area (or close to it). Time to see who showed up today.

Overview

	Vultr – Cloud Compute (1 GB)	Linode – Nanode (1 GB)
Last Benchmarked	Tue, 28 Oct 2025 11:00:51 GMT	Wed, 29 Oct 2025 11:00:52 GMT
Linux Distro	Ubuntu 24.04 LTS x64	Ubuntu 24.04 LTS x64
Kernel Version	6.8.0-79-generic	6.8.0-71-generic
MySQL Version	8.0.43-0ubuntu0.24.04.2	8.0.43-0ubuntu0.24.04.2
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 7601 32-Core Processor
Clock Speed (MHz)	2,394.45	2,200.00
CPU Cache Size (KB)	16,384.00	512.00
BogoMips	4,788.90	4,399.99
Events per Second	615.53	626.39
Minimum Latency (ms)	0.88	0.67
Average Latency (ms)	1.62	1.6
Maximum Latency (ms)	5.49	8.53
95th Percentile Latency (ms)	2.61	4.25

Memory Read

	Vultr – Cloud Compute (1 GB)	Linode – Nanode (1 GB)
Operations per second	3,650,861.12	1,992,468.11
Mebibytes per second	3,565.29	1,945.77
Minimum Latency (ms)	0	0
Average Latency (ms)	0	0
Maximum Latency (ms)	0.86	4.79
95th Percentile Latency (ms)	0	0

Memory Write

	Vultr – Cloud Compute (1 GB)	Linode – Nanode (1 GB)
Operations per second	3,964,071.36	2,048,078.98
Mebibytes per second	3,871.16	2,000.08
Minimum Latency (ms)	0	0
Average Latency (ms)	0	0
Maximum Latency (ms)	0.65	7.36
95th Percentile Latency (ms)	0	0

File I/O

	Vultr – Cloud Compute (1 GB)	Linode – Nanode (1 GB)
Reads per Second	1,335.03	1,569.23
Writes per Second	890.02	1,046.16
Fsyncs per Second	2,849.25	3,352.99
Read Mebibytes per Second	20.86	24.52
Written Mebibytes per Second	13.91	16.35
Minimum Latency (ms)	0.01	0
Average Latency (ms)	0.2	0.17
Maximum Latency (ms)	12	6.62
95th Percentile Latency (ms)	0.51	0.4

Mutex

	Vultr – Cloud Compute (1 GB)	Linode – Nanode (1 GB)
Minimum Latency (ms)	2,016.43	2,118.43
Average Latency (ms)	2,026.59	2,136.64
Maximum Latency (ms)	2,036.58	2,147.24
95th Percentile Latency (ms)	2,045.74	2,159.29

MySQL Read-only

	Vultr – Cloud Compute (1 GB)	Linode – Nanode (1 GB)
Transactions per second	4,681.00	4,513.00
Queries per second	46,810.00	45,130.00
Minimum Latency (ms)	1.57	1.69
Average Latency (ms)	2.13	2.21
Maximum Latency (ms)	22.59	14.39
95th Percentile Latency (ms)	3.75	2.48

MySQL Write-only

	Vultr – Cloud Compute (1 GB)	Linode – Nanode (1 GB)
Transactions per second	2,680.00	3,583.00
Queries per second	26,800.00	35,830.00
Minimum Latency (ms)	1.66	1.87
Average Latency (ms)	3.73	2.79
Maximum Latency (ms)	34.94	27.89
95th Percentile Latency (ms)	6.67	4.03

MySQL Read/Write

	Vultr – Cloud Compute (1 GB)	Linode – Nanode (1 GB)
Transactions per second	1,752.00	1,726.00
Queries per second	17,520.00	17,260.00
Minimum Latency (ms)	4.22	4.55
Average Latency (ms)	5.71	5.8
Maximum Latency (ms)	16.45	20.42
95th Percentile Latency (ms)	8.28	7.04

MySQL INSERT

	Vultr – Cloud Compute (1 GB)	Linode – Nanode (1 GB)
Transactions per second	4,351.00	6,224.00
Queries per second	43,510.00	62,240.00
Minimum Latency (ms)	1.34	1.13
Average Latency (ms)	2.29	1.6
Maximum Latency (ms)	26.21	9.35
95th Percentile Latency (ms)	3.36	2.03

MySQL Bulk INSERT

	Vultr – Cloud Compute (1 GB)	Linode – Nanode (1 GB)
Transactions per second	865,805.00	734,741.00
Queries per second	8,658,050.00	7,347,410.00
Minimum Latency (ms)	0	0
Average Latency (ms)	0.01	0.01
Maximum Latency (ms)	955.84	693.48
95th Percentile Latency (ms)	0	0

MySQL SELECT

	Vultr – Cloud Compute (1 GB)	Linode – Nanode (1 GB)
Transactions per second	105,481.00	96,019.00
Queries per second	1,054,810.00	960,190.00
Minimum Latency (ms)	0.06	0.07
Average Latency (ms)	0.09	0.1
Maximum Latency (ms)	9.22	4.17
95th Percentile Latency (ms)	0.16	0.14

MySQL SELECT (Random Points)

	Vultr – Cloud Compute (1 GB)	Linode – Nanode (1 GB)
Transactions per second	3,665.00	5,082.00
Queries per second	36,650.00	50,820.00
Minimum Latency (ms)	0.5	0.71
Average Latency (ms)	2.73	1.97
Maximum Latency (ms)	13.84	13.24
95th Percentile Latency (ms)	5	2.61

MySQL SELECT (Random Ranges)

	Vultr – Cloud Compute (1 GB)	Linode – Nanode (1 GB)
Transactions per second	5,236.00	5,444.00
Queries per second	52,360.00	54,440.00
Minimum Latency (ms)	0.72	0.49
Average Latency (ms)	1.91	1.84
Maximum Latency (ms)	10.33	7.22
95th Percentile Latency (ms)	2.76	2.57

MySQL UPDATE (Indexed)

	Vultr – Cloud Compute (1 GB)	Linode – Nanode (1 GB)
Transactions per second	4,511.00	5,363.00
Queries per second	45,110.00	53,630.00
Minimum Latency (ms)	1.26	1.08
Average Latency (ms)	2.21	1.86
Maximum Latency (ms)	14.93	7.65
95th Percentile Latency (ms)	3.55	2.86

MySQL UPDATE (Non-Indexed)

	Vultr – Cloud Compute (1 GB)	Linode – Nanode (1 GB)
Transactions per second	5,148.00	6,025.00
Queries per second	51,480.00	60,250.00
Minimum Latency (ms)	1.25	1.23
Average Latency (ms)	1.94	1.66
Maximum Latency (ms)	19.95	7.39
95th Percentile Latency (ms)	2.81	2.22

MySQL DELETE

	Vultr – Cloud Compute (1 GB)	Linode – Nanode (1 GB)
Transactions per second	19,636.00	32,847.00
Queries per second	196,360.00	328,470.00
Minimum Latency (ms)	0.08	0.07
Average Latency (ms)	0.51	0.3
Maximum Latency (ms)	33.94	13.38
95th Percentile Latency (ms)	2.48	1.64

Redis

	Vultr – Cloud Compute (1 GB)	Linode – Nanode (1 GB)
PING_INLINE per Second	34,270.05	31,162.36
PING_MBULK per Second	34,638.03	32,414.91
SET per Second	35,211.27	32,488.63
GET per Second	34,977.27	31,979.53
INCR per Second	34,965.04	32,082.13
LPUSH per Second	36,443.15	31,847.13
RPUSH per Second	33,898.30	32,195.75
LPOP per Second	35,855.14	31,959.09
RPOP per Second	34,831.07	31,426.78
SADD per Second	35,829.45	32,030.75
HSET per Second	34,977.27	31,585.60
SPOP per Second	34,423.41	32,123.36
ZADD per Second	35,174.11	31,347.96
ZPOPMIN per Second	35,410.77	32,061.56
LRANGE_100 (first 100 elements) per Second	23,364.48	19,459.04
LRANGE_300 (first 300 elements) per Second	12,325.90	10,030.09
LRANGE_500 (first 500 elements) per Second	8,369.60	6,825.94
LRANGE_600 (first 600 elements) per Second	7,555.15	5,909.47
MSET (10 keys) per Second	33,123.55	29,931.16

Redis Average Latency (ms)

	Vultr – Cloud Compute (1 GB)	Linode – Nanode (1 GB)
PING_INLINE	0.96	1.05
PING_MBULK	0.92	1.00
SET	0.93	1.02
GET	0.94	1.02
INCR	0.92	1.02
LPUSH	0.92	1.03
RPUSH	0.95	1.02
LPOP	0.93	1.04
RPOP	0.93	1.05
SADD	0.92	1.02
HSET	0.93	1.04
SPOP	0.94	1.01
ZADD	0.93	1.05
ZPOPMIN	0.92	1.01
LRANGE_100 (first 100 elements)	1.43	1.70
LRANGE_300 (first 300 elements)	2.77	3.22
LRANGE_500 (first 500 elements)	4.07	4.67
LRANGE_600 (first 600 elements)	4.48	5.25
MSET (10 keys)	1.03	1.16

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 Vultr's instance outperforms Linode's in most metrics, particularly in Redis operations where it achieves higher requests per second and lower latencies across various commands. Vultr's CPU also shows better performance with slightly higher BogoMIPS and a more substantial cache. However, Linode's instance excels in handling file I/O operations, with higher throughput and lower latency. For workloads that prioritize high Redis performance and CPU efficiency, Vultr's Cloud Compute (1 GB) is the better choice, while Linode's Nanode (1 GB) is more suitable for tasks that demand superior file I/O performance.

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.