Linode Linode (4 GB) vs. Vultr High Frequency Intel (8 GB, 3 Cores)
Fresh benchmarks coming at ya. Today I've spun up brand new instance from Linode and Vultr and did some benchmarking. Each instance was running Ubuntu 24.04 LTS x64 and all resided in or around the New York / New Jersey area. Let's get into the numbers.
Overview
| Linode – (4 GB) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Last Benchmarked | Mon, 01 Jun 2026 00:00:52 GMT | Mon, 01 Jun 2026 04: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 | $24.00 | $48.00 |
| RAM (GB) | 4 | 8 |
| CPU Cores | 2 | 3 |
| Storage (TB) | 80 | 256 |
| Storage Type | SSD | NVMe |
| Transfer (TB) | 4 | 4 |
CPU
| Linode – (4 GB) | Vultr – High Frequency Intel (8 GB, 3 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.95 |
| CPU Cache Size (KB) | 512.00 | 16,384.00 |
| BogoMips | 3,999.99 | 7,583.90 |
| Events per Second | 3,444.02 | 1,574.94 |
| Minimum Latency (ms) | 0.28 | 0.6 |
| Average Latency (ms) | 0.29 | 0.63 |
| Maximum Latency (ms) | 4.83 | 3.7 |
| 95th Percentile Latency (ms) | 0.3 | 0.67 |
Memory
Memory Read
| Linode – (4 GB) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Operations per second | 5,349,213.60 | 7,301,051.87 |
| Mebibytes per second | 5,223.84 | 7,129.93 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 3.16 | 0.57 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Linode – (4 GB) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Operations per second | 5,332,401.09 | 7,839,874.03 |
| Mebibytes per second | 5,207.42 | 7,656.13 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 3.25 | 0.16 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Linode – (4 GB) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Reads per Second | 3,325.24 | 8,171.93 |
| Writes per Second | 2,216.89 | 5,447.96 |
| Fsyncs per Second | 7,095.98 | 17,434.06 |
| Read Mebibytes per Second | 51.96 | 127.69 |
| Written Mebibytes per Second | 34.64 | 85.12 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.08 | 0.03 |
| Maximum Latency (ms) | 13.12 | 7.37 |
| 95th Percentile Latency (ms) | 0.22 | 0.11 |
Mutex
| Linode – (4 GB) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 864.93 | 261.09 |
| Average Latency (ms) | 931.61 | 372.41 |
| Maximum Latency (ms) | 968.34 | 402.38 |
| 95th Percentile Latency (ms) | 960.30 | 404.61 |
MySQL
MySQL Read-only
| Linode – (4 GB) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 5,919.00 | 10,533.00 |
| Queries per second | 59,190.00 | 105,330.00 |
| Minimum Latency (ms) | 1.29 | 0.88 |
| Average Latency (ms) | 1.69 | 0.95 |
| Maximum Latency (ms) | 8 | 2.32 |
| 95th Percentile Latency (ms) | 2.03 | 1.04 |
MySQL Write-only
| Linode – (4 GB) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 5,152.00 | 9,133.00 |
| Queries per second | 51,520.00 | 91,330.00 |
| Minimum Latency (ms) | 1.22 | 0.71 |
| Average Latency (ms) | 1.94 | 1.09 |
| Maximum Latency (ms) | 24.88 | 11.49 |
| 95th Percentile Latency (ms) | 2.52 | 1.34 |
MySQL Read/Write
| Linode – (4 GB) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 2,609.00 | 4,674.00 |
| Queries per second | 26,090.00 | 46,740.00 |
| Minimum Latency (ms) | 2.83 | 1.65 |
| Average Latency (ms) | 3.83 | 2.14 |
| Maximum Latency (ms) | 8.83 | 4.78 |
| 95th Percentile Latency (ms) | 4.74 | 2.52 |
MySQL INSERT
| Linode – (4 GB) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 7,493.00 | 16,322.00 |
| Queries per second | 74,930.00 | 163,220.00 |
| Minimum Latency (ms) | 0.73 | 0.38 |
| Average Latency (ms) | 1.33 | 0.61 |
| Maximum Latency (ms) | 15.06 | 2.29 |
| 95th Percentile Latency (ms) | 1.86 | 0.84 |
MySQL Bulk INSERT
| Linode – (4 GB) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 1,754,467.00 | 2,437,722.00 |
| Queries per second | 17,544,670.00 | 24,377,220.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0 |
| Maximum Latency (ms) | 418.75 | 207.9 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Linode – (4 GB) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 130,180.00 | 235,748.00 |
| Queries per second | 1,301,800.00 | 2,357,480.00 |
| Minimum Latency (ms) | 0.05 | 0.03 |
| Average Latency (ms) | 0.08 | 0.04 |
| Maximum Latency (ms) | 4.63 | 0.19 |
| 95th Percentile Latency (ms) | 0.1 | 0.05 |
MySQL SELECT (Random Points)
| Linode – (4 GB) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 8,212.00 | 12,117.00 |
| Queries per second | 82,120.00 | 121,170.00 |
| Minimum Latency (ms) | 0.33 | 0.3 |
| Average Latency (ms) | 1.22 | 0.82 |
| Maximum Latency (ms) | 11.27 | 3.79 |
| 95th Percentile Latency (ms) | 2.3 | 1.04 |
MySQL SELECT (Random Ranges)
| Linode – (4 GB) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 8,956.00 | 10,468.00 |
| Queries per second | 89,560.00 | 104,680.00 |
| Minimum Latency (ms) | 0.42 | 0.29 |
| Average Latency (ms) | 1.12 | 0.95 |
| Maximum Latency (ms) | 4.66 | 3.11 |
| 95th Percentile Latency (ms) | 1.44 | 1.23 |
MySQL UPDATE (Indexed)
| Linode – (4 GB) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 7,381.00 | 15,904.00 |
| Queries per second | 73,810.00 | 159,040.00 |
| Minimum Latency (ms) | 0.81 | 0.38 |
| Average Latency (ms) | 1.35 | 0.63 |
| Maximum Latency (ms) | 8.43 | 15.72 |
| 95th Percentile Latency (ms) | 1.76 | 0.83 |
MySQL UPDATE (Non-Indexed)
| Linode – (4 GB) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 7,379.00 | 16,320.00 |
| Queries per second | 73,790.00 | 163,200.00 |
| Minimum Latency (ms) | 0.82 | 0.38 |
| Average Latency (ms) | 1.35 | 0.61 |
| Maximum Latency (ms) | 7.2 | 1.97 |
| 95th Percentile Latency (ms) | 1.73 | 0.86 |
MySQL DELETE
| Linode – (4 GB) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 58,502.00 | 140,752.00 |
| Queries per second | 585,020.00 | 1,407,520.00 |
| Minimum Latency (ms) | 0.04 | 0.03 |
| Average Latency (ms) | 0.17 | 0.07 |
| Maximum Latency (ms) | 8.26 | 5.16 |
| 95th Percentile Latency (ms) | 1.14 | 0.09 |
Redis
| Linode – (4 GB) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| PING_INLINE per Second | 44,444.45 | 88,339.23 |
| PING_MBULK per Second | 42,158.52 | 86,655.11 |
| SET per Second | 43,725.41 | 88,417.33 |
| GET per Second | 43,084.88 | 88,967.98 |
| INCR per Second | 43,917.44 | 88,417.33 |
| LPUSH per Second | 44,169.61 | 88,417.33 |
| RPUSH per Second | 42,918.46 | 88,339.23 |
| LPOP per Second | 43,630.02 | 88,967.98 |
| RPOP per Second | 42,900.04 | 88,339.23 |
| SADD per Second | 43,066.32 | 87,108.02 |
| HSET per Second | 42,826.55 | 88,183.43 |
| SPOP per Second | 43,821.21 | 86,880.97 |
| ZADD per Second | 43,706.29 | 88,261.25 |
| ZPOPMIN per Second | 46,554.93 | 88,028.16 |
| LRANGE_100 (first 100 elements) per Second | 30,084.24 | 66,050.20 |
| LRANGE_300 (first 300 elements) per Second | 21,141.65 | 36,337.21 |
| LRANGE_500 (first 500 elements) per Second | 17,825.31 | 25,575.45 |
| LRANGE_600 (first 600 elements) per Second | 15,969.34 | 23,089.36 |
| MSET (10 keys) per Second | 45,578.85 | 86,880.97 |
Redis Average Latency (ms)
| Linode – (4 GB) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| PING_INLINE | 0.58 | 0.29 |
| PING_MBULK | 0.61 | 0.30 |
| SET | 0.59 | 0.29 |
| GET | 0.60 | 0.29 |
| INCR | 0.59 | 0.29 |
| LPUSH | 0.58 | 0.29 |
| RPUSH | 0.60 | 0.29 |
| LPOP | 0.59 | 0.29 |
| RPOP | 0.60 | 0.29 |
| SADD | 0.60 | 0.30 |
| HSET | 0.60 | 0.29 |
| SPOP | 0.59 | 0.30 |
| ZADD | 0.59 | 0.29 |
| ZPOPMIN | 0.55 | 0.29 |
| LRANGE_100 (first 100 elements) | 0.89 | 0.40 |
| LRANGE_300 (first 300 elements) | 1.25 | 0.72 |
| LRANGE_500 (first 500 elements) | 1.50 | 1.03 |
| LRANGE_600 (first 600 elements) | 1.59 | 1.16 |
| MSET (10 keys) | 0.57 | 0.30 |
Conclusion
From the friendly robots:
Based on the benchmark results, the Vultr High Frequency Intel (8 GB, 3 Cores) instance outperforms the Linode (4 GB) in nearly all tested metrics, particularly in CPU-intensive and Redis operations. Vultr achieves significantly higher request rates per second across various Redis commands, suggesting it has better throughput and lower latency for these tasks. The file I/O operations also favor Vultr, with faster read and write speeds and lower latencies. While Linode excels in MySQL OLTP operations and lower latency in memory operations, Vultr’s superior CPU and memory performance make it a better choice for applications requiring high throughput and low latency, such as web servers, high-traffic databases, and data processing tasks. On the other hand, Linode may be more suitable for applications where MySQL operations are critical and cost-effectiveness is a priority.
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.