Linode Linode (8 GB) vs. Vultr High Frequency Intel (2 GB, 2 Cores)
Same showdown, different day. 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 were created in or around the New York / New Jersey area. Without further ado, here's the results.
Overview
| Linode – (8 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Last Benchmarked | Mon, 01 Jun 2026 03: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 | $48.00 | $18.00 |
| RAM (GB) | 8 | 2 |
| CPU Cores | 4 | 2 |
| Storage (TB) | 160 | 80 |
| Storage Type | SSD | NVMe |
| Transfer (TB) | 5 | 3 |
CPU
| Linode – (8 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Vendor | AuthenticAMD | GenuineIntel |
| Model Name | AMD EPYC 7542 32-Core Processor | Intel Core Processor (Skylake, IBRS, no TSX) |
| Clock Speed (MHz) | 2,900.00 | 3,791.98 |
| CPU Cache Size (KB) | 512.00 | 16,384.00 |
| BogoMips | 5,799.99 | 7,583.95 |
| Events per Second | 1,661.57 | 1,552.05 |
| Minimum Latency (ms) | 0.58 | 0.62 |
| Average Latency (ms) | 0.6 | 0.64 |
| Maximum Latency (ms) | 3.57 | 4.61 |
| 95th Percentile Latency (ms) | 0.63 | 0.69 |
Memory
Memory Read
| Linode – (8 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 5,533,114.95 | 7,875,668.83 |
| Mebibytes per second | 5,403.43 | 7,691.08 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 1.96 | 0.12 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Linode – (8 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 5,426,984.96 | 7,729,812.11 |
| Mebibytes per second | 5,299.79 | 7,548.64 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 4 | 0.16 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Linode – (8 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Reads per Second | 5,520.56 | 4,671.85 |
| Writes per Second | 3,680.37 | 3,114.56 |
| Fsyncs per Second | 11,779.39 | 9,976.90 |
| Read Mebibytes per Second | 86.26 | 73.00 |
| Written Mebibytes per Second | 57.51 | 48.67 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.05 | 0.06 |
| Maximum Latency (ms) | 3.48 | 2.76 |
| 95th Percentile Latency (ms) | 0.17 | 0.17 |
Mutex
| Linode – (8 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 296.37 | 543.27 |
| Average Latency (ms) | 381.09 | 554.74 |
| Maximum Latency (ms) | 428.18 | 563.70 |
| 95th Percentile Latency (ms) | 427.07 | 559.50 |
MySQL
MySQL Read-only
| Linode – (8 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 6,942.00 | 10,621.00 |
| Queries per second | 69,420.00 | 106,210.00 |
| Minimum Latency (ms) | 1.2 | 0.86 |
| Average Latency (ms) | 1.44 | 0.94 |
| Maximum Latency (ms) | 4.62 | 2.5 |
| 95th Percentile Latency (ms) | 1.58 | 1.03 |
MySQL Write-only
| Linode – (8 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 6,324.00 | 10,229.00 |
| Queries per second | 63,240.00 | 102,290.00 |
| Minimum Latency (ms) | 1.02 | 0.64 |
| Average Latency (ms) | 1.58 | 0.98 |
| Maximum Latency (ms) | 22.06 | 2.08 |
| 95th Percentile Latency (ms) | 2.07 | 1.23 |
MySQL Read/Write
| Linode – (8 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 3,352.00 | 5,072.00 |
| Queries per second | 33,520.00 | 50,720.00 |
| Minimum Latency (ms) | 2.25 | 1.59 |
| Average Latency (ms) | 2.98 | 1.97 |
| Maximum Latency (ms) | 6.85 | 3.94 |
| 95th Percentile Latency (ms) | 3.49 | 2.39 |
MySQL INSERT
| Linode – (8 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,779.00 | 16,038.00 |
| Queries per second | 87,790.00 | 160,380.00 |
| Minimum Latency (ms) | 0.7 | 0.38 |
| Average Latency (ms) | 1.14 | 0.62 |
| Maximum Latency (ms) | 14.61 | 13.18 |
| 95th Percentile Latency (ms) | 1.42 | 0.8 |
MySQL Bulk INSERT
| Linode – (8 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 1,783,592.00 | 2,424,342.00 |
| Queries per second | 17,835,920.00 | 24,243,420.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0 |
| Maximum Latency (ms) | 292.01 | 205.81 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Linode – (8 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 160,295.00 | 241,313.00 |
| Queries per second | 1,602,950.00 | 2,413,130.00 |
| Minimum Latency (ms) | 0.04 | 0.03 |
| Average Latency (ms) | 0.06 | 0.04 |
| Maximum Latency (ms) | 3.19 | 0.76 |
| 95th Percentile Latency (ms) | 0.08 | 0.05 |
MySQL SELECT (Random Points)
| Linode – (8 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 9,140.00 | 12,080.00 |
| Queries per second | 91,400.00 | 120,800.00 |
| Minimum Latency (ms) | 0.4 | 0.21 |
| Average Latency (ms) | 1.09 | 0.83 |
| Maximum Latency (ms) | 4.24 | 3.31 |
| 95th Percentile Latency (ms) | 1.39 | 1.04 |
MySQL SELECT (Random Ranges)
| Linode – (8 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 7,642.00 | 10,527.00 |
| Queries per second | 76,420.00 | 105,270.00 |
| Minimum Latency (ms) | 0.47 | 0.16 |
| Average Latency (ms) | 1.31 | 0.95 |
| Maximum Latency (ms) | 4.75 | 3.25 |
| 95th Percentile Latency (ms) | 1.67 | 1.23 |
MySQL UPDATE (Indexed)
| Linode – (8 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 9,081.00 | 17,123.00 |
| Queries per second | 90,810.00 | 171,230.00 |
| Minimum Latency (ms) | 0.68 | 0.38 |
| Average Latency (ms) | 1.1 | 0.58 |
| Maximum Latency (ms) | 4.8 | 2 |
| 95th Percentile Latency (ms) | 1.3 | 0.78 |
MySQL UPDATE (Non-Indexed)
| Linode – (8 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 7,997.00 | 16,979.00 |
| Queries per second | 79,970.00 | 169,790.00 |
| Minimum Latency (ms) | 0.67 | 0.38 |
| Average Latency (ms) | 1.25 | 0.59 |
| Maximum Latency (ms) | 23.14 | 4.13 |
| 95th Percentile Latency (ms) | 1.67 | 0.8 |
MySQL DELETE
| Linode – (8 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 93,716.00 | 156,424.00 |
| Queries per second | 937,160.00 | 1,564,240.00 |
| Minimum Latency (ms) | 0.04 | 0.03 |
| Average Latency (ms) | 0.11 | 0.06 |
| Maximum Latency (ms) | 6.7 | 4.87 |
| 95th Percentile Latency (ms) | 0.12 | 0.07 |
Redis
| Linode – (8 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE per Second | 61,728.39 | 88,652.48 |
| PING_MBULK per Second | 60,204.70 | 89,605.73 |
| SET per Second | 61,957.87 | 90,171.33 |
| GET per Second | 61,199.51 | 90,579.71 |
| INCR per Second | 62,266.50 | 90,744.10 |
| LPUSH per Second | 62,695.92 | 90,497.73 |
| RPUSH per Second | 67,159.17 | 90,415.91 |
| LPOP per Second | 62,460.96 | 90,909.09 |
| RPOP per Second | 60,606.06 | 90,661.83 |
| SADD per Second | 60,716.46 | 90,252.70 |
| HSET per Second | 60,532.69 | 90,415.91 |
| SPOP per Second | 60,679.61 | 89,928.05 |
| ZADD per Second | 61,804.70 | 90,415.91 |
| ZPOPMIN per Second | 61,425.06 | 90,009.01 |
| LRANGE_100 (first 100 elements) per Second | 49,236.83 | 66,533.60 |
| LRANGE_300 (first 300 elements) per Second | 27,839.64 | 36,179.45 |
| LRANGE_500 (first 500 elements) per Second | 20,614.31 | 26,239.83 |
| LRANGE_600 (first 600 elements) per Second | 16,931.93 | 22,547.91 |
| MSET (10 keys) per Second | 64,766.84 | 88,105.73 |
Redis Average Latency (ms)
| Linode – (8 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE | 0.42 | 0.30 |
| PING_MBULK | 0.43 | 0.29 |
| SET | 0.42 | 0.29 |
| GET | 0.42 | 0.29 |
| INCR | 0.41 | 0.28 |
| LPUSH | 0.41 | 0.29 |
| RPUSH | 0.38 | 0.29 |
| LPOP | 0.41 | 0.28 |
| RPOP | 0.43 | 0.28 |
| SADD | 0.43 | 0.29 |
| HSET | 0.43 | 0.29 |
| SPOP | 0.43 | 0.29 |
| ZADD | 0.42 | 0.29 |
| ZPOPMIN | 0.42 | 0.29 |
| LRANGE_100 (first 100 elements) | 0.52 | 0.39 |
| LRANGE_300 (first 300 elements) | 0.93 | 0.71 |
| LRANGE_500 (first 500 elements) | 1.25 | 0.97 |
| LRANGE_600 (first 600 elements) | 1.52 | 1.14 |
| MSET (10 keys) | 0.40 | 0.30 |
Conclusion
From the friendly robots:
After analyzing the benchmark results for the Linode (8 GB) and Vultr (2 GB, 2 Cores) instances, it's evident that the Linode instance, powered by an AMD EPYC processor, outperforms the Vultr instance with its Intel Core processor in most metrics. The Linode instance demonstrates higher Redis request rates per second, superior CPU and file I/O performance, and more efficient memory handling, especially noticeable in memory-intensive tasks and complex Redis commands like LRANGE. Conversely, the Vultr instance excels in handling high-throughput Redis operations, displaying remarkable rates per second for simple commands such as PING, SET, and GET, despite having less CPU power and RAM. Thus, the Linode instance is ideal for workloads that benefit from higher CPU counts and more memory, like multi-threaded applications and I/O-heavy tasks, while the Vultr instance is better suited for scenarios requiring very high Redis throughput with simpler 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.