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

vs.

New day, new benchmarks. Today I've spun up brand new instance from Linode and Vultr and ran some benchmarks. 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, 09 Jun 2026 16:00:52 GMT Wed, 10 Jun 2026 21:00:52 GMT
Linux Distro Ubuntu 24.04 LTS x64 Ubuntu 24.04 LTS x64
Kernel Version 6.8.0-124-generic 6.8.0-111-generic
MySQL Version 8.0.46-0ubuntu0.24.04.2 8.0.46-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 7713 64-Core Processor
Clock Speed (MHz) 2,400.00 2,000.00
CPU Cache Size (KB) 16,384.00 512.00
BogoMips 4,799.99 4,000.00
Events per Second 818.79 1,605.64
Minimum Latency (ms) 1.02 0.28
Average Latency (ms) 1.22 0.61
Maximum Latency (ms) 4.29 15.02
95th Percentile Latency (ms) 1.37 2.86

Memory

Memory Read

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Operations per second 4,016,644.99 2,578,716.87
Mebibytes per second 3,922.50 2,518.28
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 0.24 8.61
95th Percentile Latency (ms) 0 0

Memory Write

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Operations per second 3,983,147.38 5,134,212.89
Mebibytes per second 3,889.79 5,013.88
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 0.35 7.28
95th Percentile Latency (ms) 0 0

File I/O

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Reads per Second 2,012.81 2,103.79
Writes per Second 1,341.84 1,402.53
Fsyncs per Second 4,294.21 4,497.88
Read Mebibytes per Second 31.45 32.87
Written Mebibytes per Second 20.97 21.91
Minimum Latency (ms) 0 0
Average Latency (ms) 0.13 0.12
Maximum Latency (ms) 5.76 9.57
95th Percentile Latency (ms) 0.35 0.3

Mutex

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Minimum Latency (ms) 2,100.95 2,611.09
Average Latency (ms) 2,112.04 2,623.26
Maximum Latency (ms) 2,121.79 2,632.60
95th Percentile Latency (ms) 2,120.76 2,632.28

MySQL

MySQL Read-only

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Transactions per second 5,273.00 7,182.00
Queries per second 52,730.00 71,820.00
Minimum Latency (ms) 1.65 1.22
Average Latency (ms) 1.89 1.39
Maximum Latency (ms) 13.42 8.56
95th Percentile Latency (ms) 2.07 1.64

MySQL Write-only

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Transactions per second 3,981.00 5,215.00
Queries per second 39,810.00 52,150.00
Minimum Latency (ms) 1.77 1.25
Average Latency (ms) 2.51 1.91
Maximum Latency (ms) 128.86 9.94
95th Percentile Latency (ms) 3.3 2.71

MySQL Read/Write

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Transactions per second 2,042.00 2,358.00
Queries per second 20,420.00 23,580.00
Minimum Latency (ms) 3.94 2.86
Average Latency (ms) 4.89 4.24
Maximum Latency (ms) 58.24 16.4
95th Percentile Latency (ms) 5.88 6.91

MySQL INSERT

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Transactions per second 5,470.00 7,570.00
Queries per second 54,700.00 75,700.00
Minimum Latency (ms) 1.13 0.75
Average Latency (ms) 1.83 1.32
Maximum Latency (ms) 111.33 11.85
95th Percentile Latency (ms) 3.13 1.89

MySQL Bulk INSERT

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Transactions per second 996,869.00 1,201,092.00
Queries per second 9,968,690.00 12,010,920.00
Minimum Latency (ms) 0 0
Average Latency (ms) 0.01 0.01
Maximum Latency (ms) 648.81 577.85
95th Percentile Latency (ms) 0 0

MySQL SELECT

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Transactions per second 112,678.00 152,163.00
Queries per second 1,126,780.00 1,521,630.00
Minimum Latency (ms) 0.06 0.05
Average Latency (ms) 0.09 0.07
Maximum Latency (ms) 8.37 7.75
95th Percentile Latency (ms) 0.13 0.09

MySQL SELECT (Random Points)

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Transactions per second 4,976.00 9,119.00
Queries per second 49,760.00 91,190.00
Minimum Latency (ms) 0.83 0.37
Average Latency (ms) 2.01 1.09
Maximum Latency (ms) 8.19 6.43
95th Percentile Latency (ms) 3.02 1.44

MySQL SELECT (Random Ranges)

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Transactions per second 5,987.00 8,501.00
Queries per second 59,870.00 85,010.00
Minimum Latency (ms) 0.54 0.35
Average Latency (ms) 1.67 1.17
Maximum Latency (ms) 10.51 8.45
95th Percentile Latency (ms) 2.18 2.22

MySQL UPDATE (Indexed)

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Transactions per second 5,883.00 7,551.00
Queries per second 58,830.00 75,510.00
Minimum Latency (ms) 0.98 0.7
Average Latency (ms) 1.7 1.32
Maximum Latency (ms) 4.44 10.76
95th Percentile Latency (ms) 2.26 2

MySQL UPDATE (Non-Indexed)

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Transactions per second 6,195.00 7,901.00
Queries per second 61,950.00 79,010.00
Minimum Latency (ms) 1.18 0.7
Average Latency (ms) 1.61 1.26
Maximum Latency (ms) 30.16 10.46
95th Percentile Latency (ms) 2.11 1.79

MySQL DELETE

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
Transactions per second 23,800.00 60,656.00
Queries per second 238,000.00 606,560.00
Minimum Latency (ms) 0.06 0.05
Average Latency (ms) 0.42 0.16
Maximum Latency (ms) 2553.92 11.78
95th Percentile Latency (ms) 1.7 1.12

Redis

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
PING_INLINE per Second 34,129.69 37,467.22
PING_MBULK per Second 35,248.50 37,664.79
SET per Second 34,352.46 37,160.91
GET per Second 34,806.82 37,608.12
INCR per Second 34,199.73 37,271.71
LPUSH per Second 33,840.95 37,037.04
RPUSH per Second 34,698.12 35,997.12
LPOP per Second 32,041.01 35,511.36
RPOP per Second 33,400.13 34,542.32
SADD per Second 33,568.31 36,913.99
HSET per Second 33,489.62 37,230.08
SPOP per Second 34,855.35 37,821.48
ZADD per Second 32,658.39 37,936.27
ZPOPMIN per Second 33,134.53 37,551.63
LRANGE_100 (first 100 elements) per Second 22,158.21 26,910.66
LRANGE_300 (first 300 elements) per Second 12,084.59 15,573.90
LRANGE_500 (first 500 elements) per Second 8,313.93 11,301.99
LRANGE_600 (first 600 elements) per Second 7,367.57 9,987.02
MSET (10 keys) per Second 30,807.15 34,867.50

Redis Average Latency (ms)

Vultr – Cloud Compute (1 GB) Linode – Nanode (1 GB)
PING_INLINE0.960.88
PING_MBULK0.930.88
SET0.960.89
GET0.940.87
INCR0.970.87
LPUSH0.980.88
RPUSH0.950.90
LPOP1.030.92
RPOP0.990.94
SADD0.970.88
HSET0.980.88
SPOP0.940.87
ZADD1.010.87
ZPOPMIN0.990.88
LRANGE_100 (first 100 elements)1.501.25
LRANGE_300 (first 300 elements)2.812.18
LRANGE_500 (first 500 elements)4.102.95
LRANGE_600 (first 600 elements)4.583.39
MSET (10 keys)1.100.96

Conclusion

From the friendly robots:

Upon comparing the benchmark performance of Linode's Nanode (1 GB) and Vultr's Cloud Compute (1 GB), it is evident that both instances exhibit comparable capabilities in terms of CPU, memory, and file I/O operations, but there are noticeable differences in Redis benchmarks and MySQL workloads. The Linode instance demonstrates slightly better performance in Redis benchmarks with higher requests per second (rps) and lower latencies, particularly in commands like LRANGE and MSET. Meanwhile, Vultr's instance shows more robust performance in MySQL bulk inserts and OLTP operations, suggesting it might be better suited for database-heavy workloads. Overall, Linode's instance appears marginally superior in memory-intensive and Redis operations, making it ideal for applications that benefit from such performance characteristics, while Vultr's instance would be more advantageous for databases and CPU-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.