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

vs.

New day, new benchmarks. Today I've spun up some brand new instance from Linode and Vultr to run some benchmarks on. Each instance was running Ubuntu 24.04 LTS x64 and all resided in or around the New York / New Jersey area. Without further ado, here's the results.

Overview

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Last Benchmarked Thu, 21 May 2026 23:00:52 GMT Sat, 23 May 2026 13:00:52 GMT
Linux Distro Ubuntu 24.04 LTS x64 Ubuntu 24.04 LTS x64
Kernel Version 6.8.0-117-generic 6.8.0-111-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 (Broadwell, no TSX, IBRS) AMD EPYC 7642 48-Core Processor
Clock Speed (MHz) 2,394.45 2,300.00
CPU Cache Size (KB) 16,384.00 512.00
BogoMips 4,788.90 4,600.00
Events per Second 859.04 905.04
Minimum Latency (ms) 1.14 0.61
Average Latency (ms) 1.16 1.1
Maximum Latency (ms) 2.42 22.05
95th Percentile Latency (ms) 1.25 2.48

Memory

Memory Read

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Operations per second 4,179,696.98 5,013,583.91
Mebibytes per second 4,081.74 4,896.08
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 0.23 9.43
95th Percentile Latency (ms) 0 0

Memory Write

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Operations per second 4,151,553.00 4,999,712.46
Mebibytes per second 4,054.25 4,882.53
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 0.59 9.49
95th Percentile Latency (ms) 0 0

File I/O

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Reads per Second 2,403.90 1,752.56
Writes per Second 1,602.60 1,168.34
Fsyncs per Second 5,132.41 3,745.40
Read Mebibytes per Second 37.56 27.38
Written Mebibytes per Second 25.04 18.26
Minimum Latency (ms) 0 0
Average Latency (ms) 0.11 0.15
Maximum Latency (ms) 3.04 75.52
95th Percentile Latency (ms) 0.32 0.42

Mutex

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Minimum Latency (ms) 2,066.64 1,654.93
Average Latency (ms) 2,071.43 1,667.46
Maximum Latency (ms) 2,075.26 1,678.80
95th Percentile Latency (ms) 2,082.91 1,678.14

MySQL

MySQL Read-only

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Transactions per second 5,409.00 6,108.00
Queries per second 54,090.00 61,080.00
Minimum Latency (ms) 1.74 1.43
Average Latency (ms) 1.85 1.64
Maximum Latency (ms) 13.71 22.63
95th Percentile Latency (ms) 2 2

MySQL Write-only

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Transactions per second 4,997.00 4,788.00
Queries per second 49,970.00 47,880.00
Minimum Latency (ms) 1.47 1.33
Average Latency (ms) 2 2.09
Maximum Latency (ms) 10.54 24.02
95th Percentile Latency (ms) 2.61 3.07

MySQL Read/Write

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Transactions per second 2,422.00 2,490.00
Queries per second 24,220.00 24,900.00
Minimum Latency (ms) 3.55 3.03
Average Latency (ms) 4.13 4.02
Maximum Latency (ms) 12.42 15.36
95th Percentile Latency (ms) 4.82 5.09

MySQL INSERT

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Transactions per second 9,166.00 8,775.00
Queries per second 91,660.00 87,750.00
Minimum Latency (ms) 0.71 0.68
Average Latency (ms) 1.09 1.14
Maximum Latency (ms) 6.03 20.34
95th Percentile Latency (ms) 1.39 1.47

MySQL Bulk INSERT

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Transactions per second 937,763.00 898,571.00
Queries per second 9,377,630.00 8,985,710.00
Minimum Latency (ms) 0 0
Average Latency (ms) 0.01 0.01
Maximum Latency (ms) 661.15 1312.33
95th Percentile Latency (ms) 0 0

MySQL SELECT

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Transactions per second 117,346.00 131,900.00
Queries per second 1,173,460.00 1,319,000.00
Minimum Latency (ms) 0.07 0.06
Average Latency (ms) 0.08 0.08
Maximum Latency (ms) 7.11 12.86
95th Percentile Latency (ms) 0.11 0.11

MySQL SELECT (Random Points)

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Transactions per second 5,731.00 6,799.00
Queries per second 57,310.00 67,990.00
Minimum Latency (ms) 0.62 0.48
Average Latency (ms) 1.74 1.47
Maximum Latency (ms) 6.81 12.9
95th Percentile Latency (ms) 2.18 2.03

MySQL SELECT (Random Ranges)

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Transactions per second 6,416.00 6,912.00
Queries per second 64,160.00 69,120.00
Minimum Latency (ms) 0.47 0.36
Average Latency (ms) 1.56 1.45
Maximum Latency (ms) 4.83 5.54
95th Percentile Latency (ms) 2 1.93

MySQL UPDATE (Indexed)

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Transactions per second 8,258.00 7,586.00
Queries per second 82,580.00 75,860.00
Minimum Latency (ms) 0.72 0.75
Average Latency (ms) 1.21 1.32
Maximum Latency (ms) 35.33 19.75
95th Percentile Latency (ms) 1.79 2

MySQL UPDATE (Non-Indexed)

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Transactions per second 8,930.00 7,848.00
Queries per second 89,300.00 78,480.00
Minimum Latency (ms) 0.71 0.7
Average Latency (ms) 1.12 1.27
Maximum Latency (ms) 20.29 23.83
95th Percentile Latency (ms) 1.39 1.82

MySQL DELETE

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Transactions per second 50,174.00 61,230.00
Queries per second 501,740.00 612,300.00
Minimum Latency (ms) 0.07 0.06
Average Latency (ms) 0.2 0.16
Maximum Latency (ms) 18.49 19.09
95th Percentile Latency (ms) 1.1 0.97

Redis

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
PING_INLINE per Second 36,643.46 38,804.81
PING_MBULK per Second 37,230.08 39,154.27
SET per Second 36,724.20 38,789.76
GET per Second 36,982.25 38,431.98
INCR per Second 36,941.26 38,971.16
LPUSH per Second 36,483.04 39,154.27
RPUSH per Second 37,091.99 38,505.97
LPOP per Second 36,643.46 38,476.34
RPOP per Second 36,764.71 38,925.65
SADD per Second 37,523.45 38,255.55
HSET per Second 36,995.93 36,737.70
SPOP per Second 37,565.74 38,925.65
ZADD per Second 37,009.62 38,580.25
ZPOPMIN per Second 34,916.20 39,603.96
LRANGE_100 (first 100 elements) per Second 23,557.13 26,602.82
LRANGE_300 (first 300 elements) per Second 12,960.08 14,660.61
LRANGE_500 (first 500 elements) per Second 9,176.00 10,073.54
LRANGE_600 (first 600 elements) per Second 7,776.65 8,647.53
MSET (10 keys) per Second 31,017.37 34,141.35

Redis Average Latency (ms)

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
PING_INLINE0.890.87
PING_MBULK0.880.86
SET0.900.87
GET0.890.87
INCR0.890.86
LPUSH0.910.86
RPUSH0.890.88
LPOP0.910.88
RPOP0.900.88
SADD0.880.88
HSET0.890.91
SPOP0.870.86
ZADD0.900.88
ZPOPMIN0.960.85
LRANGE_100 (first 100 elements)1.401.30
LRANGE_300 (first 300 elements)2.572.48
LRANGE_500 (first 500 elements)3.743.57
LRANGE_600 (first 600 elements)4.364.12
MSET (10 keys)1.091.02

Conclusion

From the friendly robots:

Both Linode's Nanode (1 GB) and Vultr's Cloud Compute (1 GB) instances exhibit similar benchmark results in terms of CPU, memory, and I/O performance, though Vultr's instance shows slightly higher read throughput and slightly lower Redis performance. Linode's instance shows better Redis read performance and generally higher Redis request rates, suggesting it may be slightly more performant for database-heavy tasks, whereas Vultr excels in file I/O operations with higher throughput, indicating it could be a better choice for I/O-heavy workloads. Given their nearly equivalent performance but slightly different strengths, the better choice depends on the specific use case, favoring Linode for Redis/database operations and Vultr for file-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.