Linode Nanode (1 GB) vs. Vultr Cloud Compute (4 GB, 2 Cores)
Fresh benchmarks coming at ya. Today I've spun up brand new instance from Linode and Vultr and ran my world famous suite of benchmarking scripts. Each instance was spun up with Ubuntu 24.04 LTS x64 and all resided in or around the New York / New Jersey area. Time to see who showed up today.
Overview
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Last Benchmarked | Fri, 29 May 2026 15:00:53 GMT | Wed, 27 May 2026 00: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 | $20.00 |
| RAM (GB) | 1 | 4 |
| CPU Cores | 1 | 2 |
| Storage (TB) | 25 | 80 |
| Storage Type | SSD | SSD |
| Transfer (TB) | 1 | 3 |
CPU
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (4 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,791.94 |
| CPU Cache Size (KB) | 512.00 | 16,384.00 |
| BogoMips | 4,599.99 | 7,583.88 |
| Events per Second | 1,022.23 | 1,578.33 |
| Minimum Latency (ms) | 0.61 | 0.6 |
| Average Latency (ms) | 0.98 | 0.63 |
| Maximum Latency (ms) | 5.4 | 4.39 |
| 95th Percentile Latency (ms) | 2.39 | 0.67 |
Memory
Memory Read
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 5,296,233.64 | 7,833,140.58 |
| Mebibytes per second | 5,172.10 | 7,649.55 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 3.05 | 0.17 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 5,154,651.90 | 7,590,616.10 |
| Mebibytes per second | 5,033.84 | 7,412.71 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 3.06 | 0.31 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Reads per Second | 2,055.76 | 7,658.57 |
| Writes per Second | 1,370.51 | 5,105.71 |
| Fsyncs per Second | 4,389.22 | 16,348.88 |
| Read Mebibytes per Second | 32.12 | 119.67 |
| Written Mebibytes per Second | 21.41 | 79.78 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.13 | 0.03 |
| Maximum Latency (ms) | 12.79 | 1.98 |
| 95th Percentile Latency (ms) | 0.35 | 0.12 |
Mutex
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 1,633.32 | 490.41 |
| Average Latency (ms) | 1,644.62 | 555.46 |
| Maximum Latency (ms) | 1,653.29 | 582.61 |
| 95th Percentile Latency (ms) | 1,648.20 | 580.02 |
MySQL
MySQL Read-only
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 7,575.00 | 10,091.00 |
| Queries per second | 75,750.00 | 100,910.00 |
| Minimum Latency (ms) | 1.22 | 0.89 |
| Average Latency (ms) | 1.32 | 0.99 |
| Maximum Latency (ms) | 4.67 | 2.8 |
| 95th Percentile Latency (ms) | 1.42 | 1.12 |
MySQL Write-only
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 5,800.00 | 9,607.00 |
| Queries per second | 58,000.00 | 96,070.00 |
| Minimum Latency (ms) | 1.15 | 0.64 |
| Average Latency (ms) | 1.72 | 1.04 |
| Maximum Latency (ms) | 12.35 | 3.34 |
| 95th Percentile Latency (ms) | 2.39 | 1.37 |
MySQL Read/Write
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 2,955.00 | 4,308.00 |
| Queries per second | 29,550.00 | 43,080.00 |
| Minimum Latency (ms) | 2.64 | 1.68 |
| Average Latency (ms) | 3.38 | 2.32 |
| Maximum Latency (ms) | 22.69 | 14.87 |
| 95th Percentile Latency (ms) | 4.41 | 2.86 |
MySQL INSERT
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,921.00 | 15,519.00 |
| Queries per second | 89,210.00 | 155,190.00 |
| Minimum Latency (ms) | 0.65 | 0.38 |
| Average Latency (ms) | 1.12 | 0.64 |
| Maximum Latency (ms) | 8.92 | 9.21 |
| 95th Percentile Latency (ms) | 1.42 | 0.87 |
MySQL Bulk INSERT
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 1,288,467.00 | 2,016,592.00 |
| Queries per second | 12,884,670.00 | 20,165,920.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0 |
| Maximum Latency (ms) | 398.24 | 263.36 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 170,179.00 | 226,968.00 |
| Queries per second | 1,701,790.00 | 2,269,680.00 |
| Minimum Latency (ms) | 0.05 | 0.03 |
| Average Latency (ms) | 0.06 | 0.04 |
| Maximum Latency (ms) | 7.27 | 0.49 |
| 95th Percentile Latency (ms) | 0.08 | 0.06 |
MySQL SELECT (Random Points)
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 7,819.00 | 10,984.00 |
| Queries per second | 78,190.00 | 109,840.00 |
| Minimum Latency (ms) | 0.42 | 0.27 |
| Average Latency (ms) | 1.28 | 0.91 |
| Maximum Latency (ms) | 6.03 | 2.99 |
| 95th Percentile Latency (ms) | 1.64 | 1.23 |
MySQL SELECT (Random Ranges)
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 7,328.00 | 9,929.00 |
| Queries per second | 73,280.00 | 99,290.00 |
| Minimum Latency (ms) | 0.3 | 0.2 |
| Average Latency (ms) | 1.36 | 1.01 |
| Maximum Latency (ms) | 4.97 | 3 |
| 95th Percentile Latency (ms) | 1.76 | 1.34 |
MySQL UPDATE (Indexed)
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,603.00 | 15,747.00 |
| Queries per second | 86,030.00 | 157,470.00 |
| Minimum Latency (ms) | 0.69 | 0.39 |
| Average Latency (ms) | 1.16 | 0.63 |
| Maximum Latency (ms) | 6.97 | 2.83 |
| 95th Percentile Latency (ms) | 1.7 | 0.89 |
MySQL UPDATE (Non-Indexed)
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 7,719.00 | 16,371.00 |
| Queries per second | 77,190.00 | 163,710.00 |
| Minimum Latency (ms) | 0.65 | 0.37 |
| Average Latency (ms) | 1.29 | 0.61 |
| Maximum Latency (ms) | 54.76 | 1.64 |
| 95th Percentile Latency (ms) | 1.73 | 0.84 |
MySQL DELETE
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 80,451.00 | 149,199.00 |
| Queries per second | 804,510.00 | 1,491,990.00 |
| Minimum Latency (ms) | 0.05 | 0.03 |
| Average Latency (ms) | 0.12 | 0.07 |
| Maximum Latency (ms) | 16.14 | 4.81 |
| 95th Percentile Latency (ms) | 0.42 | 0.08 |
Redis
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE per Second | 44,052.86 | 83,472.46 |
| PING_MBULK per Second | 44,563.28 | 83,263.95 |
| SET per Second | 44,072.28 | 83,125.52 |
| GET per Second | 44,345.89 | 83,194.67 |
| INCR per Second | 42,535.09 | 81,300.81 |
| LPUSH per Second | 41,545.49 | 84,530.86 |
| RPUSH per Second | 37,299.52 | 82,987.55 |
| LPOP per Second | 43,327.55 | 80,128.20 |
| RPOP per Second | 43,103.45 | 82,644.62 |
| SADD per Second | 43,994.72 | 83,822.30 |
| HSET per Second | 43,956.04 | 82,372.32 |
| SPOP per Second | 44,130.62 | 80,450.52 |
| ZADD per Second | 42,390.84 | 84,602.37 |
| ZPOPMIN per Second | 43,159.26 | 87,642.41 |
| LRANGE_100 (first 100 elements) per Second | 28,843.38 | 56,179.78 |
| LRANGE_300 (first 300 elements) per Second | 15,153.81 | 31,715.82 |
| LRANGE_500 (first 500 elements) per Second | 10,595.47 | 19,888.62 |
| LRANGE_600 (first 600 elements) per Second | 9,122.42 | 15,092.06 |
| MSET (10 keys) per Second | 40,112.31 | 79,554.50 |
Redis Average Latency (ms)
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE | 0.78 | 0.31 |
| PING_MBULK | 0.77 | 0.31 |
| SET | 0.78 | 0.31 |
| GET | 0.77 | 0.31 |
| INCR | 0.80 | 0.32 |
| LPUSH | 0.82 | 0.31 |
| RPUSH | 0.90 | 0.31 |
| LPOP | 0.80 | 0.32 |
| RPOP | 0.80 | 0.32 |
| SADD | 0.78 | 0.31 |
| HSET | 0.79 | 0.31 |
| SPOP | 0.77 | 0.33 |
| ZADD | 0.81 | 0.31 |
| ZPOPMIN | 0.79 | 0.29 |
| LRANGE_100 (first 100 elements) | 1.23 | 0.49 |
| LRANGE_300 (first 300 elements) | 2.38 | 0.95 |
| LRANGE_500 (first 500 elements) | 3.44 | 1.53 |
| LRANGE_600 (first 600 elements) | 3.96 | 2.10 |
| MSET (10 keys) | 0.88 | 0.41 |
Conclusion
From the friendly robots:
After analyzing the benchmarks, the Linode Nanode (1 GB) instance shows strong performance in Redis operations, particularly with high requests per second (rps) and relatively low latency across various commands, indicating efficient memory usage and CPU performance despite having only 1 CPU core and 1 GB of RAM. On the other hand, the Vultr Cloud Compute (4 GB, 2 Cores) instance significantly outperforms in both CPU utilization, with higher events per second and lower average latency, as well as in memory operations, featuring higher throughput and more operations per second. The Vultr instance also excels in Redis operations with even higher rps and lower latencies. Ideal use cases for the Linode instance would be lightweight applications or development environments where modest performance suffices, while the Vultr instance is well-suited for more demanding workloads, such as CPU-intensive tasks and applications requiring higher memory throughput and overall performance.
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.