Linode Nanode (1 GB) vs. Vultr High Performance Intel (2 GB)
My friend, I'm so glad you're here! Today I've spun up brand new instance from Linode and Vultr and did some benchmarking. Each instance was spun up with Ubuntu 24.04 LTS x64 and were created in or around the New York / New Jersey area. Enough talk. Here's the data.
Overview
| Linode – Nanode (1 GB) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Last Benchmarked | Fri, 29 May 2026 15:00:53 GMT | Fri, 29 May 2026 05: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 | $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 Intel (2 GB) | |
|---|---|---|
| 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,206.19 |
| Minimum Latency (ms) | 0.61 | 0.81 |
| Average Latency (ms) | 0.98 | 0.83 |
| Maximum Latency (ms) | 5.4 | 3.29 |
| 95th Percentile Latency (ms) | 2.39 | 0.86 |
Memory
Memory Read
| Linode – Nanode (1 GB) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Operations per second | 5,296,233.64 | 5,591,991.42 |
| Mebibytes per second | 5,172.10 | 5,460.93 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 3.05 | 0.35 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Linode – Nanode (1 GB) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Operations per second | 5,154,651.90 | 5,491,481.81 |
| Mebibytes per second | 5,033.84 | 5,362.78 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 3.06 | 0.3 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Linode – Nanode (1 GB) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Reads per Second | 2,055.76 | 5,227.24 |
| Writes per Second | 1,370.51 | 3,484.79 |
| Fsyncs per Second | 4,389.22 | 11,154.86 |
| Read Mebibytes per Second | 32.12 | 81.68 |
| Written Mebibytes per Second | 21.41 | 54.45 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.13 | 0.05 |
| Maximum Latency (ms) | 12.79 | 2.13 |
| 95th Percentile Latency (ms) | 0.35 | 0.15 |
Mutex
| Linode – Nanode (1 GB) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Minimum Latency (ms) | 1,633.32 | 1,435.85 |
| Average Latency (ms) | 1,644.62 | 1,442.52 |
| Maximum Latency (ms) | 1,653.29 | 1,448.85 |
| 95th Percentile Latency (ms) | 1,648.20 | 1,453.01 |
MySQL
MySQL Read-only
| Linode – Nanode (1 GB) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 7,575.00 | 8,395.00 |
| Queries per second | 75,750.00 | 83,950.00 |
| Minimum Latency (ms) | 1.22 | 1.05 |
| Average Latency (ms) | 1.32 | 1.19 |
| Maximum Latency (ms) | 4.67 | 5.6 |
| 95th Percentile Latency (ms) | 1.42 | 1.5 |
MySQL Write-only
| Linode – Nanode (1 GB) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 5,800.00 | 9,371.00 |
| Queries per second | 58,000.00 | 93,710.00 |
| Minimum Latency (ms) | 1.15 | 0.75 |
| Average Latency (ms) | 1.72 | 1.07 |
| Maximum Latency (ms) | 12.35 | 3.46 |
| 95th Percentile Latency (ms) | 2.39 | 1.42 |
MySQL Read/Write
| Linode – Nanode (1 GB) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 2,955.00 | 3,792.00 |
| Queries per second | 29,550.00 | 37,920.00 |
| Minimum Latency (ms) | 2.64 | 2.09 |
| Average Latency (ms) | 3.38 | 2.63 |
| Maximum Latency (ms) | 22.69 | 9.19 |
| 95th Percentile Latency (ms) | 4.41 | 3.3 |
MySQL INSERT
| Linode – Nanode (1 GB) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 8,921.00 | 17,044.00 |
| Queries per second | 89,210.00 | 170,440.00 |
| Minimum Latency (ms) | 0.65 | 0.41 |
| Average Latency (ms) | 1.12 | 0.58 |
| Maximum Latency (ms) | 8.92 | 9.77 |
| 95th Percentile Latency (ms) | 1.42 | 0.77 |
MySQL Bulk INSERT
| Linode – Nanode (1 GB) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 1,288,467.00 | 1,463,217.00 |
| Queries per second | 12,884,670.00 | 14,632,170.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0.01 |
| Maximum Latency (ms) | 398.24 | 329.56 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Linode – Nanode (1 GB) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 170,179.00 | 229,529.00 |
| Queries per second | 1,701,790.00 | 2,295,290.00 |
| Minimum Latency (ms) | 0.05 | 0.04 |
| Average Latency (ms) | 0.06 | 0.04 |
| Maximum Latency (ms) | 7.27 | 1.24 |
| 95th Percentile Latency (ms) | 0.08 | 0.06 |
MySQL SELECT (Random Points)
| Linode – Nanode (1 GB) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 7,819.00 | 7,518.00 |
| Queries per second | 78,190.00 | 75,180.00 |
| Minimum Latency (ms) | 0.42 | 0.41 |
| Average Latency (ms) | 1.28 | 1.33 |
| Maximum Latency (ms) | 6.03 | 4.71 |
| 95th Percentile Latency (ms) | 1.64 | 1.73 |
MySQL SELECT (Random Ranges)
| Linode – Nanode (1 GB) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 7,328.00 | 8,093.00 |
| Queries per second | 73,280.00 | 80,930.00 |
| Minimum Latency (ms) | 0.3 | 0.5 |
| Average Latency (ms) | 1.36 | 1.23 |
| Maximum Latency (ms) | 4.97 | 3.17 |
| 95th Percentile Latency (ms) | 1.76 | 1.64 |
MySQL UPDATE (Indexed)
| Linode – Nanode (1 GB) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 8,603.00 | 16,757.00 |
| Queries per second | 86,030.00 | 167,570.00 |
| Minimum Latency (ms) | 0.69 | 0.41 |
| Average Latency (ms) | 1.16 | 0.6 |
| Maximum Latency (ms) | 6.97 | 2.52 |
| 95th Percentile Latency (ms) | 1.7 | 0.84 |
MySQL UPDATE (Non-Indexed)
| Linode – Nanode (1 GB) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 7,719.00 | 17,303.00 |
| Queries per second | 77,190.00 | 173,030.00 |
| Minimum Latency (ms) | 0.65 | 0.4 |
| Average Latency (ms) | 1.29 | 0.58 |
| Maximum Latency (ms) | 54.76 | 2.22 |
| 95th Percentile Latency (ms) | 1.73 | 0.77 |
MySQL DELETE
| Linode – Nanode (1 GB) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 80,451.00 | 149,834.00 |
| Queries per second | 804,510.00 | 1,498,340.00 |
| Minimum Latency (ms) | 0.05 | 0.04 |
| Average Latency (ms) | 0.12 | 0.07 |
| Maximum Latency (ms) | 16.14 | 2.02 |
| 95th Percentile Latency (ms) | 0.42 | 0.12 |
Redis
| Linode – Nanode (1 GB) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| PING_INLINE per Second | 44,052.86 | 49,043.65 |
| PING_MBULK per Second | 44,563.28 | 49,850.45 |
| SET per Second | 44,072.28 | 47,915.67 |
| GET per Second | 44,345.89 | 48,638.13 |
| INCR per Second | 42,535.09 | 49,309.66 |
| LPUSH per Second | 41,545.49 | 48,685.49 |
| RPUSH per Second | 37,299.52 | 48,732.94 |
| LPOP per Second | 43,327.55 | 48,309.18 |
| RPOP per Second | 43,103.45 | 48,638.13 |
| SADD per Second | 43,994.72 | 48,030.74 |
| HSET per Second | 43,956.04 | 48,638.13 |
| SPOP per Second | 44,130.62 | 49,529.47 |
| ZADD per Second | 42,390.84 | 48,661.80 |
| ZPOPMIN per Second | 43,159.26 | 49,627.79 |
| LRANGE_100 (first 100 elements) per Second | 28,843.38 | 31,397.18 |
| LRANGE_300 (first 300 elements) per Second | 15,153.81 | 17,059.02 |
| LRANGE_500 (first 500 elements) per Second | 10,595.47 | 11,502.19 |
| LRANGE_600 (first 600 elements) per Second | 9,122.42 | 9,700.26 |
| MSET (10 keys) per Second | 40,112.31 | 45,106.00 |
Redis Average Latency (ms)
| Linode – Nanode (1 GB) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| PING_INLINE | 0.78 | 0.67 |
| PING_MBULK | 0.77 | 0.66 |
| SET | 0.78 | 0.69 |
| GET | 0.77 | 0.69 |
| INCR | 0.80 | 0.67 |
| LPUSH | 0.82 | 0.69 |
| RPUSH | 0.90 | 0.68 |
| LPOP | 0.80 | 0.69 |
| RPOP | 0.80 | 0.69 |
| SADD | 0.78 | 0.69 |
| HSET | 0.79 | 0.68 |
| SPOP | 0.77 | 0.66 |
| ZADD | 0.81 | 0.69 |
| ZPOPMIN | 0.79 | 0.67 |
| LRANGE_100 (first 100 elements) | 1.23 | 1.11 |
| LRANGE_300 (first 300 elements) | 2.38 | 2.11 |
| LRANGE_500 (first 500 elements) | 3.44 | 3.09 |
| LRANGE_600 (first 600 elements) | 3.96 | 3.68 |
| MSET (10 keys) | 0.88 | 0.76 |
Conclusion
From the friendly robots:
When comparing the benchmark performance of the Linode Nanode (1 GB) and the Vultr High Performance Intel (2 GB) instances, the Vultr instance demonstrates superior performance metrics across the board, particularly in CPU and Redis benchmarks where it achieved higher requests per second (rps) and lower latency for various operations. The Vultr instance also excelled in file I/O operations, showing higher throughput and lower average latency. The Linode instance, while competent, showed lower rps and higher latency in Redis operations, file I/O, and CPU benchmarks, suggesting it is more suitable for lower-demand applications. The Vultr instance’s higher RAM and more powerful CPU make it ideal for CPU-intensive, I/O-heavy workloads, while the Linode instance might be more appropriate for simpler, less demanding tasks.
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.