Linode Linode (4 GB) vs. Vultr High Frequency Intel (1 GB)
Welcome to another round of the VPS Showdown. Today I've spun up brand new instance from Linode and Vultr and ran my world famous suite of benchmarking scripts. All instances were running Ubuntu 24.04 LTS x64 and all resided in or around the New York / New Jersey area. Time to see who showed up today.
Overview
| Linode – (4 GB) | Vultr – High Frequency Intel (1 GB) | |
|---|---|---|
| Last Benchmarked | Mon, 01 Jun 2026 00:00:52 GMT | Sat, 30 May 2026 12: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 | $6.00 |
| RAM (GB) | 4 | 1 |
| CPU Cores | 2 | 1 |
| Storage (TB) | 80 | 32 |
| Storage Type | SSD | NVMe |
| Transfer (TB) | 4 | 1 |
CPU
| Linode – (4 GB) | Vultr – High Frequency Intel (1 GB) | |
|---|---|---|
| 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,792.05 |
| CPU Cache Size (KB) | 512.00 | 16,384.00 |
| BogoMips | 3,999.99 | 7,584.09 |
| Events per Second | 3,444.02 | 1,546.10 |
| Minimum Latency (ms) | 0.28 | 0.62 |
| Average Latency (ms) | 0.29 | 0.65 |
| Maximum Latency (ms) | 4.83 | 2.56 |
| 95th Percentile Latency (ms) | 0.3 | 0.74 |
Memory
Memory Read
| Linode – (4 GB) | Vultr – High Frequency Intel (1 GB) | |
|---|---|---|
| Operations per second | 5,349,213.60 | 7,548,382.97 |
| Mebibytes per second | 5,223.84 | 7,371.47 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 3.16 | 1.24 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Linode – (4 GB) | Vultr – High Frequency Intel (1 GB) | |
|---|---|---|
| Operations per second | 5,332,401.09 | 7,119,813.26 |
| Mebibytes per second | 5,207.42 | 6,952.94 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 3.25 | 0.15 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Linode – (4 GB) | Vultr – High Frequency Intel (1 GB) | |
|---|---|---|
| Reads per Second | 3,325.24 | 4,315.27 |
| Writes per Second | 2,216.89 | 2,876.81 |
| Fsyncs per Second | 7,095.98 | 9,210.59 |
| Read Mebibytes per Second | 51.96 | 67.43 |
| Written Mebibytes per Second | 34.64 | 44.95 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.08 | 0.06 |
| Maximum Latency (ms) | 13.12 | 1.42 |
| 95th Percentile Latency (ms) | 0.22 | 0.18 |
Mutex
| Linode – (4 GB) | Vultr – High Frequency Intel (1 GB) | |
|---|---|---|
| Minimum Latency (ms) | 864.93 | 1,097.72 |
| Average Latency (ms) | 931.61 | 1,103.69 |
| Maximum Latency (ms) | 968.34 | 1,109.05 |
| 95th Percentile Latency (ms) | 960.30 | 1,109.09 |
MySQL
MySQL Read-only
| Linode – (4 GB) | Vultr – High Frequency Intel (1 GB) | |
|---|---|---|
| Transactions per second | 5,919.00 | 10,280.00 |
| Queries per second | 59,190.00 | 102,800.00 |
| Minimum Latency (ms) | 1.29 | 0.9 |
| Average Latency (ms) | 1.69 | 0.97 |
| Maximum Latency (ms) | 8 | 5.51 |
| 95th Percentile Latency (ms) | 2.03 | 1.06 |
MySQL Write-only
| Linode – (4 GB) | Vultr – High Frequency Intel (1 GB) | |
|---|---|---|
| Transactions per second | 5,152.00 | 9,640.00 |
| Queries per second | 51,520.00 | 96,400.00 |
| Minimum Latency (ms) | 1.22 | 0.67 |
| Average Latency (ms) | 1.94 | 1.04 |
| Maximum Latency (ms) | 24.88 | 7.17 |
| 95th Percentile Latency (ms) | 2.52 | 1.32 |
MySQL Read/Write
| Linode – (4 GB) | Vultr – High Frequency Intel (1 GB) | |
|---|---|---|
| Transactions per second | 2,609.00 | 4,205.00 |
| Queries per second | 26,090.00 | 42,050.00 |
| Minimum Latency (ms) | 2.83 | 1.76 |
| Average Latency (ms) | 3.83 | 2.38 |
| Maximum Latency (ms) | 8.83 | 11.16 |
| 95th Percentile Latency (ms) | 4.74 | 3.13 |
MySQL INSERT
| Linode – (4 GB) | Vultr – High Frequency Intel (1 GB) | |
|---|---|---|
| Transactions per second | 7,493.00 | 17,283.00 |
| Queries per second | 74,930.00 | 172,830.00 |
| Minimum Latency (ms) | 0.73 | 0.38 |
| Average Latency (ms) | 1.33 | 0.58 |
| Maximum Latency (ms) | 15.06 | 5.55 |
| 95th Percentile Latency (ms) | 1.86 | 0.77 |
MySQL Bulk INSERT
| Linode – (4 GB) | Vultr – High Frequency Intel (1 GB) | |
|---|---|---|
| Transactions per second | 1,754,467.00 | 1,841,842.00 |
| Queries per second | 17,544,670.00 | 18,418,420.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0.01 |
| Maximum Latency (ms) | 418.75 | 261.29 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Linode – (4 GB) | Vultr – High Frequency Intel (1 GB) | |
|---|---|---|
| Transactions per second | 130,180.00 | 221,775.00 |
| Queries per second | 1,301,800.00 | 2,217,750.00 |
| Minimum Latency (ms) | 0.05 | 0.04 |
| Average Latency (ms) | 0.08 | 0.04 |
| Maximum Latency (ms) | 4.63 | 3.29 |
| 95th Percentile Latency (ms) | 0.1 | 0.06 |
MySQL SELECT (Random Points)
| Linode – (4 GB) | Vultr – High Frequency Intel (1 GB) | |
|---|---|---|
| Transactions per second | 8,212.00 | 10,706.00 |
| Queries per second | 82,120.00 | 107,060.00 |
| Minimum Latency (ms) | 0.33 | 0.31 |
| Average Latency (ms) | 1.22 | 0.93 |
| Maximum Latency (ms) | 11.27 | 3.42 |
| 95th Percentile Latency (ms) | 2.3 | 1.18 |
MySQL SELECT (Random Ranges)
| Linode – (4 GB) | Vultr – High Frequency Intel (1 GB) | |
|---|---|---|
| Transactions per second | 8,956.00 | 11,049.00 |
| Queries per second | 89,560.00 | 110,490.00 |
| Minimum Latency (ms) | 0.42 | 0.28 |
| Average Latency (ms) | 1.12 | 0.9 |
| Maximum Latency (ms) | 4.66 | 2.07 |
| 95th Percentile Latency (ms) | 1.44 | 1.16 |
MySQL UPDATE (Indexed)
| Linode – (4 GB) | Vultr – High Frequency Intel (1 GB) | |
|---|---|---|
| Transactions per second | 7,381.00 | 15,798.00 |
| Queries per second | 73,810.00 | 157,980.00 |
| Minimum Latency (ms) | 0.81 | 0.38 |
| Average Latency (ms) | 1.35 | 0.63 |
| Maximum Latency (ms) | 8.43 | 10.97 |
| 95th Percentile Latency (ms) | 1.76 | 0.86 |
MySQL UPDATE (Non-Indexed)
| Linode – (4 GB) | Vultr – High Frequency Intel (1 GB) | |
|---|---|---|
| Transactions per second | 7,379.00 | 15,941.00 |
| Queries per second | 73,790.00 | 159,410.00 |
| Minimum Latency (ms) | 0.82 | 0.39 |
| Average Latency (ms) | 1.35 | 0.63 |
| Maximum Latency (ms) | 7.2 | 3.15 |
| 95th Percentile Latency (ms) | 1.73 | 0.84 |
MySQL DELETE
| Linode – (4 GB) | Vultr – High Frequency Intel (1 GB) | |
|---|---|---|
| Transactions per second | 58,502.00 | 142,642.00 |
| Queries per second | 585,020.00 | 1,426,420.00 |
| Minimum Latency (ms) | 0.04 | 0.04 |
| Average Latency (ms) | 0.17 | 0.07 |
| Maximum Latency (ms) | 8.26 | 3.9 |
| 95th Percentile Latency (ms) | 1.14 | 0.1 |
Redis
| Linode – (4 GB) | Vultr – High Frequency Intel (1 GB) | |
|---|---|---|
| PING_INLINE per Second | 44,444.45 | 54,259.36 |
| PING_MBULK per Second | 42,158.52 | 54,764.51 |
| SET per Second | 43,725.41 | 54,259.36 |
| GET per Second | 43,084.88 | 51,786.64 |
| INCR per Second | 43,917.44 | 54,141.85 |
| LPUSH per Second | 44,169.61 | 54,318.30 |
| RPUSH per Second | 42,918.46 | 51,098.62 |
| LPOP per Second | 43,630.02 | 54,141.85 |
| RPOP per Second | 42,900.04 | 54,436.58 |
| SADD per Second | 43,066.32 | 55,218.11 |
| HSET per Second | 42,826.55 | 54,288.82 |
| SPOP per Second | 43,821.21 | 55,524.71 |
| ZADD per Second | 43,706.29 | 54,674.69 |
| ZPOPMIN per Second | 46,554.93 | 54,945.05 |
| LRANGE_100 (first 100 elements) per Second | 30,084.24 | 35,014.01 |
| LRANGE_300 (first 300 elements) per Second | 21,141.65 | 20,161.29 |
| LRANGE_500 (first 500 elements) per Second | 17,825.31 | 14,124.29 |
| LRANGE_600 (first 600 elements) per Second | 15,969.34 | 11,522.06 |
| MSET (10 keys) per Second | 45,578.85 | 44,702.73 |
Redis Average Latency (ms)
| Linode – (4 GB) | Vultr – High Frequency Intel (1 GB) | |
|---|---|---|
| PING_INLINE | 0.58 | 0.60 |
| PING_MBULK | 0.61 | 0.59 |
| SET | 0.59 | 0.60 |
| GET | 0.60 | 0.63 |
| INCR | 0.59 | 0.60 |
| LPUSH | 0.58 | 0.60 |
| RPUSH | 0.60 | 0.64 |
| LPOP | 0.59 | 0.60 |
| RPOP | 0.60 | 0.60 |
| SADD | 0.60 | 0.58 |
| HSET | 0.60 | 0.60 |
| SPOP | 0.59 | 0.58 |
| ZADD | 0.59 | 0.59 |
| ZPOPMIN | 0.55 | 0.59 |
| LRANGE_100 (first 100 elements) | 0.89 | 0.98 |
| LRANGE_300 (first 300 elements) | 1.25 | 1.73 |
| LRANGE_500 (first 500 elements) | 1.50 | 2.55 |
| LRANGE_600 (first 600 elements) | 1.59 | 3.12 |
| MSET (10 keys) | 0.57 | 0.78 |
Conclusion
From the friendly robots:
Analyzing the benchmark results from both providers, the Linode instance (4 GB) demonstrates solid overall performance with high Redis request rates, efficient CPU handling, and strong file I/O throughput, making it particularly suited for CPU-intensive tasks and workloads that require fast random read/write operations. Conversely, the Vultr High Frequency Intel (1 GB) instance shows superior Redis performance in terms of requests per second, indicating it might be more optimal for high-throughput scenarios involving in-memory data operations. However, it lags behind in CPU handling, file I/O throughput, and memory operations compared to Linode, making it less ideal for heavy computational tasks. Thus, the Linode instance is better suited for applications demanding balanced CPU and memory performance, while the Vultr instance shines in scenarios requiring high Redis throughput with modest resource requirements.
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.