Linode Nanode (1 GB) vs. Vultr High Performance Intel (2 GB, 2 Cores)
New day, new benchmarks. Today I've spun up some 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 or around the New York / New Jersey area. Let's get into the numbers.
Overview
| Linode – Nanode (1 GB) | Vultr – High Performance Intel (2 GB, 2 Cores) | |
|---|---|---|
| Last Benchmarked | Fri, 29 May 2026 15:00:53 GMT | Thu, 28 May 2026 19: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 | $18.00 |
| RAM (GB) | 1 | 2 |
| CPU Cores | 1 | 2 |
| Storage (TB) | 25 | 60 |
| Storage Type | SSD | NVMe |
| Transfer (TB) | 1 | 4 |
CPU
| Linode – Nanode (1 GB) | Vultr – High Performance Intel (2 GB, 2 Cores) | |
|---|---|---|
| Vendor | AuthenticAMD | GenuineIntel |
| Model Name | AMD EPYC 7642 48-Core Processor | Intel Xeon Processor (Cascadelake) |
| Clock Speed (MHz) | 2,300.00 | 2,992.91 |
| CPU Cache Size (KB) | 512.00 | 16,384.00 |
| BogoMips | 4,599.99 | 5,985.82 |
| Events per Second | 1,022.23 | 1,187.62 |
| Minimum Latency (ms) | 0.61 | 0.81 |
| Average Latency (ms) | 0.98 | 0.84 |
| Maximum Latency (ms) | 5.4 | 2.88 |
| 95th Percentile Latency (ms) | 2.39 | 0.9 |
Memory
Memory Read
| Linode – Nanode (1 GB) | Vultr – High Performance Intel (2 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 5,296,233.64 | 5,533,703.60 |
| Mebibytes per second | 5,172.10 | 5,404.01 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 3.05 | 0.25 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Linode – Nanode (1 GB) | Vultr – High Performance Intel (2 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 5,154,651.90 | 5,505,088.80 |
| Mebibytes per second | 5,033.84 | 5,376.06 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 3.06 | 1.61 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Linode – Nanode (1 GB) | Vultr – High Performance Intel (2 GB, 2 Cores) | |
|---|---|---|
| Reads per Second | 2,055.76 | 4,521.36 |
| Writes per Second | 1,370.51 | 3,014.24 |
| Fsyncs per Second | 4,389.22 | 9,651.47 |
| Read Mebibytes per Second | 32.12 | 70.65 |
| Written Mebibytes per Second | 21.41 | 47.10 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.13 | 0.06 |
| Maximum Latency (ms) | 12.79 | 2.34 |
| 95th Percentile Latency (ms) | 0.35 | 0.17 |
Mutex
| Linode – Nanode (1 GB) | Vultr – High Performance Intel (2 GB, 2 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 1,633.32 | 786.47 |
| Average Latency (ms) | 1,644.62 | 840.34 |
| Maximum Latency (ms) | 1,653.29 | 902.81 |
| 95th Percentile Latency (ms) | 1,648.20 | 909.80 |
MySQL
MySQL Read-only
| Linode – Nanode (1 GB) | Vultr – High Performance Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 7,575.00 | 7,827.00 |
| Queries per second | 75,750.00 | 78,270.00 |
| Minimum Latency (ms) | 1.22 | 1.06 |
| Average Latency (ms) | 1.32 | 1.28 |
| Maximum Latency (ms) | 4.67 | 6.83 |
| 95th Percentile Latency (ms) | 1.42 | 1.67 |
MySQL Write-only
| Linode – Nanode (1 GB) | Vultr – High Performance Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 5,800.00 | 8,553.00 |
| Queries per second | 58,000.00 | 85,530.00 |
| Minimum Latency (ms) | 1.15 | 0.76 |
| Average Latency (ms) | 1.72 | 1.17 |
| Maximum Latency (ms) | 12.35 | 5.93 |
| 95th Percentile Latency (ms) | 2.39 | 1.64 |
MySQL Read/Write
| Linode – Nanode (1 GB) | Vultr – High Performance Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 2,955.00 | 4,001.00 |
| Queries per second | 29,550.00 | 40,010.00 |
| Minimum Latency (ms) | 2.64 | 1.95 |
| Average Latency (ms) | 3.38 | 2.5 |
| Maximum Latency (ms) | 22.69 | 12.92 |
| 95th Percentile Latency (ms) | 4.41 | 3.19 |
MySQL INSERT
| Linode – Nanode (1 GB) | Vultr – High Performance Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,921.00 | 15,620.00 |
| Queries per second | 89,210.00 | 156,200.00 |
| Minimum Latency (ms) | 0.65 | 0.41 |
| Average Latency (ms) | 1.12 | 0.64 |
| Maximum Latency (ms) | 8.92 | 7.59 |
| 95th Percentile Latency (ms) | 1.42 | 0.87 |
MySQL Bulk INSERT
| Linode – Nanode (1 GB) | Vultr – High Performance Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 1,288,467.00 | 1,667,092.00 |
| Queries per second | 12,884,670.00 | 16,670,920.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0.01 |
| Maximum Latency (ms) | 398.24 | 301.96 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Linode – Nanode (1 GB) | Vultr – High Performance Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 170,179.00 | 199,934.00 |
| Queries per second | 1,701,790.00 | 1,999,340.00 |
| Minimum Latency (ms) | 0.05 | 0.03 |
| Average Latency (ms) | 0.06 | 0.05 |
| Maximum Latency (ms) | 7.27 | 0.9 |
| 95th Percentile Latency (ms) | 0.08 | 0.07 |
MySQL SELECT (Random Points)
| Linode – Nanode (1 GB) | Vultr – High Performance Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 7,819.00 | 7,539.00 |
| Queries per second | 78,190.00 | 75,390.00 |
| Minimum Latency (ms) | 0.42 | 0.4 |
| Average Latency (ms) | 1.28 | 1.32 |
| Maximum Latency (ms) | 6.03 | 4.12 |
| 95th Percentile Latency (ms) | 1.64 | 1.76 |
MySQL SELECT (Random Ranges)
| Linode – Nanode (1 GB) | Vultr – High Performance Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 7,328.00 | 7,695.00 |
| Queries per second | 73,280.00 | 76,950.00 |
| Minimum Latency (ms) | 0.3 | 0.46 |
| Average Latency (ms) | 1.36 | 1.3 |
| Maximum Latency (ms) | 4.97 | 3.38 |
| 95th Percentile Latency (ms) | 1.76 | 1.79 |
MySQL UPDATE (Indexed)
| Linode – Nanode (1 GB) | Vultr – High Performance Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,603.00 | 14,916.00 |
| Queries per second | 86,030.00 | 149,160.00 |
| Minimum Latency (ms) | 0.69 | 0.42 |
| Average Latency (ms) | 1.16 | 0.67 |
| Maximum Latency (ms) | 6.97 | 2.94 |
| 95th Percentile Latency (ms) | 1.7 | 0.99 |
MySQL UPDATE (Non-Indexed)
| Linode – Nanode (1 GB) | Vultr – High Performance Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 7,719.00 | 15,251.00 |
| Queries per second | 77,190.00 | 152,510.00 |
| Minimum Latency (ms) | 0.65 | 0.41 |
| Average Latency (ms) | 1.29 | 0.65 |
| Maximum Latency (ms) | 54.76 | 13.01 |
| 95th Percentile Latency (ms) | 1.73 | 0.9 |
MySQL DELETE
| Linode – Nanode (1 GB) | Vultr – High Performance Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 80,451.00 | 134,991.00 |
| Queries per second | 804,510.00 | 1,349,910.00 |
| Minimum Latency (ms) | 0.05 | 0.03 |
| Average Latency (ms) | 0.12 | 0.07 |
| Maximum Latency (ms) | 16.14 | 4.38 |
| 95th Percentile Latency (ms) | 0.42 | 0.1 |
Redis
| Linode – Nanode (1 GB) | Vultr – High Performance Intel (2 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE per Second | 44,052.86 | 64,020.48 |
| PING_MBULK per Second | 44,563.28 | 63,451.78 |
| SET per Second | 44,072.28 | 63,979.53 |
| GET per Second | 44,345.89 | 67,069.08 |
| INCR per Second | 42,535.09 | 66,622.25 |
| LPUSH per Second | 41,545.49 | 66,800.27 |
| RPUSH per Second | 37,299.52 | 66,093.85 |
| LPOP per Second | 43,327.55 | 68,352.70 |
| RPOP per Second | 43,103.45 | 67,521.95 |
| SADD per Second | 43,994.72 | 67,204.30 |
| HSET per Second | 43,956.04 | 67,430.88 |
| SPOP per Second | 44,130.62 | 66,181.34 |
| ZADD per Second | 42,390.84 | 66,050.20 |
| ZPOPMIN per Second | 43,159.26 | 67,613.25 |
| LRANGE_100 (first 100 elements) per Second | 28,843.38 | 48,923.68 |
| LRANGE_300 (first 300 elements) per Second | 15,153.81 | 28,620.49 |
| LRANGE_500 (first 500 elements) per Second | 10,595.47 | 20,120.72 |
| LRANGE_600 (first 600 elements) per Second | 9,122.42 | 17,190.99 |
| MSET (10 keys) per Second | 40,112.31 | 66,313.00 |
Redis Average Latency (ms)
| Linode – Nanode (1 GB) | Vultr – High Performance Intel (2 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE | 0.78 | 0.41 |
| PING_MBULK | 0.77 | 0.41 |
| SET | 0.78 | 0.41 |
| GET | 0.77 | 0.38 |
| INCR | 0.80 | 0.39 |
| LPUSH | 0.82 | 0.39 |
| RPUSH | 0.90 | 0.39 |
| LPOP | 0.80 | 0.39 |
| RPOP | 0.80 | 0.38 |
| SADD | 0.78 | 0.39 |
| HSET | 0.79 | 0.38 |
| SPOP | 0.77 | 0.39 |
| ZADD | 0.81 | 0.39 |
| ZPOPMIN | 0.79 | 0.38 |
| LRANGE_100 (first 100 elements) | 1.23 | 0.55 |
| LRANGE_300 (first 300 elements) | 2.38 | 0.97 |
| LRANGE_500 (first 500 elements) | 3.44 | 1.43 |
| LRANGE_600 (first 600 elements) | 3.96 | 1.66 |
| MSET (10 keys) | 0.88 | 0.39 |
Conclusion
From the friendly robots:
In benchmarking, the Linode Nanode (1 GB) instance demonstrates robust performance for simple Redis operations, achieving high requests per second (rps) with relatively low latencies, though it shows a notable decline in performance for more complex Redis commands like LRANGE with larger datasets. On the other hand, the Vultr High Performance Intel (2 GB, 2 Cores) instance excels in handling more demanding tasks, exhibiting significantly higher rps rates and lower latencies across a broader spectrum of Redis operations, especially for LRANGE with larger datasets. While the Vultr instance also delivers superior CPU and memory performance, the Linode instance is more budget-friendly. Hence, the Linode Nanode is ideal for basic workloads and cost-sensitive projects, whereas the Vultr High Performance Intel is better suited for more complex, demanding applications requiring higher computational and data access throughput.
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.