Linode Nanode (1 GB) vs. Vultr High Frequency Intel (2 GB)
Fresh benchmarks coming at ya. 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 all resided in or around the New York / New Jersey area. Enough talk. Here's the data.
Overview
| Linode – Nanode (1 GB) | Vultr – High Frequency Intel (2 GB) | |
|---|---|---|
| Last Benchmarked | Fri, 29 May 2026 15:00:53 GMT | Wed, 27 May 2026 02: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 | 64 |
| Storage Type | SSD | NVMe |
| Transfer (TB) | 1 | 2 |
CPU
| Linode – Nanode (1 GB) | Vultr – High Frequency Intel (2 GB) | |
|---|---|---|
| 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,192.00 |
| CPU Cache Size (KB) | 512.00 | 16,384.00 |
| BogoMips | 4,599.99 | 6,384.00 |
| Events per Second | 1,022.23 | 4,305.45 |
| Minimum Latency (ms) | 0.61 | 0.23 |
| Average Latency (ms) | 0.98 | 0.23 |
| Maximum Latency (ms) | 5.4 | 2.9 |
| 95th Percentile Latency (ms) | 2.39 | 0.25 |
Memory
Memory Read
| Linode – Nanode (1 GB) | Vultr – High Frequency Intel (2 GB) | |
|---|---|---|
| Operations per second | 5,296,233.64 | 9,400,390.29 |
| Mebibytes per second | 5,172.10 | 9,180.07 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 3.05 | 0.32 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Linode – Nanode (1 GB) | Vultr – High Frequency Intel (2 GB) | |
|---|---|---|
| Operations per second | 5,154,651.90 | 9,401,759.67 |
| Mebibytes per second | 5,033.84 | 9,181.41 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 3.06 | 0.83 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Linode – Nanode (1 GB) | Vultr – High Frequency Intel (2 GB) | |
|---|---|---|
| Reads per Second | 2,055.76 | 7,484.03 |
| Writes per Second | 1,370.51 | 4,989.35 |
| Fsyncs per Second | 4,389.22 | 15,967.85 |
| Read Mebibytes per Second | 32.12 | 116.94 |
| Written Mebibytes per Second | 21.41 | 77.96 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.13 | 0.03 |
| Maximum Latency (ms) | 12.79 | 1.87 |
| 95th Percentile Latency (ms) | 0.35 | 0.13 |
Mutex
| Linode – Nanode (1 GB) | Vultr – High Frequency Intel (2 GB) | |
|---|---|---|
| Minimum Latency (ms) | 1,633.32 | 1,002.06 |
| Average Latency (ms) | 1,644.62 | 1,006.23 |
| Maximum Latency (ms) | 1,653.29 | 1,011.51 |
| 95th Percentile Latency (ms) | 1,648.20 | 1,013.60 |
MySQL
MySQL Read-only
| Linode – Nanode (1 GB) | Vultr – High Frequency Intel (2 GB) | |
|---|---|---|
| Transactions per second | 7,575.00 | 14,009.00 |
| Queries per second | 75,750.00 | 140,090.00 |
| Minimum Latency (ms) | 1.22 | 0.66 |
| Average Latency (ms) | 1.32 | 0.71 |
| Maximum Latency (ms) | 4.67 | 2.13 |
| 95th Percentile Latency (ms) | 1.42 | 0.75 |
MySQL Write-only
| Linode – Nanode (1 GB) | Vultr – High Frequency Intel (2 GB) | |
|---|---|---|
| Transactions per second | 5,800.00 | 13,650.00 |
| Queries per second | 58,000.00 | 136,500.00 |
| Minimum Latency (ms) | 1.15 | 0.49 |
| Average Latency (ms) | 1.72 | 0.73 |
| Maximum Latency (ms) | 12.35 | 9.22 |
| 95th Percentile Latency (ms) | 2.39 | 1.12 |
MySQL Read/Write
| Linode – Nanode (1 GB) | Vultr – High Frequency Intel (2 GB) | |
|---|---|---|
| Transactions per second | 2,955.00 | 5,991.00 |
| Queries per second | 29,550.00 | 59,910.00 |
| Minimum Latency (ms) | 2.64 | 1.34 |
| Average Latency (ms) | 3.38 | 1.67 |
| Maximum Latency (ms) | 22.69 | 6.11 |
| 95th Percentile Latency (ms) | 4.41 | 2.11 |
MySQL INSERT
| Linode – Nanode (1 GB) | Vultr – High Frequency Intel (2 GB) | |
|---|---|---|
| Transactions per second | 8,921.00 | 30,591.00 |
| Queries per second | 89,210.00 | 305,910.00 |
| Minimum Latency (ms) | 0.65 | 0.26 |
| Average Latency (ms) | 1.12 | 0.33 |
| Maximum Latency (ms) | 8.92 | 6.3 |
| 95th Percentile Latency (ms) | 1.42 | 0.4 |
MySQL Bulk INSERT
| Linode – Nanode (1 GB) | Vultr – High Frequency Intel (2 GB) | |
|---|---|---|
| Transactions per second | 1,288,467.00 | 2,832,092.00 |
| Queries per second | 12,884,670.00 | 28,320,920.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0 |
| Maximum Latency (ms) | 398.24 | 176.83 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Linode – Nanode (1 GB) | Vultr – High Frequency Intel (2 GB) | |
|---|---|---|
| Transactions per second | 170,179.00 | 331,979.00 |
| Queries per second | 1,701,790.00 | 3,319,790.00 |
| Minimum Latency (ms) | 0.05 | 0.03 |
| Average Latency (ms) | 0.06 | 0.03 |
| Maximum Latency (ms) | 7.27 | 0.82 |
| 95th Percentile Latency (ms) | 0.08 | 0.04 |
MySQL SELECT (Random Points)
| Linode – Nanode (1 GB) | Vultr – High Frequency Intel (2 GB) | |
|---|---|---|
| Transactions per second | 7,819.00 | 13,884.00 |
| Queries per second | 78,190.00 | 138,840.00 |
| Minimum Latency (ms) | 0.42 | 0.24 |
| Average Latency (ms) | 1.28 | 0.72 |
| Maximum Latency (ms) | 6.03 | 2.38 |
| 95th Percentile Latency (ms) | 1.64 | 0.92 |
MySQL SELECT (Random Ranges)
| Linode – Nanode (1 GB) | Vultr – High Frequency Intel (2 GB) | |
|---|---|---|
| Transactions per second | 7,328.00 | 16,355.00 |
| Queries per second | 73,280.00 | 163,550.00 |
| Minimum Latency (ms) | 0.3 | 0.18 |
| Average Latency (ms) | 1.36 | 0.61 |
| Maximum Latency (ms) | 4.97 | 2.24 |
| 95th Percentile Latency (ms) | 1.76 | 0.78 |
MySQL UPDATE (Indexed)
| Linode – Nanode (1 GB) | Vultr – High Frequency Intel (2 GB) | |
|---|---|---|
| Transactions per second | 8,603.00 | 22,886.00 |
| Queries per second | 86,030.00 | 228,860.00 |
| Minimum Latency (ms) | 0.69 | 0.26 |
| Average Latency (ms) | 1.16 | 0.44 |
| Maximum Latency (ms) | 6.97 | 2.52 |
| 95th Percentile Latency (ms) | 1.7 | 0.69 |
MySQL UPDATE (Non-Indexed)
| Linode – Nanode (1 GB) | Vultr – High Frequency Intel (2 GB) | |
|---|---|---|
| Transactions per second | 7,719.00 | 23,976.00 |
| Queries per second | 77,190.00 | 239,760.00 |
| Minimum Latency (ms) | 0.65 | 0.26 |
| Average Latency (ms) | 1.29 | 0.42 |
| Maximum Latency (ms) | 54.76 | 1.57 |
| 95th Percentile Latency (ms) | 1.73 | 0.67 |
MySQL DELETE
| Linode – Nanode (1 GB) | Vultr – High Frequency Intel (2 GB) | |
|---|---|---|
| Transactions per second | 80,451.00 | 230,446.00 |
| Queries per second | 804,510.00 | 2,304,460.00 |
| Minimum Latency (ms) | 0.05 | 0.03 |
| Average Latency (ms) | 0.12 | 0.04 |
| Maximum Latency (ms) | 16.14 | 4.36 |
| 95th Percentile Latency (ms) | 0.42 | 0.06 |
Redis
| Linode – Nanode (1 GB) | Vultr – High Frequency Intel (2 GB) | |
|---|---|---|
| PING_INLINE per Second | 44,052.86 | 65,487.89 |
| PING_MBULK per Second | 44,563.28 | 66,050.20 |
| SET per Second | 44,072.28 | 65,402.22 |
| GET per Second | 44,345.89 | 66,006.60 |
| INCR per Second | 42,535.09 | 65,746.22 |
| LPUSH per Second | 41,545.49 | 65,359.48 |
| RPUSH per Second | 37,299.52 | 65,659.88 |
| LPOP per Second | 43,327.55 | 64,935.07 |
| RPOP per Second | 43,103.45 | 65,274.15 |
| SADD per Second | 43,994.72 | 65,919.58 |
| HSET per Second | 43,956.04 | 65,061.81 |
| SPOP per Second | 44,130.62 | 66,313.00 |
| ZADD per Second | 42,390.84 | 64,808.82 |
| ZPOPMIN per Second | 43,159.26 | 66,357.00 |
| LRANGE_100 (first 100 elements) per Second | 28,843.38 | 48,216.01 |
| LRANGE_300 (first 300 elements) per Second | 15,153.81 | 29,086.68 |
| LRANGE_500 (first 500 elements) per Second | 10,595.47 | 21,263.02 |
| LRANGE_600 (first 600 elements) per Second | 9,122.42 | 18,782.87 |
| MSET (10 keys) per Second | 40,112.31 | 61,881.19 |
Redis Average Latency (ms)
| Linode – Nanode (1 GB) | Vultr – High Frequency Intel (2 GB) | |
|---|---|---|
| PING_INLINE | 0.78 | 0.47 |
| PING_MBULK | 0.77 | 0.46 |
| SET | 0.78 | 0.47 |
| GET | 0.77 | 0.47 |
| INCR | 0.80 | 0.47 |
| LPUSH | 0.82 | 0.47 |
| RPUSH | 0.90 | 0.47 |
| LPOP | 0.80 | 0.47 |
| RPOP | 0.80 | 0.47 |
| SADD | 0.78 | 0.47 |
| HSET | 0.79 | 0.47 |
| SPOP | 0.77 | 0.46 |
| ZADD | 0.81 | 0.48 |
| ZPOPMIN | 0.79 | 0.46 |
| LRANGE_100 (first 100 elements) | 1.23 | 0.67 |
| LRANGE_300 (first 300 elements) | 2.38 | 1.11 |
| LRANGE_500 (first 500 elements) | 3.44 | 1.54 |
| LRANGE_600 (first 600 elements) | 3.96 | 1.78 |
| MSET (10 keys) | 0.88 | 0.52 |
Conclusion
From the friendly robots:
In comparing the Linode Nanode (1 GB) and Vultr High Frequency Intel (2 GB) instances, both demonstrate excellent performance in various benchmarks, but their strengths differ based on resource needs. The Linode instance excels in single-threaded Redis operations, achieving high requests per second and relatively low latency, though it shows diminishing performance when handling large data retrievals from Redis. The Vultr instance, with its more powerful CPU and additional RAM, offers superior overall performance, especially in bulk Redis operations and handling larger data sets, making it a better choice for I/O-heavy workloads. However, it is marginally behind the Linode instance in specific single-threaded Redis operations. For budget-conscious users needing a balance of performance and cost, the Linode instance is ideal, while those prioritizing higher throughput and I/O performance should opt for the Vultr instance.
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.