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

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Last Benchmarked Sat, 23 May 2026 13:00:52 GMT Thu, 21 May 2026 23:00:52 GMT
Linux Distro Ubuntu 24.04 LTS x64 Ubuntu 24.04 LTS x64
Kernel Version 6.8.0-111-generic 6.8.0-117-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

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Vendor AuthenticAMD GenuineIntel
Model Name AMD EPYC 7642 48-Core Processor Intel Core Processor (Broadwell, no TSX, IBRS)
Clock Speed (MHz) 2,300.00 2,394.45
CPU Cache Size (KB) 512.00 16,384.00
BogoMips 4,600.00 4,788.90
Events per Second 905.04 859.04
Minimum Latency (ms) 0.61 1.14
Average Latency (ms) 1.1 1.16
Maximum Latency (ms) 22.05 2.42
95th Percentile Latency (ms) 2.48 1.25

Memory

Memory Read

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

Memory Write

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

File I/O

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

Mutex

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

MySQL

MySQL Read-only

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

MySQL Write-only

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

MySQL Read/Write

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

MySQL INSERT

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

MySQL Bulk INSERT

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

MySQL SELECT

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

MySQL SELECT (Random Points)

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

MySQL SELECT (Random Ranges)

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

MySQL UPDATE (Indexed)

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

MySQL UPDATE (Non-Indexed)

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

MySQL DELETE

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

Redis

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

Redis Average Latency (ms)

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
PING_INLINE0.870.89
PING_MBULK0.860.88
SET0.870.90
GET0.870.89
INCR0.860.89
LPUSH0.860.91
RPUSH0.880.89
LPOP0.880.91
RPOP0.880.90
SADD0.880.88
HSET0.910.89
SPOP0.860.87
ZADD0.880.90
ZPOPMIN0.850.96
LRANGE_100 (first 100 elements)1.301.40
LRANGE_300 (first 300 elements)2.482.57
LRANGE_500 (first 500 elements)3.573.74
LRANGE_600 (first 600 elements)4.124.36
MSET (10 keys)1.021.09

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.