Linode Nanode (1 GB) vs. Vultr Cloud Compute (2 GB, 2 Cores)
Same showdown, different day. Today I've spun up some brand new instance from Linode and Vultr and did some benchmarking. All instances were running Ubuntu 24.04 LTS x64 and were created in or around the New York / New Jersey area. Without further ado, here's the results.
Overview
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Last Benchmarked | Mon, 11 May 2026 08:00:52 GMT | Mon, 11 May 2026 04: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-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 | $15.00 |
| RAM (GB) | 1 | 2 |
| CPU Cores | 1 | 2 |
| Storage (TB) | 25 | 65 |
| Storage Type | SSD | SSD |
| Transfer (TB) | 1 | 3 |
CPU
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Vendor | AuthenticAMD | GenuineIntel |
| Model Name | AMD EPYC 7642 48-Core Processor | Intel Core Processor (Skylake, IBRS, no TSX) |
| Clock Speed (MHz) | 2,300.00 | 3,792.00 |
| CPU Cache Size (KB) | 512.00 | 16,384.00 |
| BogoMips | 4,599.99 | 7,583.99 |
| Events per Second | 775.25 | 1,481.60 |
| Minimum Latency (ms) | 0.6 | 0.63 |
| Average Latency (ms) | 1.27 | 0.67 |
| Maximum Latency (ms) | 13.19 | 1.95 |
| 95th Percentile Latency (ms) | 2.43 | 0.77 |
Memory
Memory Read
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 4,816,011.71 | 6,401,389.08 |
| Mebibytes per second | 4,703.14 | 6,251.36 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 2.65 | 0.23 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 5,028,052.52 | 6,411,085.35 |
| Mebibytes per second | 4,910.21 | 6,260.83 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.65 | 0.18 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Reads per Second | 1,745.08 | 4,345.71 |
| Writes per Second | 1,163.32 | 2,897.07 |
| Fsyncs per Second | 3,734.14 | 9,273.19 |
| Read Mebibytes per Second | 27.27 | 67.90 |
| Written Mebibytes per Second | 18.18 | 45.27 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.15 | 0.06 |
| Maximum Latency (ms) | 111.66 | 2.92 |
| 95th Percentile Latency (ms) | 0.42 | 0.17 |
Mutex
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 1,765.15 | 214.63 |
| Average Latency (ms) | 1,776.48 | 569.72 |
| Maximum Latency (ms) | 1,784.54 | 636.55 |
| 95th Percentile Latency (ms) | 1,771.29 | 634.66 |
MySQL
MySQL Read-only
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 6,475.00 | 8,015.00 |
| Queries per second | 64,750.00 | 80,150.00 |
| Minimum Latency (ms) | 1.35 | 0.92 |
| Average Latency (ms) | 1.54 | 1.25 |
| Maximum Latency (ms) | 16.82 | 5.5 |
| 95th Percentile Latency (ms) | 1.89 | 1.86 |
MySQL Write-only
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 4,612.00 | 8,497.00 |
| Queries per second | 46,120.00 | 84,970.00 |
| Minimum Latency (ms) | 1.31 | 0.76 |
| Average Latency (ms) | 2.17 | 1.17 |
| Maximum Latency (ms) | 25.08 | 3.04 |
| 95th Percentile Latency (ms) | 3.25 | 1.55 |
MySQL Read/Write
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 2,257.00 | 3,726.00 |
| Queries per second | 22,570.00 | 37,260.00 |
| Minimum Latency (ms) | 2.94 | 1.78 |
| Average Latency (ms) | 4.43 | 2.68 |
| Maximum Latency (ms) | 284.62 | 5.82 |
| 95th Percentile Latency (ms) | 5.57 | 3.43 |
MySQL INSERT
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,257.00 | 15,028.00 |
| Queries per second | 82,570.00 | 150,280.00 |
| Minimum Latency (ms) | 0.68 | 0.41 |
| Average Latency (ms) | 1.21 | 0.66 |
| Maximum Latency (ms) | 18.06 | 2.42 |
| 95th Percentile Latency (ms) | 1.64 | 0.86 |
MySQL Bulk INSERT
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 996,869.00 | 1,696,217.00 |
| Queries per second | 9,968,690.00 | 16,962,170.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0.01 |
| Maximum Latency (ms) | 636.05 | 283.37 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 131,656.00 | 201,989.00 |
| Queries per second | 1,316,560.00 | 2,019,890.00 |
| Minimum Latency (ms) | 0.05 | 0.03 |
| Average Latency (ms) | 0.08 | 0.05 |
| Maximum Latency (ms) | 16.69 | 0.51 |
| 95th Percentile Latency (ms) | 0.11 | 0.07 |
MySQL SELECT (Random Points)
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 6,583.00 | 8,025.00 |
| Queries per second | 65,830.00 | 80,250.00 |
| Minimum Latency (ms) | 0.58 | 0.35 |
| Average Latency (ms) | 1.52 | 1.24 |
| Maximum Latency (ms) | 10.35 | 3.55 |
| 95th Percentile Latency (ms) | 2.14 | 2.07 |
MySQL SELECT (Random Ranges)
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 6,958.00 | 8,336.00 |
| Queries per second | 69,580.00 | 83,360.00 |
| Minimum Latency (ms) | 0.52 | 0.4 |
| Average Latency (ms) | 1.44 | 1.2 |
| Maximum Latency (ms) | 10.88 | 4.25 |
| 95th Percentile Latency (ms) | 1.96 | 2.22 |
MySQL UPDATE (Indexed)
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 7,379.00 | 13,858.00 |
| Queries per second | 73,790.00 | 138,580.00 |
| Minimum Latency (ms) | 0.72 | 0.42 |
| Average Latency (ms) | 1.35 | 0.72 |
| Maximum Latency (ms) | 54.41 | 6.33 |
| 95th Percentile Latency (ms) | 2.03 | 0.95 |
MySQL UPDATE (Non-Indexed)
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 7,578.00 | 14,587.00 |
| Queries per second | 75,780.00 | 145,870.00 |
| Minimum Latency (ms) | 0.73 | 0.4 |
| Average Latency (ms) | 1.32 | 0.68 |
| Maximum Latency (ms) | 163.64 | 11.69 |
| 95th Percentile Latency (ms) | 1.86 | 0.9 |
MySQL DELETE
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 56,096.00 | 129,013.00 |
| Queries per second | 560,960.00 | 1,290,130.00 |
| Minimum Latency (ms) | 0.05 | 0.03 |
| Average Latency (ms) | 0.18 | 0.08 |
| Maximum Latency (ms) | 15.75 | 2.61 |
| 95th Percentile Latency (ms) | 1.1 | 0.09 |
Redis
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE per Second | 38,037.28 | 78,247.26 |
| PING_MBULK per Second | 39,077.77 | 74,738.41 |
| SET per Second | 38,520.80 | 77,041.60 |
| GET per Second | 39,888.31 | 83,333.33 |
| INCR per Second | 35,663.34 | 80,971.66 |
| LPUSH per Second | 37,878.79 | 79,113.92 |
| RPUSH per Second | 38,446.75 | 77,160.49 |
| LPOP per Second | 38,138.82 | 81,499.59 |
| RPOP per Second | 38,314.18 | 82,440.23 |
| SADD per Second | 39,047.25 | 80,192.46 |
| HSET per Second | 37,664.79 | 83,612.04 |
| SPOP per Second | 39,169.61 | 85,034.02 |
| ZADD per Second | 38,328.86 | 83,263.95 |
| ZPOPMIN per Second | 38,284.84 | 82,987.55 |
| LRANGE_100 (first 100 elements) per Second | 25,886.62 | 55,555.56 |
| LRANGE_300 (first 300 elements) per Second | 14,273.48 | 28,851.70 |
| LRANGE_500 (first 500 elements) per Second | 10,143.02 | 19,391.12 |
| LRANGE_600 (first 600 elements) per Second | 8,834.70 | 17,211.71 |
| MSET (10 keys) per Second | 37,009.62 | 80,256.82 |
Redis Average Latency (ms)
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE | 0.90 | 0.34 |
| PING_MBULK | 0.86 | 0.35 |
| SET | 0.88 | 0.34 |
| GET | 0.84 | 0.32 |
| INCR | 0.96 | 0.32 |
| LPUSH | 0.90 | 0.34 |
| RPUSH | 0.89 | 0.34 |
| LPOP | 0.90 | 0.32 |
| RPOP | 0.89 | 0.32 |
| SADD | 0.86 | 0.32 |
| HSET | 0.88 | 0.31 |
| SPOP | 0.85 | 0.30 |
| ZADD | 0.88 | 0.31 |
| ZPOPMIN | 0.89 | 0.31 |
| LRANGE_100 (first 100 elements) | 1.34 | 0.54 |
| LRANGE_300 (first 300 elements) | 2.54 | 1.11 |
| LRANGE_500 (first 500 elements) | 3.55 | 1.62 |
| LRANGE_600 (first 600 elements) | 4.07 | 1.84 |
| MSET (10 keys) | 0.95 | 0.38 |
Conclusion
From the friendly robots:
After analyzing the benchmark performance, the Vultr Cloud Compute instance shows higher overall throughput and better latency for most Redis operations, indicating it can handle higher request rates with lower average and peak latencies compared to the Linode Nanode instance. The Vultr instance also boasts superior CPU performance, with higher events per second and lower average latency, and provides better file I/O performance, with higher read and write throughput. However, the Linode instance shows better thread fairness and lower thread latencies. For CPU-intensive, I/O-heavy workloads, or applications that require high concurrency and throughput, the Vultr Cloud Compute instance is more suitable due to its better overall performance metrics. Meanwhile, the Linode Nanode instance might be more appropriate for less demanding tasks where lower cost and simpler setup are prioritized.
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.