Linode Linode (4 GB) vs. Vultr High Performance Intel (8 GB, 4 Cores)
My friend, I'm so glad you're here! Today I've spun up brand new instance from Linode and Vultr and ran my world famous suite of benchmarking scripts. Each instance was spun up with 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 Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Last Benchmarked | Mon, 01 Jun 2026 00:00:52 GMT | Sun, 31 May 2026 03: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 | 4 |
| Storage (TB) | 80 | 180 |
| Storage Type | SSD | NVMe |
| Transfer (TB) | 4 | 6 |
CPU
| Linode – (4 GB) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Vendor | AuthenticAMD | GenuineIntel |
| Model Name | AMD EPYC 7713 64-Core Processor | Intel Xeon Processor (Cascadelake) |
| Clock Speed (MHz) | 2,000.00 | 2,893.17 |
| CPU Cache Size (KB) | 512.00 | 16,384.00 |
| BogoMips | 3,999.99 | 5,786.33 |
| Events per Second | 3,444.02 | 1,164.11 |
| Minimum Latency (ms) | 0.28 | 0.83 |
| Average Latency (ms) | 0.29 | 0.86 |
| Maximum Latency (ms) | 4.83 | 1.81 |
| 95th Percentile Latency (ms) | 0.3 | 0.9 |
Memory
Memory Read
| Linode – (4 GB) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Operations per second | 5,349,213.60 | 5,268,671.27 |
| Mebibytes per second | 5,223.84 | 5,145.19 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 3.16 | 0.85 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Linode – (4 GB) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Operations per second | 5,332,401.09 | 5,300,398.23 |
| Mebibytes per second | 5,207.42 | 5,176.17 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 3.25 | 0.29 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Linode – (4 GB) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Reads per Second | 3,325.24 | 8,120.73 |
| Writes per Second | 2,216.89 | 5,413.82 |
| Fsyncs per Second | 7,095.98 | 17,334.39 |
| Read Mebibytes per Second | 51.96 | 126.89 |
| Written Mebibytes per Second | 34.64 | 84.59 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.08 | 0.03 |
| Maximum Latency (ms) | 13.12 | 16.4 |
| 95th Percentile Latency (ms) | 0.22 | 0.1 |
Mutex
| Linode – (4 GB) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 864.93 | 197.88 |
| Average Latency (ms) | 931.61 | 357.16 |
| Maximum Latency (ms) | 968.34 | 411.19 |
| 95th Percentile Latency (ms) | 960.30 | 411.96 |
MySQL
MySQL Read-only
| Linode – (4 GB) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 5,919.00 | 7,388.00 |
| Queries per second | 59,190.00 | 73,880.00 |
| Minimum Latency (ms) | 1.29 | 1.14 |
| Average Latency (ms) | 1.69 | 1.35 |
| Maximum Latency (ms) | 8 | 3.22 |
| 95th Percentile Latency (ms) | 2.03 | 1.7 |
MySQL Write-only
| Linode – (4 GB) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 5,152.00 | 7,997.00 |
| Queries per second | 51,520.00 | 79,970.00 |
| Minimum Latency (ms) | 1.22 | 0.87 |
| Average Latency (ms) | 1.94 | 1.25 |
| Maximum Latency (ms) | 24.88 | 3.16 |
| 95th Percentile Latency (ms) | 2.52 | 1.55 |
MySQL Read/Write
| Linode – (4 GB) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 2,609.00 | 3,262.00 |
| Queries per second | 26,090.00 | 32,620.00 |
| Minimum Latency (ms) | 2.83 | 2.17 |
| Average Latency (ms) | 3.83 | 3.06 |
| Maximum Latency (ms) | 8.83 | 7.36 |
| 95th Percentile Latency (ms) | 4.74 | 3.82 |
MySQL INSERT
| Linode – (4 GB) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 7,493.00 | 12,898.00 |
| Queries per second | 74,930.00 | 128,980.00 |
| Minimum Latency (ms) | 0.73 | 0.44 |
| Average Latency (ms) | 1.33 | 0.77 |
| Maximum Latency (ms) | 15.06 | 11.56 |
| 95th Percentile Latency (ms) | 1.86 | 1.04 |
MySQL Bulk INSERT
| Linode – (4 GB) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 1,754,467.00 | 1,434,092.00 |
| Queries per second | 17,544,670.00 | 14,340,920.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0.01 |
| Maximum Latency (ms) | 418.75 | 363.55 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Linode – (4 GB) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 130,180.00 | 190,206.00 |
| Queries per second | 1,301,800.00 | 1,902,060.00 |
| Minimum Latency (ms) | 0.05 | 0.04 |
| Average Latency (ms) | 0.08 | 0.05 |
| Maximum Latency (ms) | 4.63 | 2 |
| 95th Percentile Latency (ms) | 0.1 | 0.07 |
MySQL SELECT (Random Points)
| Linode – (4 GB) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 8,212.00 | 6,349.00 |
| Queries per second | 82,120.00 | 63,490.00 |
| Minimum Latency (ms) | 0.33 | 0.37 |
| Average Latency (ms) | 1.22 | 1.57 |
| Maximum Latency (ms) | 11.27 | 3.86 |
| 95th Percentile Latency (ms) | 2.3 | 2.11 |
MySQL SELECT (Random Ranges)
| Linode – (4 GB) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 8,956.00 | 7,578.00 |
| Queries per second | 89,560.00 | 75,780.00 |
| Minimum Latency (ms) | 0.42 | 0.33 |
| Average Latency (ms) | 1.12 | 1.32 |
| Maximum Latency (ms) | 4.66 | 3.34 |
| 95th Percentile Latency (ms) | 1.44 | 1.79 |
MySQL UPDATE (Indexed)
| Linode – (4 GB) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 7,381.00 | 12,520.00 |
| Queries per second | 73,810.00 | 125,200.00 |
| Minimum Latency (ms) | 0.81 | 0.44 |
| Average Latency (ms) | 1.35 | 0.8 |
| Maximum Latency (ms) | 8.43 | 3.4 |
| 95th Percentile Latency (ms) | 1.76 | 1.06 |
MySQL UPDATE (Non-Indexed)
| Linode – (4 GB) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 7,379.00 | 13,084.00 |
| Queries per second | 73,790.00 | 130,840.00 |
| Minimum Latency (ms) | 0.82 | 0.45 |
| Average Latency (ms) | 1.35 | 0.76 |
| Maximum Latency (ms) | 7.2 | 4.55 |
| 95th Percentile Latency (ms) | 1.73 | 0.99 |
MySQL DELETE
| Linode – (4 GB) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 58,502.00 | 116,263.00 |
| Queries per second | 585,020.00 | 1,162,630.00 |
| Minimum Latency (ms) | 0.04 | 0.03 |
| Average Latency (ms) | 0.17 | 0.09 |
| Maximum Latency (ms) | 8.26 | 3.79 |
| 95th Percentile Latency (ms) | 1.14 | 0.12 |
Redis
| Linode – (4 GB) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| PING_INLINE per Second | 44,444.45 | 53,022.27 |
| PING_MBULK per Second | 42,158.52 | 58,139.54 |
| SET per Second | 43,725.41 | 58,309.04 |
| GET per Second | 43,084.88 | 59,453.03 |
| INCR per Second | 43,917.44 | 60,024.01 |
| LPUSH per Second | 44,169.61 | 58,997.05 |
| RPUSH per Second | 42,918.46 | 59,916.12 |
| LPOP per Second | 43,630.02 | 60,938.45 |
| RPOP per Second | 42,900.04 | 61,804.70 |
| SADD per Second | 43,066.32 | 62,189.05 |
| HSET per Second | 42,826.55 | 63,131.31 |
| SPOP per Second | 43,821.21 | 61,274.51 |
| ZADD per Second | 43,706.29 | 61,312.08 |
| ZPOPMIN per Second | 46,554.93 | 63,653.72 |
| LRANGE_100 (first 100 elements) per Second | 30,084.24 | 42,535.09 |
| LRANGE_300 (first 300 elements) per Second | 21,141.65 | 25,018.76 |
| LRANGE_500 (first 500 elements) per Second | 17,825.31 | 17,895.49 |
| LRANGE_600 (first 600 elements) per Second | 15,969.34 | 15,649.45 |
| MSET (10 keys) per Second | 45,578.85 | 61,199.51 |
Redis Average Latency (ms)
| Linode – (4 GB) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| PING_INLINE | 0.58 | 0.49 |
| PING_MBULK | 0.61 | 0.44 |
| SET | 0.59 | 0.44 |
| GET | 0.60 | 0.43 |
| INCR | 0.59 | 0.43 |
| LPUSH | 0.58 | 0.44 |
| RPUSH | 0.60 | 0.43 |
| LPOP | 0.59 | 0.43 |
| RPOP | 0.60 | 0.42 |
| SADD | 0.60 | 0.47 |
| HSET | 0.60 | 0.45 |
| SPOP | 0.59 | 0.42 |
| ZADD | 0.59 | 0.43 |
| ZPOPMIN | 0.55 | 0.45 |
| LRANGE_100 (first 100 elements) | 0.89 | 0.87 |
| LRANGE_300 (first 300 elements) | 1.25 | 1.46 |
| LRANGE_500 (first 500 elements) | 1.50 | 1.69 |
| LRANGE_600 (first 600 elements) | 1.59 | 1.77 |
| MSET (10 keys) | 0.57 | 0.45 |
Conclusion
From the friendly robots:
After analyzing both the Linode (4 GB) and Vultr High Performance Intel (8 GB, 4 Cores) instances, it's evident that the Vultr instance demonstrates higher performance across most benchmarks, particularly in Redis operations, CPU events, file I/O operations, and MySQL bulk inserts, reflecting its stronger CPU capabilities due to the Intel Xeon Processor. The Linode instance, though powerful with 2 cores of AMD EPYC 7642, lags behind in overall performance metrics, especially in memory operations and longer Redis list range operations. Therefore, the Vultr instance is better suited for CPU-intensive, I/O-heavy workloads, while the Linode instance might be more appropriate for scenarios where high memory throughput and lower latency in specific Redis operations are critical, given its more efficient memory handling and lower latency in Redis commands.
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.