Linode Nanode (1 GB) vs. Vultr High Frequency Intel (1 GB)
New day, new benchmarks. Today I've spun up some brand new instance from Linode and Vultr to run some benchmarks on. All instances were running Ubuntu 24.04 LTS x64 and were created in or around the New York / New Jersey area. Time to see who showed up today.
Overview
| Linode – Nanode (1 GB) | Vultr – High Frequency Intel (1 GB) | |
|---|---|---|
| Last Benchmarked | Fri, 29 May 2026 15:00:53 GMT | Wed, 27 May 2026 11: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 | $6.00 |
| RAM (GB) | 1 | 1 |
| CPU Cores | 1 | 1 |
| Storage (TB) | 25 | 32 |
| Storage Type | SSD | NVMe |
| Transfer (TB) | 1 | 1 |
CPU
| Linode – Nanode (1 GB) | Vultr – High Frequency Intel (1 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,070.05 |
| Minimum Latency (ms) | 0.61 | 0.23 |
| Average Latency (ms) | 0.98 | 0.25 |
| Maximum Latency (ms) | 5.4 | 1.79 |
| 95th Percentile Latency (ms) | 2.39 | 0.28 |
Memory
Memory Read
| Linode – Nanode (1 GB) | Vultr – High Frequency Intel (1 GB) | |
|---|---|---|
| Operations per second | 5,296,233.64 | 8,789,401.86 |
| Mebibytes per second | 5,172.10 | 8,583.40 |
| 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 Frequency Intel (1 GB) | |
|---|---|---|
| Operations per second | 5,154,651.90 | 8,651,859.92 |
| Mebibytes per second | 5,033.84 | 8,449.08 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 3.06 | 0.54 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Linode – Nanode (1 GB) | Vultr – High Frequency Intel (1 GB) | |
|---|---|---|
| Reads per Second | 2,055.76 | 6,116.78 |
| Writes per Second | 1,370.51 | 4,077.79 |
| Fsyncs per Second | 4,389.22 | 13,049.55 |
| Read Mebibytes per Second | 32.12 | 95.57 |
| Written Mebibytes per Second | 21.41 | 63.72 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.13 | 0.04 |
| Maximum Latency (ms) | 12.79 | 1.6 |
| 95th Percentile Latency (ms) | 0.35 | 0.14 |
Mutex
| Linode – Nanode (1 GB) | Vultr – High Frequency Intel (1 GB) | |
|---|---|---|
| Minimum Latency (ms) | 1,633.32 | 1,119.99 |
| Average Latency (ms) | 1,644.62 | 1,130.23 |
| Maximum Latency (ms) | 1,653.29 | 1,138.75 |
| 95th Percentile Latency (ms) | 1,648.20 | 1,129.24 |
MySQL
MySQL Read-only
| Linode – Nanode (1 GB) | Vultr – High Frequency Intel (1 GB) | |
|---|---|---|
| Transactions per second | 7,575.00 | 13,254.00 |
| Queries per second | 75,750.00 | 132,540.00 |
| Minimum Latency (ms) | 1.22 | 0.67 |
| Average Latency (ms) | 1.32 | 0.75 |
| Maximum Latency (ms) | 4.67 | 4.77 |
| 95th Percentile Latency (ms) | 1.42 | 0.83 |
MySQL Write-only
| Linode – Nanode (1 GB) | Vultr – High Frequency Intel (1 GB) | |
|---|---|---|
| Transactions per second | 5,800.00 | 12,926.00 |
| Queries per second | 58,000.00 | 129,260.00 |
| Minimum Latency (ms) | 1.15 | 0.49 |
| Average Latency (ms) | 1.72 | 0.77 |
| Maximum Latency (ms) | 12.35 | 6.05 |
| 95th Percentile Latency (ms) | 2.39 | 1.21 |
MySQL Read/Write
| Linode – Nanode (1 GB) | Vultr – High Frequency Intel (1 GB) | |
|---|---|---|
| Transactions per second | 2,955.00 | 5,630.00 |
| Queries per second | 29,550.00 | 56,300.00 |
| Minimum Latency (ms) | 2.64 | 1.34 |
| Average Latency (ms) | 3.38 | 1.77 |
| Maximum Latency (ms) | 22.69 | 4.28 |
| 95th Percentile Latency (ms) | 4.41 | 2.35 |
MySQL INSERT
| Linode – Nanode (1 GB) | Vultr – High Frequency Intel (1 GB) | |
|---|---|---|
| Transactions per second | 8,921.00 | 27,541.00 |
| Queries per second | 89,210.00 | 275,410.00 |
| Minimum Latency (ms) | 0.65 | 0.26 |
| Average Latency (ms) | 1.12 | 0.36 |
| Maximum Latency (ms) | 8.92 | 3.78 |
| 95th Percentile Latency (ms) | 1.42 | 0.49 |
MySQL Bulk INSERT
| Linode – Nanode (1 GB) | Vultr – High Frequency Intel (1 GB) | |
|---|---|---|
| Transactions per second | 1,288,467.00 | 2,424,342.00 |
| Queries per second | 12,884,670.00 | 24,243,420.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0 |
| Maximum Latency (ms) | 398.24 | 231.9 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Linode – Nanode (1 GB) | Vultr – High Frequency Intel (1 GB) | |
|---|---|---|
| Transactions per second | 170,179.00 | 313,347.00 |
| Queries per second | 1,701,790.00 | 3,133,470.00 |
| Minimum Latency (ms) | 0.05 | 0.03 |
| Average Latency (ms) | 0.06 | 0.03 |
| Maximum Latency (ms) | 7.27 | 3.12 |
| 95th Percentile Latency (ms) | 0.08 | 0.04 |
MySQL SELECT (Random Points)
| Linode – Nanode (1 GB) | Vultr – High Frequency Intel (1 GB) | |
|---|---|---|
| Transactions per second | 7,819.00 | 13,113.00 |
| Queries per second | 78,190.00 | 131,130.00 |
| Minimum Latency (ms) | 0.42 | 0.2 |
| Average Latency (ms) | 1.28 | 0.76 |
| Maximum Latency (ms) | 6.03 | 3.09 |
| 95th Percentile Latency (ms) | 1.64 | 0.99 |
MySQL SELECT (Random Ranges)
| Linode – Nanode (1 GB) | Vultr – High Frequency Intel (1 GB) | |
|---|---|---|
| Transactions per second | 7,328.00 | 15,696.00 |
| Queries per second | 73,280.00 | 156,960.00 |
| Minimum Latency (ms) | 0.3 | 0.21 |
| Average Latency (ms) | 1.36 | 0.64 |
| Maximum Latency (ms) | 4.97 | 1.93 |
| 95th Percentile Latency (ms) | 1.76 | 0.83 |
MySQL UPDATE (Indexed)
| Linode – Nanode (1 GB) | Vultr – High Frequency Intel (1 GB) | |
|---|---|---|
| Transactions per second | 8,603.00 | 21,350.00 |
| Queries per second | 86,030.00 | 213,500.00 |
| Minimum Latency (ms) | 0.69 | 0.27 |
| Average Latency (ms) | 1.16 | 0.47 |
| Maximum Latency (ms) | 6.97 | 3.4 |
| 95th Percentile Latency (ms) | 1.7 | 0.73 |
MySQL UPDATE (Non-Indexed)
| Linode – Nanode (1 GB) | Vultr – High Frequency Intel (1 GB) | |
|---|---|---|
| Transactions per second | 7,719.00 | 22,667.00 |
| Queries per second | 77,190.00 | 226,670.00 |
| Minimum Latency (ms) | 0.65 | 0.26 |
| Average Latency (ms) | 1.29 | 0.44 |
| Maximum Latency (ms) | 54.76 | 2.9 |
| 95th Percentile Latency (ms) | 1.73 | 0.7 |
MySQL DELETE
| Linode – Nanode (1 GB) | Vultr – High Frequency Intel (1 GB) | |
|---|---|---|
| Transactions per second | 80,451.00 | 202,678.00 |
| Queries per second | 804,510.00 | 2,026,780.00 |
| Minimum Latency (ms) | 0.05 | 0.03 |
| Average Latency (ms) | 0.12 | 0.05 |
| Maximum Latency (ms) | 16.14 | 49.65 |
| 95th Percentile Latency (ms) | 0.42 | 0.08 |
Redis
| Linode – Nanode (1 GB) | Vultr – High Frequency Intel (1 GB) | |
|---|---|---|
| PING_INLINE per Second | 44,052.86 | 62,111.80 |
| PING_MBULK per Second | 44,563.28 | 63,131.31 |
| SET per Second | 44,072.28 | 62,266.50 |
| GET per Second | 44,345.89 | 62,695.92 |
| INCR per Second | 42,535.09 | 62,617.41 |
| LPUSH per Second | 41,545.49 | 62,617.41 |
| RPUSH per Second | 37,299.52 | 62,500.00 |
| LPOP per Second | 43,327.55 | 60,827.25 |
| RPOP per Second | 43,103.45 | 61,919.50 |
| SADD per Second | 43,994.72 | 61,766.52 |
| HSET per Second | 43,956.04 | 62,344.14 |
| SPOP per Second | 44,130.62 | 62,972.29 |
| ZADD per Second | 42,390.84 | 62,266.50 |
| ZPOPMIN per Second | 43,159.26 | 63,331.22 |
| LRANGE_100 (first 100 elements) per Second | 28,843.38 | 46,382.19 |
| LRANGE_300 (first 300 elements) per Second | 15,153.81 | 28,669.72 |
| LRANGE_500 (first 500 elements) per Second | 10,595.47 | 20,230.63 |
| LRANGE_600 (first 600 elements) per Second | 9,122.42 | 17,869.91 |
| MSET (10 keys) per Second | 40,112.31 | 58,858.15 |
Redis Average Latency (ms)
| Linode – Nanode (1 GB) | Vultr – High Frequency Intel (1 GB) | |
|---|---|---|
| PING_INLINE | 0.78 | 0.50 |
| PING_MBULK | 0.77 | 0.49 |
| SET | 0.78 | 0.50 |
| GET | 0.77 | 0.50 |
| INCR | 0.80 | 0.50 |
| LPUSH | 0.82 | 0.50 |
| RPUSH | 0.90 | 0.50 |
| LPOP | 0.80 | 0.51 |
| RPOP | 0.80 | 0.50 |
| SADD | 0.78 | 0.50 |
| HSET | 0.79 | 0.50 |
| SPOP | 0.77 | 0.49 |
| ZADD | 0.81 | 0.50 |
| ZPOPMIN | 0.79 | 0.49 |
| LRANGE_100 (first 100 elements) | 1.23 | 0.70 |
| LRANGE_300 (first 300 elements) | 2.38 | 1.16 |
| LRANGE_500 (first 500 elements) | 3.44 | 1.62 |
| LRANGE_600 (first 600 elements) | 3.96 | 1.88 |
| MSET (10 keys) | 0.88 | 0.55 |
Conclusion
From the friendly robots:
Both Linode's Nanode (1 GB) and Vultr's High Frequency Intel (1 GB) instances show strong performance, but they cater to different use cases due to their distinct strengths. The Vultr instance demonstrates higher Redis performance, with notably higher requests per second and lower latency across a variety of operations, suggesting it is better suited for high-performance caching and data processing tasks. Conversely, Linode's instance excels in MySQL bulk insert operations and offers superior file I/O performance, making it more appropriate for databases and file-intensive applications. When considering price, Vultr's instance is slightly more expensive, but it provides a clear advantage in Redis-related benchmarks, while Linode's instance leads in MySQL and file I/O operations. Users should choose based on their specific workload requirements, favoring Vultr for Redis-heavy tasks and Linode for database-intensive or file operations.
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.