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

vs.

Welcome to another round of the VPS Showdown. Today I spun up fresh instances from Linode and Vultr and ran my world famous suite of benchmarking scripts. Each instance was running Ubuntu 26.04 LTS x64 and were created in the New York area (or close to it). Enough talk. Here's the data.

Overview

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Last Benchmarked Sat, 01 Aug 2026 05:01:32 GMT Sat, 01 Aug 2026 05:03:02 GMT
Linux Distro Ubuntu 26.04 LTS x64 Ubuntu 26.04 LTS x64
Kernel Version 7.0.0-22-generic 7.0.0-28-generic
MySQL Version 8.4.10-0ubuntu0.26.04.1 8.4.10-0ubuntu0.26.04.1
Redis Version 8.0.5 8.0.5
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

Head-to-head

Category winners from the latest benchmarks.

CategoryWinner
CPU (events/sec)Linode – Nanode (1 GB)
Memory (read MiB/s)Linode – Nanode (1 GB)
Disk I/O (MiB/s)Linode – Nanode (1 GB)
MySQL (read/write tps)Linode – Nanode (1 GB)
Redis (GET/sec)Linode – Nanode (1 GB)
Value (CPU events per $/mo)Linode – Nanode (1 GB)

Linode – Nanode (1 GB) takes 6 of 6 categories.

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,400.00
CPU Cache Size (KB) 512.00 16,384.00
BogoMips 4,600.00 4,799.99
Events per Second 1,479.09 763.23
Minimum Latency (ms) 0.65 1.11
Average Latency (ms) 0.68 1.31
Maximum Latency (ms) 4.07 2.63
95th Percentile Latency (ms) 0.69 1.44

Memory

Memory Read

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Operations per second 5,162,780.30 3,905,870.09
Mebibytes per second 5,041.78 3,814.33
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 1.07 0.72
95th Percentile Latency (ms) 0 0

Memory Write

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Operations per second 5,347,459.67 3,886,921.83
Mebibytes per second 5,222.13 3,795.82
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 0.26 0.73
95th Percentile Latency (ms) 0 0

File I/O

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Reads per Second 2,518.00 1,890.03
Writes per Second 1,678.67 1,259.95
Fsyncs per Second 5,375.23 4,040.16
Read Mebibytes per Second 39.34 29.53
Written Mebibytes per Second 26.23 19.69
Minimum Latency (ms) 0 0
Average Latency (ms) 0.1 0.14
Maximum Latency (ms) 14.25 4.59
95th Percentile Latency (ms) 0.35 0.35

Mutex

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Minimum Latency (ms) 1,639.75 2,141.87
Average Latency (ms) 1,650.21 2,158.92
Maximum Latency (ms) 1,660.37 2,165.16
95th Percentile Latency (ms) 1,648.20 2,159.29

MySQL

MySQL Read-only

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Transactions per second 9,017.00 5,168.00
Queries per second 90,170.00 51,680.00
Minimum Latency (ms) 1.02 1.65
Average Latency (ms) 1.11 1.93
Maximum Latency (ms) 5.75 12.8
95th Percentile Latency (ms) 1.27 2.22

MySQL Write-only

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Transactions per second 8,101.00 3,072.00
Queries per second 81,010.00 30,720.00
Minimum Latency (ms) 0.87 1.58
Average Latency (ms) 1.23 3.71
Maximum Latency (ms) 11.04 3416.63
95th Percentile Latency (ms) 1.64 3.07

MySQL Read/Write

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Transactions per second 3,971.00 2,195.00
Queries per second 39,710.00 21,950.00
Minimum Latency (ms) 1.98 3.59
Average Latency (ms) 2.52 4.55
Maximum Latency (ms) 17.34 11.62
95th Percentile Latency (ms) 3.07 5.28

MySQL INSERT

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Transactions per second 12,157.00 6,793.00
Queries per second 121,570.00 67,930.00
Minimum Latency (ms) 0.58 1.03
Average Latency (ms) 0.82 1.47
Maximum Latency (ms) 13.14 42.94
95th Percentile Latency (ms) 1.12 1.89

MySQL Bulk INSERT

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Transactions per second 1,346,717.00 931,337.00
Queries per second 13,467,170.00 9,313,370.00
Minimum Latency (ms) 0 0
Average Latency (ms) 0.01 0.01
Maximum Latency (ms) 454.87 595.92
95th Percentile Latency (ms) 0 0

MySQL SELECT

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Transactions per second 211,595.00 112,159.00
Queries per second 2,115,950.00 1,121,590.00
Minimum Latency (ms) 0.04 0.07
Average Latency (ms) 0.05 0.09
Maximum Latency (ms) 3.28 3.1
95th Percentile Latency (ms) 0.06 0.13

MySQL SELECT (Random Points)

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Transactions per second 6,687.00 4,115.00
Queries per second 66,870.00 41,150.00
Minimum Latency (ms) 0.46 0.76
Average Latency (ms) 1.49 2.43
Maximum Latency (ms) 5 6.44
95th Percentile Latency (ms) 1.93 3.25

MySQL SELECT (Random Ranges)

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Transactions per second 7,633.00 5,698.00
Queries per second 76,330.00 56,980.00
Minimum Latency (ms) 0.46 0.65
Average Latency (ms) 1.31 1.75
Maximum Latency (ms) 3.52 5.36
95th Percentile Latency (ms) 1.73 2.35

MySQL UPDATE (Indexed)

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Transactions per second 12,921.00 6,594.00
Queries per second 129,210.00 65,940.00
Minimum Latency (ms) 0.6 1
Average Latency (ms) 0.77 1.51
Maximum Latency (ms) 10.21 26.54
95th Percentile Latency (ms) 0.99 2.07

MySQL UPDATE (Non-Indexed)

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Transactions per second 11,621.00 6,477.00
Queries per second 116,210.00 64,770.00
Minimum Latency (ms) 0.59 1.02
Average Latency (ms) 0.86 1.54
Maximum Latency (ms) 70.33 33.4
95th Percentile Latency (ms) 1.3 2.18

MySQL DELETE

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
Transactions per second 137,539.00 48,339.00
Queries per second 1,375,390.00 483,390.00
Minimum Latency (ms) 0.04 0.06
Average Latency (ms) 0.07 0.21
Maximum Latency (ms) 5.83 22.17
95th Percentile Latency (ms) 0.1 1.34

Redis

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
PING_INLINE per Second 85,324.23 33,288.95
PING_MBULK per Second 72,150.07 33,704.08
SET per Second 83,682.01 33,456.00
GET per Second 86,430.43 32,010.24
INCR per Second 85,984.52 30,147.72
LPUSH per Second 85,324.23 28,232.64
RPUSH per Second 85,543.20 32,552.08
LPOP per Second 85,034.02 32,414.91
RPOP per Second 84,961.77 32,195.75
SADD per Second 85,763.29 32,278.89
HSET per Second 84,961.77 32,776.14
SPOP per Second 85,984.52 30,147.72
ZADD per Second 85,106.38 25,412.96
ZPOPMIN per Second 86,580.09 25,920.17
LRANGE_100 (first 100 elements) per Second 44,782.80 19,098.55
LRANGE_300 (first 300 elements) per Second 21,213.41 11,506.16
LRANGE_500 (first 500 elements) per Second 14,192.45 7,970.67
LRANGE_600 (first 600 elements) per Second 11,773.02 7,017.05
MSET (10 keys) per Second 72,046.11 30,165.91

Redis Average Latency (ms)

Linode – Nanode (1 GB) Vultr – Cloud Compute (1 GB)
PING_INLINE0.370.92
PING_MBULK0.430.90
SET0.390.92
GET0.370.94
INCR0.371.01
LPUSH0.381.08
RPUSH0.380.94
LPOP0.380.95
RPOP0.380.96
SADD0.370.94
HSET0.380.93
SPOP0.371.01
ZADD0.381.21
ZPOPMIN0.371.16
LRANGE_100 (first 100 elements)0.801.65
LRANGE_300 (first 300 elements)1.612.64
LRANGE_500 (first 500 elements)2.493.64
LRANGE_600 (first 600 elements)2.964.12
MSET (10 keys)0.571.10

Conclusion

From the friendly robots:

The Linode Nanode (1 GB) instance outperforms the Vultr Cloud Compute (1 GB) instance in key benchmarks, especially in Redis performance with higher request per second (rps) rates and lower latencies, such as 85324.23 rps for PING_INLINE compared to Vultr's 33288.95 rps. The Linode also excels in CPU event processing, registering 1479.09 events per second versus Vultr's 763.23, demonstrating superior overall performance for CPU-intensive tasks. For users prioritizing high throughput and low latency, especially in database operations and general CPU-heavy applications, the Linode Nanode is the better choice.

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 next time you shop on Amazon.

Providers & pricing

Related comparisons