Linode Linode (4 GB) vs. Vultr High Frequency Intel (4 GB, 2 Cores)
My friend, I'm so glad you're here! 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. Without further ado, here's the results.
Overview
| Linode – (4 GB) | Vultr – High Frequency Intel (4 GB, 2 Cores) | |
|---|---|---|
| Last Benchmarked | Mon, 01 Jun 2026 00:00:52 GMT | Sun, 31 May 2026 15: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 | $24.00 |
| RAM (GB) | 4 | 4 |
| CPU Cores | 2 | 2 |
| Storage (TB) | 80 | 128 |
| Storage Type | SSD | NVMe |
| Transfer (TB) | 4 | 3 |
CPU
| Linode – (4 GB) | Vultr – High Frequency Intel (4 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.97 |
| CPU Cache Size (KB) | 512.00 | 16,384.00 |
| BogoMips | 3,999.99 | 7,583.94 |
| Events per Second | 3,444.02 | 1,574.56 |
| Minimum Latency (ms) | 0.28 | 0.62 |
| Average Latency (ms) | 0.29 | 0.63 |
| Maximum Latency (ms) | 4.83 | 2.75 |
| 95th Percentile Latency (ms) | 0.3 | 0.68 |
Memory
Memory Read
| Linode – (4 GB) | Vultr – High Frequency Intel (4 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 5,349,213.60 | 7,748,150.36 |
| Mebibytes per second | 5,223.84 | 7,566.55 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 3.16 | 0.07 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Linode – (4 GB) | Vultr – High Frequency Intel (4 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 5,332,401.09 | 7,774,132.12 |
| Mebibytes per second | 5,207.42 | 7,591.93 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 3.25 | 0.27 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Linode – (4 GB) | Vultr – High Frequency Intel (4 GB, 2 Cores) | |
|---|---|---|
| Reads per Second | 3,325.24 | 7,795.87 |
| Writes per Second | 2,216.89 | 5,197.25 |
| Fsyncs per Second | 7,095.98 | 16,639.28 |
| Read Mebibytes per Second | 51.96 | 121.81 |
| Written Mebibytes per Second | 34.64 | 81.21 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.08 | 0.03 |
| Maximum Latency (ms) | 13.12 | 0.85 |
| 95th Percentile Latency (ms) | 0.22 | 0.12 |
Mutex
| Linode – (4 GB) | Vultr – High Frequency Intel (4 GB, 2 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 864.93 | 508.91 |
| Average Latency (ms) | 931.61 | 536.68 |
| Maximum Latency (ms) | 968.34 | 555.84 |
| 95th Percentile Latency (ms) | 960.30 | 559.50 |
MySQL
MySQL Read-only
| Linode – (4 GB) | Vultr – High Frequency Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 5,919.00 | 10,239.00 |
| Queries per second | 59,190.00 | 102,390.00 |
| Minimum Latency (ms) | 1.29 | 0.89 |
| Average Latency (ms) | 1.69 | 0.98 |
| Maximum Latency (ms) | 8 | 3.09 |
| 95th Percentile Latency (ms) | 2.03 | 1.1 |
MySQL Write-only
| Linode – (4 GB) | Vultr – High Frequency Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 5,152.00 | 9,867.00 |
| Queries per second | 51,520.00 | 98,670.00 |
| Minimum Latency (ms) | 1.22 | 0.67 |
| Average Latency (ms) | 1.94 | 1.01 |
| Maximum Latency (ms) | 24.88 | 2.05 |
| 95th Percentile Latency (ms) | 2.52 | 1.27 |
MySQL Read/Write
| Linode – (4 GB) | Vultr – High Frequency Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 2,609.00 | 4,833.00 |
| Queries per second | 26,090.00 | 48,330.00 |
| Minimum Latency (ms) | 2.83 | 1.66 |
| Average Latency (ms) | 3.83 | 2.07 |
| Maximum Latency (ms) | 8.83 | 13 |
| 95th Percentile Latency (ms) | 4.74 | 2.48 |
MySQL INSERT
| Linode – (4 GB) | Vultr – High Frequency Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 7,493.00 | 16,634.00 |
| Queries per second | 74,930.00 | 166,340.00 |
| Minimum Latency (ms) | 0.73 | 0.4 |
| Average Latency (ms) | 1.33 | 0.6 |
| Maximum Latency (ms) | 15.06 | 11.65 |
| 95th Percentile Latency (ms) | 1.86 | 0.8 |
MySQL Bulk INSERT
| Linode – (4 GB) | Vultr – High Frequency Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 1,754,467.00 | 2,395,217.00 |
| Queries per second | 17,544,670.00 | 23,952,170.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0 |
| Maximum Latency (ms) | 418.75 | 203.97 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Linode – (4 GB) | Vultr – High Frequency Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 130,180.00 | 234,845.00 |
| Queries per second | 1,301,800.00 | 2,348,450.00 |
| Minimum Latency (ms) | 0.05 | 0.03 |
| Average Latency (ms) | 0.08 | 0.04 |
| Maximum Latency (ms) | 4.63 | 0.65 |
| 95th Percentile Latency (ms) | 0.1 | 0.05 |
MySQL SELECT (Random Points)
| Linode – (4 GB) | Vultr – High Frequency Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,212.00 | 10,869.00 |
| Queries per second | 82,120.00 | 108,690.00 |
| Minimum Latency (ms) | 0.33 | 0.26 |
| Average Latency (ms) | 1.22 | 0.92 |
| Maximum Latency (ms) | 11.27 | 2.74 |
| 95th Percentile Latency (ms) | 2.3 | 1.34 |
MySQL SELECT (Random Ranges)
| Linode – (4 GB) | Vultr – High Frequency Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,956.00 | 10,176.00 |
| Queries per second | 89,560.00 | 101,760.00 |
| Minimum Latency (ms) | 0.42 | 0.38 |
| Average Latency (ms) | 1.12 | 0.98 |
| Maximum Latency (ms) | 4.66 | 3.71 |
| 95th Percentile Latency (ms) | 1.44 | 1.3 |
MySQL UPDATE (Indexed)
| Linode – (4 GB) | Vultr – High Frequency Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 7,381.00 | 16,370.00 |
| Queries per second | 73,810.00 | 163,700.00 |
| Minimum Latency (ms) | 0.81 | 0.39 |
| Average Latency (ms) | 1.35 | 0.61 |
| Maximum Latency (ms) | 8.43 | 1.95 |
| 95th Percentile Latency (ms) | 1.76 | 0.81 |
MySQL UPDATE (Non-Indexed)
| Linode – (4 GB) | Vultr – High Frequency Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 7,379.00 | 16,970.00 |
| Queries per second | 73,790.00 | 169,700.00 |
| Minimum Latency (ms) | 0.82 | 0.39 |
| Average Latency (ms) | 1.35 | 0.59 |
| Maximum Latency (ms) | 7.2 | 1.83 |
| 95th Percentile Latency (ms) | 1.73 | 0.81 |
MySQL DELETE
| Linode – (4 GB) | Vultr – High Frequency Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 58,502.00 | 155,757.00 |
| Queries per second | 585,020.00 | 1,557,570.00 |
| Minimum Latency (ms) | 0.04 | 0.03 |
| Average Latency (ms) | 0.17 | 0.06 |
| Maximum Latency (ms) | 8.26 | 2.85 |
| 95th Percentile Latency (ms) | 1.14 | 0.08 |
Redis
| Linode – (4 GB) | Vultr – High Frequency Intel (4 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE per Second | 44,444.45 | 85,910.65 |
| PING_MBULK per Second | 42,158.52 | 87,796.30 |
| SET per Second | 43,725.41 | 89,047.20 |
| GET per Second | 43,084.88 | 88,105.73 |
| INCR per Second | 43,917.44 | 87,032.20 |
| LPUSH per Second | 44,169.61 | 87,032.20 |
| RPUSH per Second | 42,918.46 | 88,573.96 |
| LPOP per Second | 43,630.02 | 88,417.33 |
| RPOP per Second | 42,900.04 | 89,525.52 |
| SADD per Second | 43,066.32 | 88,183.43 |
| HSET per Second | 42,826.55 | 89,047.20 |
| SPOP per Second | 43,821.21 | 86,956.52 |
| ZADD per Second | 43,706.29 | 88,183.43 |
| ZPOPMIN per Second | 46,554.93 | 87,260.03 |
| LRANGE_100 (first 100 elements) per Second | 30,084.24 | 63,251.11 |
| LRANGE_300 (first 300 elements) per Second | 21,141.65 | 34,940.60 |
| LRANGE_500 (first 500 elements) per Second | 17,825.31 | 25,700.33 |
| LRANGE_600 (first 600 elements) per Second | 15,969.34 | 22,537.75 |
| MSET (10 keys) per Second | 45,578.85 | 85,836.91 |
Redis Average Latency (ms)
| Linode – (4 GB) | Vultr – High Frequency Intel (4 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE | 0.58 | 0.31 |
| PING_MBULK | 0.61 | 0.29 |
| SET | 0.59 | 0.29 |
| GET | 0.60 | 0.29 |
| INCR | 0.59 | 0.30 |
| LPUSH | 0.58 | 0.30 |
| RPUSH | 0.60 | 0.29 |
| LPOP | 0.59 | 0.29 |
| RPOP | 0.60 | 0.29 |
| SADD | 0.60 | 0.29 |
| HSET | 0.60 | 0.29 |
| SPOP | 0.59 | 0.30 |
| ZADD | 0.59 | 0.30 |
| ZPOPMIN | 0.55 | 0.30 |
| LRANGE_100 (first 100 elements) | 0.89 | 0.46 |
| LRANGE_300 (first 300 elements) | 1.25 | 0.74 |
| LRANGE_500 (first 500 elements) | 1.50 | 0.99 |
| LRANGE_600 (first 600 elements) | 1.59 | 1.15 |
| MSET (10 keys) | 0.57 | 0.30 |
Conclusion
From the friendly robots:
Upon comparing the benchmarks for the Linode and Vultr instances, it's clear that both providers offer high-performance computing options suitable for different workloads. The Linode instance, with its powerful AMD EPYC processor, excels in tasks requiring high I/O throughput and memory operations, with impressive read and write speeds, as well as excellent Redis and MySQL performance metrics. The Vultr instance, powered by a more cost-effective Intel Core processor, showcases remarkable overall performance, especially in Redis operations where it achieves significantly higher requests per second with lower latencies, indicating superior efficiency in memory-intensive tasks. For users prioritizing CPU-intensive and high-concurrency tasks with lower latency, the Vultr instance appears to be the better choice, while the Linode instance would be ideal for workloads that benefit from higher storage throughput and robust memory handling.
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.