Linode Nanode (1 GB) vs. Vultr Cloud Compute (1 GB)
Same showdown, different day. Today I've spun up some brand new instance from Linode and Vultr to run some benchmarks on. Each instance was spun up with 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 (1 GB) | |
|---|---|---|
| Last Benchmarked | Thu, 25 Dec 2025 09:00:51 GMT | Tue, 23 Dec 2025 19:00:51 GMT |
| Linux Distro | Ubuntu 24.04 LTS x64 | Ubuntu 24.04 LTS x64 |
| Kernel Version | 6.8.0-71-generic | 6.8.0-90-generic |
| MySQL Version | 8.0.44-0ubuntu0.24.04.2 | 8.0.44-0ubuntu0.24.04.2 |
| Redis Version | 7.0.15 | 7.0.15 |
| Location | Newark, NJ | Newark, NJ |
| Monthly Price | $5.00 | $5.00 |
| RAM (GB) | 1 | 1 |
| CPU Cores | 1 | 1 |
| Storage (TB) | 25 | 25 |
| Storage Type | SSD | SSD |
| Transfer (TB) | 1 | 1 |
CPU
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (1 GB) | |
|---|---|---|
| Vendor | AuthenticAMD | GenuineIntel |
| Model Name | AMD EPYC 7713 64-Core Processor | Intel Core Processor (Broadwell, no TSX, IBRS) |
| Clock Speed (MHz) | 2,000.00 | 2,400.00 |
| CPU Cache Size (KB) | 512.00 | 16,384.00 |
| BogoMips | 3,999.99 | 4,799.99 |
| Events per Second | 1,664.06 | 774.49 |
| Minimum Latency (ms) | 0.28 | 1.13 |
| Average Latency (ms) | 0.6 | 1.29 |
| Maximum Latency (ms) | 29.07 | 3.64 |
| 95th Percentile Latency (ms) | 2.86 | 1.55 |
Memory
Memory Read
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (1 GB) | |
|---|---|---|
| Operations per second | 2,695,177.67 | 3,563,144.39 |
| Mebibytes per second | 2,632.01 | 3,479.63 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 3.64 | 2.33 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (1 GB) | |
|---|---|---|
| Operations per second | 5,064,699.38 | 3,578,279.14 |
| Mebibytes per second | 4,946.00 | 3,494.41 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 2.03 | 1.36 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (1 GB) | |
|---|---|---|
| Reads per Second | 2,101.42 | 1,893.29 |
| Writes per Second | 1,400.94 | 1,262.20 |
| Fsyncs per Second | 4,487.49 | 4,041.52 |
| Read Mebibytes per Second | 32.83 | 29.58 |
| Written Mebibytes per Second | 21.89 | 19.72 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.12 | 0.14 |
| Maximum Latency (ms) | 6.63 | 7.93 |
| 95th Percentile Latency (ms) | 0.3 | 0.35 |
Mutex
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (1 GB) | |
|---|---|---|
| Minimum Latency (ms) | 1,779.50 | 2,405.08 |
| Average Latency (ms) | 1,789.35 | 2,423.84 |
| Maximum Latency (ms) | 1,804.14 | 2,436.20 |
| 95th Percentile Latency (ms) | 1,803.47 | 2,449.36 |
MySQL
MySQL Read-only
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (1 GB) | |
|---|---|---|
| Transactions per second | 6,359.00 | 4,627.00 |
| Queries per second | 63,590.00 | 46,270.00 |
| Minimum Latency (ms) | 1.3 | 1.69 |
| Average Latency (ms) | 1.57 | 2.16 |
| Maximum Latency (ms) | 9.8 | 14.35 |
| 95th Percentile Latency (ms) | 1.89 | 3.13 |
MySQL Write-only
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (1 GB) | |
|---|---|---|
| Transactions per second | 4,913.00 | 3,192.00 |
| Queries per second | 49,130.00 | 31,920.00 |
| Minimum Latency (ms) | 1.35 | 1.88 |
| Average Latency (ms) | 2.03 | 3.13 |
| Maximum Latency (ms) | 8.51 | 32.5 |
| 95th Percentile Latency (ms) | 2.81 | 4.57 |
MySQL Read/Write
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (1 GB) | |
|---|---|---|
| Transactions per second | 2,408.00 | 1,733.00 |
| Queries per second | 24,080.00 | 17,330.00 |
| Minimum Latency (ms) | 3.1 | 3.98 |
| Average Latency (ms) | 4.15 | 5.77 |
| Maximum Latency (ms) | 11.3 | 15.77 |
| 95th Percentile Latency (ms) | 5.18 | 8.28 |
MySQL INSERT
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (1 GB) | |
|---|---|---|
| Transactions per second | 7,492.00 | 5,038.00 |
| Queries per second | 74,920.00 | 50,380.00 |
| Minimum Latency (ms) | 0.95 | 1.29 |
| Average Latency (ms) | 1.33 | 1.98 |
| Maximum Latency (ms) | 9.48 | 20.82 |
| 95th Percentile Latency (ms) | 1.79 | 2.76 |
MySQL Bulk INSERT
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (1 GB) | |
|---|---|---|
| Transactions per second | 1,201,092.00 | 800,273.00 |
| Queries per second | 12,010,920.00 | 8,002,730.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0.01 |
| Maximum Latency (ms) | 508.44 | 783.86 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (1 GB) | |
|---|---|---|
| Transactions per second | 127,654.00 | 100,060.00 |
| Queries per second | 1,276,540.00 | 1,000,600.00 |
| Minimum Latency (ms) | 0.06 | 0.07 |
| Average Latency (ms) | 0.08 | 0.1 |
| Maximum Latency (ms) | 6.3 | 9.15 |
| 95th Percentile Latency (ms) | 0.11 | 0.15 |
MySQL SELECT (Random Points)
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (1 GB) | |
|---|---|---|
| Transactions per second | 8,562.00 | 4,470.00 |
| Queries per second | 85,620.00 | 44,700.00 |
| Minimum Latency (ms) | 0.29 | 0.68 |
| Average Latency (ms) | 1.17 | 2.23 |
| Maximum Latency (ms) | 9.19 | 9.2 |
| 95th Percentile Latency (ms) | 1.58 | 3.55 |
MySQL SELECT (Random Ranges)
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (1 GB) | |
|---|---|---|
| Transactions per second | 9,338.00 | 4,738.00 |
| Queries per second | 93,380.00 | 47,380.00 |
| Minimum Latency (ms) | 0.41 | 0.65 |
| Average Latency (ms) | 1.07 | 2.11 |
| Maximum Latency (ms) | 7.81 | 8.72 |
| 95th Percentile Latency (ms) | 1.39 | 3.68 |
MySQL UPDATE (Indexed)
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (1 GB) | |
|---|---|---|
| Transactions per second | 7,211.00 | 4,344.00 |
| Queries per second | 72,110.00 | 43,440.00 |
| Minimum Latency (ms) | 0.77 | 1.12 |
| Average Latency (ms) | 1.39 | 2.3 |
| Maximum Latency (ms) | 7.29 | 37 |
| 95th Percentile Latency (ms) | 2 | 3.96 |
MySQL UPDATE (Non-Indexed)
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (1 GB) | |
|---|---|---|
| Transactions per second | 7,966.00 | 5,409.00 |
| Queries per second | 79,660.00 | 54,090.00 |
| Minimum Latency (ms) | 0.92 | 1.08 |
| Average Latency (ms) | 1.25 | 1.85 |
| Maximum Latency (ms) | 9.36 | 13.01 |
| 95th Percentile Latency (ms) | 1.64 | 2.52 |
MySQL DELETE
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (1 GB) | |
|---|---|---|
| Transactions per second | 52,482.00 | 34,310.00 |
| Queries per second | 524,820.00 | 343,100.00 |
| Minimum Latency (ms) | 0.05 | 0.07 |
| Average Latency (ms) | 0.19 | 0.29 |
| Maximum Latency (ms) | 11.04 | 6.95 |
| 95th Percentile Latency (ms) | 1.16 | 1.82 |
Redis
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (1 GB) | |
|---|---|---|
| PING_INLINE per Second | 35,448.42 | 33,670.04 |
| PING_MBULK per Second | 35,373.19 | 32,948.93 |
| SET per Second | 35,100.04 | 32,829.94 |
| GET per Second | 36,310.82 | 34,411.56 |
| INCR per Second | 35,498.76 | 36,258.16 |
| LPUSH per Second | 35,511.36 | 32,435.94 |
| RPUSH per Second | 35,373.19 | 34,891.84 |
| LPOP per Second | 35,038.54 | 31,938.68 |
| RPOP per Second | 34,566.20 | 31,605.56 |
| SADD per Second | 35,663.34 | 32,679.74 |
| HSET per Second | 35,298.27 | 33,840.95 |
| SPOP per Second | 36,483.04 | 34,411.56 |
| ZADD per Second | 35,893.75 | 34,542.32 |
| ZPOPMIN per Second | 36,023.05 | 34,176.35 |
| LRANGE_100 (first 100 elements) per Second | 25,284.45 | 22,084.81 |
| LRANGE_300 (first 300 elements) per Second | 15,195.26 | 10,593.22 |
| LRANGE_500 (first 500 elements) per Second | 10,902.75 | 7,519.93 |
| LRANGE_600 (first 600 elements) per Second | 9,585.89 | 5,956.28 |
| MSET (10 keys) per Second | 29,078.22 | 29,594.55 |
Redis Average Latency (ms)
| Linode – Nanode (1 GB) | Vultr – Cloud Compute (1 GB) | |
|---|---|---|
| PING_INLINE | 0.93 | 0.97 |
| PING_MBULK | 0.93 | 0.98 |
| SET | 0.95 | 0.99 |
| GET | 0.91 | 0.95 |
| INCR | 0.93 | 0.91 |
| LPUSH | 0.94 | 1.01 |
| RPUSH | 0.94 | 0.95 |
| LPOP | 0.96 | 1.04 |
| RPOP | 0.97 | 1.04 |
| SADD | 0.93 | 1.00 |
| HSET | 0.94 | 0.98 |
| SPOP | 0.91 | 0.95 |
| ZADD | 0.93 | 0.96 |
| ZPOPMIN | 0.92 | 0.96 |
| LRANGE_100 (first 100 elements) | 1.34 | 1.53 |
| LRANGE_300 (first 300 elements) | 2.22 | 3.20 |
| LRANGE_500 (first 500 elements) | 3.08 | 4.53 |
| LRANGE_600 (first 600 elements) | 3.55 | 5.63 |
| MSET (10 keys) | 1.16 | 1.17 |
Conclusion
From the friendly robots:
The Linode Nanode configuration outperforms the Vultr Cloud Compute instance in most benchmarks, demonstrating superior performance in Redis operations, MySQL tasks, and general CPU utilization. The Linode instance shows higher rates of requests per second (rps) and lower latencies across a variety of metrics, indicating it can handle more requests with lower wait times. In contrast, the Vultr instance, while competitive, falls behind in handling complex data retrieval operations like Redis LRANGE commands and MySQL OLTP operations. For users needing high-performance, low-latency workloads, especially for CPU-intensive tasks or applications requiring rapid data access, the Linode Nanode would be more suitable. Conversely, if the priority is a cost-effective, minimal configuration for light workloads, the Vultr Cloud Compute instance remains a viable option.
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.