Linode Nanode (1 GB) vs. Vultr Cloud Compute (8 GB, 4 Cores)
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. Without further ado, here's the results.
Overview
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (8 GB, 4 Cores) | |
|---|---|---|
| Last Benchmarked | Sat, 23 May 2026 13:00:52 GMT | Sat, 23 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 | $40.00 |
| RAM (GB) | 1 | 8 |
| CPU Cores | 1 | 4 |
| Storage (TB) | 25 | 160 |
| Storage Type | SSD | SSD |
| Transfer (TB) | 1 | 4 |
CPU
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (8 GB, 4 Cores) | |
|---|---|---|
| Vendor | AuthenticAMD | GenuineIntel |
| Model Name | AMD EPYC 7642 48-Core Processor | Intel Xeon Processor (Skylake, IBRS) |
| Clock Speed (MHz) | 2,300.00 | 2,593.90 |
| CPU Cache Size (KB) | 512.00 | 16,384.00 |
| BogoMips | 4,600.00 | 5,187.80 |
| Events per Second | 905.04 | 1,100.82 |
| Minimum Latency (ms) | 0.61 | 0.88 |
| Average Latency (ms) | 1.1 | 0.91 |
| Maximum Latency (ms) | 22.05 | 1.56 |
| 95th Percentile Latency (ms) | 2.48 | 0.97 |
Memory
Memory Read
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (8 GB, 4 Cores) | |
|---|---|---|
| Operations per second | 5,013,583.91 | 3,685,781.23 |
| Mebibytes per second | 4,896.08 | 3,599.40 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 9.43 | 1.03 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (8 GB, 4 Cores) | |
|---|---|---|
| Operations per second | 4,999,712.46 | 3,590,629.63 |
| Mebibytes per second | 4,882.53 | 3,506.47 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 9.49 | 1.16 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (8 GB, 4 Cores) | |
|---|---|---|
| Reads per Second | 1,752.56 | 4,999.39 |
| Writes per Second | 1,168.34 | 3,332.93 |
| Fsyncs per Second | 3,745.40 | 10,670.47 |
| Read Mebibytes per Second | 27.38 | 78.12 |
| Written Mebibytes per Second | 18.26 | 52.08 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.15 | 0.05 |
| Maximum Latency (ms) | 75.52 | 37.52 |
| 95th Percentile Latency (ms) | 0.42 | 0.18 |
Mutex
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (8 GB, 4 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 1,654.93 | 369.37 |
| Average Latency (ms) | 1,667.46 | 416.22 |
| Maximum Latency (ms) | 1,678.80 | 441.77 |
| 95th Percentile Latency (ms) | 1,678.14 | 442.73 |
MySQL
MySQL Read-only
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 6,108.00 | 5,144.00 |
| Queries per second | 61,080.00 | 51,440.00 |
| Minimum Latency (ms) | 1.43 | 1.72 |
| Average Latency (ms) | 1.64 | 1.94 |
| Maximum Latency (ms) | 22.63 | 7.67 |
| 95th Percentile Latency (ms) | 2 | 2.35 |
MySQL Write-only
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 4,788.00 | 5,108.00 |
| Queries per second | 47,880.00 | 51,080.00 |
| Minimum Latency (ms) | 1.33 | 1.15 |
| Average Latency (ms) | 2.09 | 1.96 |
| Maximum Latency (ms) | 24.02 | 12.52 |
| 95th Percentile Latency (ms) | 3.07 | 2.71 |
MySQL Read/Write
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 2,490.00 | 2,247.00 |
| Queries per second | 24,900.00 | 22,470.00 |
| Minimum Latency (ms) | 3.03 | 3.08 |
| Average Latency (ms) | 4.02 | 4.45 |
| Maximum Latency (ms) | 15.36 | 29.7 |
| 95th Percentile Latency (ms) | 5.09 | 5.28 |
MySQL INSERT
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 8,775.00 | 7,630.00 |
| Queries per second | 87,750.00 | 76,300.00 |
| Minimum Latency (ms) | 0.68 | 0.71 |
| Average Latency (ms) | 1.14 | 1.31 |
| Maximum Latency (ms) | 20.34 | 29.81 |
| 95th Percentile Latency (ms) | 1.47 | 1.55 |
MySQL Bulk INSERT
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 898,571.00 | 898,571.00 |
| Queries per second | 8,985,710.00 | 8,985,710.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0.01 |
| Maximum Latency (ms) | 1312.33 | 505.86 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 131,900.00 | 149,465.00 |
| Queries per second | 1,319,000.00 | 1,494,650.00 |
| Minimum Latency (ms) | 0.06 | 0.05 |
| Average Latency (ms) | 0.08 | 0.07 |
| Maximum Latency (ms) | 12.86 | 1.22 |
| 95th Percentile Latency (ms) | 0.11 | 0.09 |
MySQL SELECT (Random Points)
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 6,799.00 | 4,249.00 |
| Queries per second | 67,990.00 | 42,490.00 |
| Minimum Latency (ms) | 0.48 | 0.83 |
| Average Latency (ms) | 1.47 | 2.35 |
| Maximum Latency (ms) | 12.9 | 6.6 |
| 95th Percentile Latency (ms) | 2.03 | 3.02 |
MySQL SELECT (Random Ranges)
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 6,912.00 | 2,637.00 |
| Queries per second | 69,120.00 | 26,370.00 |
| Minimum Latency (ms) | 0.36 | 0.94 |
| Average Latency (ms) | 1.45 | 3.79 |
| Maximum Latency (ms) | 5.54 | 6.3 |
| 95th Percentile Latency (ms) | 1.93 | 5.09 |
MySQL UPDATE (Indexed)
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 7,586.00 | 7,166.00 |
| Queries per second | 75,860.00 | 71,660.00 |
| Minimum Latency (ms) | 0.75 | 0.7 |
| Average Latency (ms) | 1.32 | 1.39 |
| Maximum Latency (ms) | 19.75 | 28.84 |
| 95th Percentile Latency (ms) | 2 | 1.79 |
MySQL UPDATE (Non-Indexed)
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 7,848.00 | 7,661.00 |
| Queries per second | 78,480.00 | 76,610.00 |
| Minimum Latency (ms) | 0.7 | 0.7 |
| Average Latency (ms) | 1.27 | 1.3 |
| Maximum Latency (ms) | 23.83 | 33.97 |
| 95th Percentile Latency (ms) | 1.82 | 1.58 |
MySQL DELETE
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 61,230.00 | 69,690.00 |
| Queries per second | 612,300.00 | 696,900.00 |
| Minimum Latency (ms) | 0.06 | 0.05 |
| Average Latency (ms) | 0.16 | 0.14 |
| Maximum Latency (ms) | 19.09 | 27.73 |
| 95th Percentile Latency (ms) | 0.97 | 0.87 |
Redis
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (8 GB, 4 Cores) | |
|---|---|---|
| PING_INLINE per Second | 38,804.81 | 54,436.58 |
| PING_MBULK per Second | 39,154.27 | 48,828.12 |
| SET per Second | 38,789.76 | 51,572.98 |
| GET per Second | 38,431.98 | 48,239.27 |
| INCR per Second | 38,971.16 | 52,328.62 |
| LPUSH per Second | 39,154.27 | 45,454.54 |
| RPUSH per Second | 38,505.97 | 49,751.24 |
| LPOP per Second | 38,476.34 | 53,390.28 |
| RPOP per Second | 38,925.65 | 53,648.07 |
| SADD per Second | 38,255.55 | 48,285.85 |
| HSET per Second | 36,737.70 | 51,493.30 |
| SPOP per Second | 38,925.65 | 52,910.05 |
| ZADD per Second | 38,580.25 | 53,504.55 |
| ZPOPMIN per Second | 39,603.96 | 53,590.57 |
| LRANGE_100 (first 100 elements) per Second | 26,602.82 | 28,645.09 |
| LRANGE_300 (first 300 elements) per Second | 14,660.61 | 13,131.98 |
| LRANGE_500 (first 500 elements) per Second | 10,073.54 | 8,529.51 |
| LRANGE_600 (first 600 elements) per Second | 8,647.53 | 7,479.99 |
| MSET (10 keys) per Second | 34,141.35 | 49,212.60 |
Redis Average Latency (ms)
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (8 GB, 4 Cores) | |
|---|---|---|
| PING_INLINE | 0.87 | 0.47 |
| PING_MBULK | 0.86 | 0.53 |
| SET | 0.87 | 0.50 |
| GET | 0.87 | 0.54 |
| INCR | 0.86 | 0.49 |
| LPUSH | 0.86 | 0.58 |
| RPUSH | 0.88 | 0.52 |
| LPOP | 0.88 | 0.49 |
| RPOP | 0.88 | 0.48 |
| SADD | 0.88 | 0.54 |
| HSET | 0.91 | 0.53 |
| SPOP | 0.86 | 0.49 |
| ZADD | 0.88 | 0.48 |
| ZPOPMIN | 0.85 | 0.48 |
| LRANGE_100 (first 100 elements) | 1.30 | 0.91 |
| LRANGE_300 (first 300 elements) | 2.48 | 1.94 |
| LRANGE_500 (first 500 elements) | 3.57 | 3.00 |
| LRANGE_600 (first 600 elements) | 4.12 | 3.43 |
| MSET (10 keys) | 1.02 | 0.77 |
Conclusion
From the friendly robots:
Upon comparing the benchmark performance of the Linode Nanode (1 GB) and Vultr Cloud Compute (8 GB, 4 Cores), it's evident that Vultr's instance demonstrates superior overall performance, particularly in CPU-intensive and I/O-heavy tasks. Vultr’s instance consistently outperforms in Redis benchmarks, CPU events per second, and memory operations per second, while also showing better thread fairness and lower latencies. Conversely, the Linode instance excels in minimal configurations, making it suitable for lightweight applications and tasks that do not require significant computational power or memory. Therefore, the Vultr instance is ideal for workloads demanding more resources, whereas the Linode Nanode is better suited for less demanding, cost-effective applications.
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.