Linode Nanode (1 GB) vs. Vultr High Performance AMD (2 GB)
Fresh benchmarks coming at ya. Today I've spun up brand new instance from Linode and Vultr and ran some benchmarks. Each instance was spun up with Ubuntu 24.04 LTS x64 and all resided in or around the New York / New Jersey area. Enough talk. Here's the data.
Overview
| Linode – Nanode (1 GB) | Vultr – High Performance AMD (2 GB) | |
|---|---|---|
| Last Benchmarked | Fri, 29 May 2026 15:00:53 GMT | Fri, 29 May 2026 13:00:53 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 | $12.00 |
| RAM (GB) | 1 | 2 |
| CPU Cores | 1 | 1 |
| Storage (TB) | 25 | 50 |
| Storage Type | SSD | NVMe |
| Transfer (TB) | 1 | 3 |
CPU
| Linode – Nanode (1 GB) | Vultr – High Performance AMD (2 GB) | |
|---|---|---|
| Vendor | AuthenticAMD | AuthenticAMD |
| Model Name | AMD EPYC 7642 48-Core Processor | AMD EPYC-Genoa Processor |
| Clock Speed (MHz) | 2,300.00 | 2,900.00 |
| CPU Cache Size (KB) | 512.00 | 1,024.00 |
| BogoMips | 4,599.99 | 5,800.00 |
| Events per Second | 1,022.23 | 4,571.75 |
| Minimum Latency (ms) | 0.61 | 0.21 |
| Average Latency (ms) | 0.98 | 0.22 |
| Maximum Latency (ms) | 5.4 | 3.35 |
| 95th Percentile Latency (ms) | 2.39 | 0.23 |
Memory
Memory Read
| Linode – Nanode (1 GB) | Vultr – High Performance AMD (2 GB) | |
|---|---|---|
| Operations per second | 5,296,233.64 | 7,459,554.27 |
| Mebibytes per second | 5,172.10 | 7,284.72 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 3.05 | 0.58 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Linode – Nanode (1 GB) | Vultr – High Performance AMD (2 GB) | |
|---|---|---|
| Operations per second | 5,154,651.90 | 7,475,561.40 |
| Mebibytes per second | 5,033.84 | 7,300.35 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 3.06 | 0.27 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Linode – Nanode (1 GB) | Vultr – High Performance AMD (2 GB) | |
|---|---|---|
| Reads per Second | 2,055.76 | 5,083.40 |
| Writes per Second | 1,370.51 | 3,388.87 |
| Fsyncs per Second | 4,389.22 | 10,846.93 |
| Read Mebibytes per Second | 32.12 | 79.43 |
| Written Mebibytes per Second | 21.41 | 52.95 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.13 | 0.05 |
| Maximum Latency (ms) | 12.79 | 8.54 |
| 95th Percentile Latency (ms) | 0.35 | 0.12 |
Mutex
| Linode – Nanode (1 GB) | Vultr – High Performance AMD (2 GB) | |
|---|---|---|
| Minimum Latency (ms) | 1,633.32 | 1,261.44 |
| Average Latency (ms) | 1,644.62 | 1,266.47 |
| Maximum Latency (ms) | 1,653.29 | 1,274.11 |
| 95th Percentile Latency (ms) | 1,648.20 | 1,280.93 |
MySQL
MySQL Read-only
| Linode – Nanode (1 GB) | Vultr – High Performance AMD (2 GB) | |
|---|---|---|
| Transactions per second | 7,575.00 | 12,567.00 |
| Queries per second | 75,750.00 | 125,670.00 |
| Minimum Latency (ms) | 1.22 | 0.71 |
| Average Latency (ms) | 1.32 | 0.79 |
| Maximum Latency (ms) | 4.67 | 3.08 |
| 95th Percentile Latency (ms) | 1.42 | 0.94 |
MySQL Write-only
| Linode – Nanode (1 GB) | Vultr – High Performance AMD (2 GB) | |
|---|---|---|
| Transactions per second | 5,800.00 | 10,288.00 |
| Queries per second | 58,000.00 | 102,880.00 |
| Minimum Latency (ms) | 1.15 | 0.65 |
| Average Latency (ms) | 1.72 | 0.97 |
| Maximum Latency (ms) | 12.35 | 3.2 |
| 95th Percentile Latency (ms) | 2.39 | 1.34 |
MySQL Read/Write
| Linode – Nanode (1 GB) | Vultr – High Performance AMD (2 GB) | |
|---|---|---|
| Transactions per second | 2,955.00 | 4,897.00 |
| Queries per second | 29,550.00 | 48,970.00 |
| Minimum Latency (ms) | 2.64 | 1.61 |
| Average Latency (ms) | 3.38 | 2.04 |
| Maximum Latency (ms) | 22.69 | 5.14 |
| 95th Percentile Latency (ms) | 4.41 | 2.57 |
MySQL INSERT
| Linode – Nanode (1 GB) | Vultr – High Performance AMD (2 GB) | |
|---|---|---|
| Transactions per second | 8,921.00 | 16,170.00 |
| Queries per second | 89,210.00 | 161,700.00 |
| Minimum Latency (ms) | 0.65 | 0.43 |
| Average Latency (ms) | 1.12 | 0.62 |
| Maximum Latency (ms) | 8.92 | 18.34 |
| 95th Percentile Latency (ms) | 1.42 | 0.74 |
MySQL Bulk INSERT
| Linode – Nanode (1 GB) | Vultr – High Performance AMD (2 GB) | |
|---|---|---|
| Transactions per second | 1,288,467.00 | 2,408,418.00 |
| Queries per second | 12,884,670.00 | 24,084,180.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0 |
| Maximum Latency (ms) | 398.24 | 221.46 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Linode – Nanode (1 GB) | Vultr – High Performance AMD (2 GB) | |
|---|---|---|
| Transactions per second | 170,179.00 | 326,079.00 |
| Queries per second | 1,701,790.00 | 3,260,790.00 |
| Minimum Latency (ms) | 0.05 | 0.03 |
| Average Latency (ms) | 0.06 | 0.03 |
| Maximum Latency (ms) | 7.27 | 3.17 |
| 95th Percentile Latency (ms) | 0.08 | 0.04 |
MySQL SELECT (Random Points)
| Linode – Nanode (1 GB) | Vultr – High Performance AMD (2 GB) | |
|---|---|---|
| Transactions per second | 7,819.00 | 14,308.00 |
| Queries per second | 78,190.00 | 143,080.00 |
| Minimum Latency (ms) | 0.42 | 0.16 |
| Average Latency (ms) | 1.28 | 0.7 |
| Maximum Latency (ms) | 6.03 | 3.35 |
| 95th Percentile Latency (ms) | 1.64 | 0.89 |
MySQL SELECT (Random Ranges)
| Linode – Nanode (1 GB) | Vultr – High Performance AMD (2 GB) | |
|---|---|---|
| Transactions per second | 7,328.00 | 14,222.00 |
| Queries per second | 73,280.00 | 142,220.00 |
| Minimum Latency (ms) | 0.3 | 0.26 |
| Average Latency (ms) | 1.36 | 0.7 |
| Maximum Latency (ms) | 4.97 | 3.04 |
| 95th Percentile Latency (ms) | 1.76 | 0.9 |
MySQL UPDATE (Indexed)
| Linode – Nanode (1 GB) | Vultr – High Performance AMD (2 GB) | |
|---|---|---|
| Transactions per second | 8,603.00 | 15,111.00 |
| Queries per second | 86,030.00 | 151,110.00 |
| Minimum Latency (ms) | 0.69 | 0.43 |
| Average Latency (ms) | 1.16 | 0.66 |
| Maximum Latency (ms) | 6.97 | 3.73 |
| 95th Percentile Latency (ms) | 1.7 | 1.01 |
MySQL UPDATE (Non-Indexed)
| Linode – Nanode (1 GB) | Vultr – High Performance AMD (2 GB) | |
|---|---|---|
| Transactions per second | 7,719.00 | 15,910.00 |
| Queries per second | 77,190.00 | 159,100.00 |
| Minimum Latency (ms) | 0.65 | 0.42 |
| Average Latency (ms) | 1.29 | 0.63 |
| Maximum Latency (ms) | 54.76 | 3.9 |
| 95th Percentile Latency (ms) | 1.73 | 0.9 |
MySQL DELETE
| Linode – Nanode (1 GB) | Vultr – High Performance AMD (2 GB) | |
|---|---|---|
| Transactions per second | 80,451.00 | 194,308.00 |
| Queries per second | 804,510.00 | 1,943,080.00 |
| Minimum Latency (ms) | 0.05 | 0.02 |
| Average Latency (ms) | 0.12 | 0.05 |
| Maximum Latency (ms) | 16.14 | 3.02 |
| 95th Percentile Latency (ms) | 0.42 | 0.08 |
Redis
| Linode – Nanode (1 GB) | Vultr – High Performance AMD (2 GB) | |
|---|---|---|
| PING_INLINE per Second | 44,052.86 | 40,273.86 |
| PING_MBULK per Second | 44,563.28 | 41,186.16 |
| SET per Second | 44,072.28 | 40,749.80 |
| GET per Second | 44,345.89 | 40,983.61 |
| INCR per Second | 42,535.09 | 40,866.37 |
| LPUSH per Second | 41,545.49 | 40,716.61 |
| RPUSH per Second | 37,299.52 | 40,766.41 |
| LPOP per Second | 43,327.55 | 40,966.82 |
| RPOP per Second | 43,103.45 | 35,536.61 |
| SADD per Second | 43,994.72 | 41,220.11 |
| HSET per Second | 43,956.04 | 40,453.08 |
| SPOP per Second | 44,130.62 | 41,649.31 |
| ZADD per Second | 42,390.84 | 41,631.97 |
| ZPOPMIN per Second | 43,159.26 | 41,963.91 |
| LRANGE_100 (first 100 elements) per Second | 28,843.38 | 32,701.11 |
| LRANGE_300 (first 300 elements) per Second | 15,153.81 | 21,114.87 |
| LRANGE_500 (first 500 elements) per Second | 10,595.47 | 15,974.44 |
| LRANGE_600 (first 600 elements) per Second | 9,122.42 | 14,202.53 |
| MSET (10 keys) per Second | 40,112.31 | 39,651.07 |
Redis Average Latency (ms)
| Linode – Nanode (1 GB) | Vultr – High Performance AMD (2 GB) | |
|---|---|---|
| PING_INLINE | 0.78 | 0.82 |
| PING_MBULK | 0.77 | 0.81 |
| SET | 0.78 | 0.82 |
| GET | 0.77 | 0.81 |
| INCR | 0.80 | 0.81 |
| LPUSH | 0.82 | 0.81 |
| RPUSH | 0.90 | 0.81 |
| LPOP | 0.80 | 0.82 |
| RPOP | 0.80 | 0.95 |
| SADD | 0.78 | 0.81 |
| HSET | 0.79 | 0.83 |
| SPOP | 0.77 | 0.80 |
| ZADD | 0.81 | 0.80 |
| ZPOPMIN | 0.79 | 0.79 |
| LRANGE_100 (first 100 elements) | 1.23 | 1.01 |
| LRANGE_300 (first 300 elements) | 2.38 | 1.55 |
| LRANGE_500 (first 500 elements) | 3.44 | 2.08 |
| LRANGE_600 (first 600 elements) | 3.96 | 2.33 |
| MSET (10 keys) | 0.88 | 0.85 |
Conclusion
From the friendly robots:
Comparing the benchmarks of Linode's Nanode and Vultr's High Performance AMD instance, it's clear that both offer unique strengths. The Linode Nanode shines in Redis operations, particularly in high-throughput tasks like SET, GET, and INCR, showcasing very high request rates and low latencies. The Vultr instance, while slightly behind in Redis performance, offers better CPU efficiency with higher events per second and better overall thread fairness. It also provides superior file I/O and memory performance, with higher throughput and lower latencies for both read and write operations. For applications needing high Redis throughput with modest CPU demands, the Linode Nanode is ideal, whereas for workloads that require better CPU efficiency, superior memory performance, and higher file I/O operations, the Vultr High Performance AMD instance is more suitable.
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.