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

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Last Benchmarked Wed, 10 Jun 2026 21:00:52 GMT Tue, 09 Jun 2026 16: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-124-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

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,400.00
CPU Cache Size (KB) 512.00 16,384.00
BogoMips 4,000.00 4,799.99
Events per Second 1,605.64 818.79
Minimum Latency (ms) 0.28 1.02
Average Latency (ms) 0.61 1.22
Maximum Latency (ms) 15.02 4.29
95th Percentile Latency (ms) 2.86 1.37

Memory

Memory Read

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

Memory Write

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

File I/O

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

Mutex

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

MySQL

MySQL Read-only

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

MySQL Write-only

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

MySQL Read/Write

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

MySQL INSERT

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

MySQL Bulk INSERT

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

MySQL SELECT

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

MySQL SELECT (Random Points)

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

MySQL SELECT (Random Ranges)

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

MySQL UPDATE (Indexed)

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

MySQL UPDATE (Non-Indexed)

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

MySQL DELETE

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

Redis

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

Redis Average Latency (ms)

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
PING_INLINE0.880.96
PING_MBULK0.880.93
SET0.890.96
GET0.870.94
INCR0.870.97
LPUSH0.880.98
RPUSH0.900.95
LPOP0.921.03
RPOP0.940.99
SADD0.880.97
HSET0.880.98
SPOP0.870.94
ZADD0.871.01
ZPOPMIN0.880.99
LRANGE_100 (first 100 elements)1.251.50
LRANGE_300 (first 300 elements)2.182.81
LRANGE_500 (first 500 elements)2.954.10
LRANGE_600 (first 600 elements)3.394.58
MSET (10 keys)0.961.10

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.