Linode Linode (2 GB) vs. Vultr High Frequency Intel (2 GB, 2 Cores)
My friend, I'm so glad you're here! 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 all resided in or around the New York / New Jersey area. Enough talk. Here's the data.
Overview
| Linode – (2 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Last Benchmarked | Mon, 01 Jun 2026 15:00:52 GMT | Sun, 31 May 2026 13:00:55 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 | $12.00 | $18.00 |
| RAM (GB) | 2 | 2 |
| CPU Cores | 1 | 2 |
| Storage (TB) | 50 | 80 |
| Storage Type | SSD | NVMe |
| Transfer (TB) | 2 | 3 |
CPU
| Linode – (2 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Vendor | AuthenticAMD | GenuineIntel |
| Model Name | AMD EPYC 7713 64-Core Processor | Intel Core Processor (Skylake, IBRS, no TSX) |
| Clock Speed (MHz) | 2,000.00 | 3,791.98 |
| CPU Cache Size (KB) | 512.00 | 16,384.00 |
| BogoMips | 4,000.00 | 7,583.95 |
| Events per Second | 1,678.52 | 1,552.05 |
| Minimum Latency (ms) | 0.28 | 0.62 |
| Average Latency (ms) | 0.59 | 0.64 |
| Maximum Latency (ms) | 9.24 | 4.61 |
| 95th Percentile Latency (ms) | 2.81 | 0.69 |
Memory
Memory Read
| Linode – (2 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 2,645,654.09 | 7,875,668.83 |
| Mebibytes per second | 2,583.65 | 7,691.08 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 6.1 | 0.12 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Linode – (2 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 2,626,766.86 | 7,729,812.11 |
| Mebibytes per second | 2,565.20 | 7,548.64 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 6.15 | 0.16 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Linode – (2 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Reads per Second | 2,287.26 | 4,671.85 |
| Writes per Second | 1,524.77 | 3,114.56 |
| Fsyncs per Second | 4,881.82 | 9,976.90 |
| Read Mebibytes per Second | 35.74 | 73.00 |
| Written Mebibytes per Second | 23.82 | 48.67 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.11 | 0.06 |
| Maximum Latency (ms) | 5.87 | 2.76 |
| 95th Percentile Latency (ms) | 0.34 | 0.17 |
Mutex
| Linode – (2 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 1,654.99 | 543.27 |
| Average Latency (ms) | 1,663.47 | 554.74 |
| Maximum Latency (ms) | 1,670.46 | 563.70 |
| 95th Percentile Latency (ms) | 1,678.14 | 559.50 |
MySQL
MySQL Read-only
| Linode – (2 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 7,825.00 | 10,621.00 |
| Queries per second | 78,250.00 | 106,210.00 |
| Minimum Latency (ms) | 1.14 | 0.86 |
| Average Latency (ms) | 1.28 | 0.94 |
| Maximum Latency (ms) | 5.27 | 2.5 |
| 95th Percentile Latency (ms) | 1.5 | 1.03 |
MySQL Write-only
| Linode – (2 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 5,536.00 | 10,229.00 |
| Queries per second | 55,360.00 | 102,290.00 |
| Minimum Latency (ms) | 1.14 | 0.64 |
| Average Latency (ms) | 1.8 | 0.98 |
| Maximum Latency (ms) | 6.57 | 2.08 |
| 95th Percentile Latency (ms) | 2.39 | 1.23 |
MySQL Read/Write
| Linode – (2 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 2,901.00 | 5,072.00 |
| Queries per second | 29,010.00 | 50,720.00 |
| Minimum Latency (ms) | 2.49 | 1.59 |
| Average Latency (ms) | 3.44 | 1.97 |
| Maximum Latency (ms) | 8.33 | 3.94 |
| 95th Percentile Latency (ms) | 4.25 | 2.39 |
MySQL INSERT
| Linode – (2 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,340.00 | 16,038.00 |
| Queries per second | 83,400.00 | 160,380.00 |
| Minimum Latency (ms) | 0.67 | 0.38 |
| Average Latency (ms) | 1.2 | 0.62 |
| Maximum Latency (ms) | 5.42 | 13.18 |
| 95th Percentile Latency (ms) | 1.55 | 0.8 |
MySQL Bulk INSERT
| Linode – (2 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 1,434,092.00 | 2,424,342.00 |
| Queries per second | 14,340,920.00 | 24,243,420.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0 |
| Maximum Latency (ms) | 351.06 | 205.81 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Linode – (2 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 174,599.00 | 241,313.00 |
| Queries per second | 1,745,990.00 | 2,413,130.00 |
| Minimum Latency (ms) | 0.05 | 0.03 |
| Average Latency (ms) | 0.06 | 0.04 |
| Maximum Latency (ms) | 3.6 | 0.76 |
| 95th Percentile Latency (ms) | 0.07 | 0.05 |
MySQL SELECT (Random Points)
| Linode – (2 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 9,155.00 | 12,080.00 |
| Queries per second | 91,550.00 | 120,800.00 |
| Minimum Latency (ms) | 0.36 | 0.21 |
| Average Latency (ms) | 1.09 | 0.83 |
| Maximum Latency (ms) | 4.69 | 3.31 |
| 95th Percentile Latency (ms) | 1.44 | 1.04 |
MySQL SELECT (Random Ranges)
| Linode – (2 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,799.00 | 10,527.00 |
| Queries per second | 87,990.00 | 105,270.00 |
| Minimum Latency (ms) | 0.3 | 0.16 |
| Average Latency (ms) | 1.13 | 0.95 |
| Maximum Latency (ms) | 4.2 | 3.25 |
| 95th Percentile Latency (ms) | 2.26 | 1.23 |
MySQL UPDATE (Indexed)
| Linode – (2 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 6,915.00 | 17,123.00 |
| Queries per second | 69,150.00 | 171,230.00 |
| Minimum Latency (ms) | 0.69 | 0.38 |
| Average Latency (ms) | 1.44 | 0.58 |
| Maximum Latency (ms) | 38.35 | 2 |
| 95th Percentile Latency (ms) | 2.14 | 0.78 |
MySQL UPDATE (Non-Indexed)
| Linode – (2 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,030.00 | 16,979.00 |
| Queries per second | 80,300.00 | 169,790.00 |
| Minimum Latency (ms) | 0.68 | 0.38 |
| Average Latency (ms) | 1.24 | 0.59 |
| Maximum Latency (ms) | 5.88 | 4.13 |
| 95th Percentile Latency (ms) | 1.64 | 0.8 |
MySQL DELETE
| Linode – (2 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 75,134.00 | 156,424.00 |
| Queries per second | 751,340.00 | 1,564,240.00 |
| Minimum Latency (ms) | 0.04 | 0.03 |
| Average Latency (ms) | 0.13 | 0.06 |
| Maximum Latency (ms) | 5.6 | 4.87 |
| 95th Percentile Latency (ms) | 0.77 | 0.07 |
Redis
| Linode – (2 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE per Second | 37,369.21 | 88,652.48 |
| PING_MBULK per Second | 37,921.88 | 89,605.73 |
| SET per Second | 37,936.27 | 90,171.33 |
| GET per Second | 37,693.18 | 90,579.71 |
| INCR per Second | 37,523.45 | 90,744.10 |
| LPUSH per Second | 37,921.88 | 90,497.73 |
| RPUSH per Second | 36,075.04 | 90,415.91 |
| LPOP per Second | 37,285.61 | 90,909.09 |
| RPOP per Second | 37,993.92 | 90,661.83 |
| SADD per Second | 37,664.79 | 90,252.70 |
| HSET per Second | 37,565.74 | 90,415.91 |
| SPOP per Second | 38,182.51 | 89,928.05 |
| ZADD per Second | 37,750.09 | 90,415.91 |
| ZPOPMIN per Second | 37,299.52 | 90,009.01 |
| LRANGE_100 (first 100 elements) per Second | 26,048.45 | 66,533.60 |
| LRANGE_300 (first 300 elements) per Second | 15,156.11 | 36,179.45 |
| LRANGE_500 (first 500 elements) per Second | 10,071.51 | 26,239.83 |
| LRANGE_600 (first 600 elements) per Second | 9,412.65 | 22,547.91 |
| MSET (10 keys) per Second | 34,317.09 | 88,105.73 |
Redis Average Latency (ms)
| Linode – (2 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE | 0.87 | 0.30 |
| PING_MBULK | 0.86 | 0.29 |
| SET | 0.87 | 0.29 |
| GET | 0.87 | 0.29 |
| INCR | 0.88 | 0.28 |
| LPUSH | 0.88 | 0.29 |
| RPUSH | 0.94 | 0.29 |
| LPOP | 0.90 | 0.28 |
| RPOP | 0.89 | 0.28 |
| SADD | 0.89 | 0.29 |
| HSET | 0.90 | 0.29 |
| SPOP | 0.88 | 0.29 |
| ZADD | 0.89 | 0.29 |
| ZPOPMIN | 0.90 | 0.29 |
| LRANGE_100 (first 100 elements) | 1.30 | 0.39 |
| LRANGE_300 (first 300 elements) | 2.19 | 0.71 |
| LRANGE_500 (first 500 elements) | 3.30 | 0.97 |
| LRANGE_600 (first 600 elements) | 3.57 | 1.14 |
| MSET (10 keys) | 0.98 | 0.30 |
Conclusion
From the friendly robots:
Upon analyzing the provided benchmark results for both Linode and Vultr instances, it is clear that Vultr's High Frequency Intel configuration outperforms Linode's AMD EPYC instance, particularly in terms of raw throughput for Redis operations, with higher requests per second and lower average latencies observed in most benchmarks. This suggests that for workloads that heavily rely on fast data access and manipulation, such as caching or real-time data processing, the Vultr instance would be more suitable. However, Linode offers slightly better file I/O performance and more consistent thread fairness in its benchmarks, indicating it might be preferred for applications requiring robust file operations or that benefit from high I/O throughput. Additionally, Linode's lower cost per month for a similar configuration could make it a more economical choice for budget-conscious users. Thus, the best choice between these instances depends on the specific performance needs, with Vultr excelling in high-throughput data processing tasks and Linode providing a more balanced performance and cost-effectiveness for a range of general-purpose workloads.
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.