Linode Linode (8 GB) vs. Vultr Cloud Compute (4 GB, 2 Cores)
Welcome to another round of the VPS Showdown. Today I've spun up some brand new instance from Linode and Vultr and ran some benchmarks. Each instance was running 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 – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Last Benchmarked | Wed, 10 Jun 2026 08:00:52 GMT | Thu, 11 Jun 2026 09: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-124-generic |
| MySQL Version | 8.0.46-0ubuntu0.24.04.2 | 8.0.46-0ubuntu0.24.04.2 |
| Redis Version | 7.0.15 | 7.0.15 |
| Location | Newark, NJ | Newark, NJ |
| Monthly Price | $48.00 | $20.00 |
| RAM (GB) | 8 | 4 |
| CPU Cores | 4 | 2 |
| Storage (TB) | 160 | 80 |
| Storage Type | SSD | SSD |
| Transfer (TB) | 5 | 3 |
CPU
| Linode – (8 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Vendor | AuthenticAMD | GenuineIntel |
| Model Name | AMD EPYC 7542 32-Core Processor | Intel Xeon Processor (Skylake, IBRS) |
| Clock Speed (MHz) | 2,900.00 | 2,593.91 |
| CPU Cache Size (KB) | 512.00 | 16,384.00 |
| BogoMips | 5,799.99 | 5,187.81 |
| Events per Second | 1,620.79 | 1,022.39 |
| Minimum Latency (ms) | 0.58 | 0.88 |
| Average Latency (ms) | 0.62 | 0.98 |
| Maximum Latency (ms) | 7.7 | 1.77 |
| 95th Percentile Latency (ms) | 0.65 | 1.21 |
Memory
Memory Read
| Linode – (8 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 5,340,659.88 | 3,523,809.57 |
| Mebibytes per second | 5,215.49 | 3,441.22 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 5.6 | 0.22 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Linode – (8 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 5,368,937.33 | 3,568,203.77 |
| Mebibytes per second | 5,243.10 | 3,484.57 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 3.07 | 1.02 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Linode – (8 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Reads per Second | 4,923.97 | 2,972.63 |
| Writes per Second | 3,282.71 | 1,981.75 |
| Fsyncs per Second | 10,512.35 | 6,347.81 |
| Read Mebibytes per Second | 76.94 | 46.45 |
| Written Mebibytes per Second | 51.29 | 30.96 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.05 | 0.09 |
| Maximum Latency (ms) | 20.27 | 17.12 |
| 95th Percentile Latency (ms) | 0.2 | 0.33 |
Mutex
| Linode – (8 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 343.38 | 899.28 |
| Average Latency (ms) | 401.69 | 935.93 |
| Maximum Latency (ms) | 439.54 | 969.92 |
| 95th Percentile Latency (ms) | 442.73 | 977.74 |
MySQL
MySQL Read-only
| Linode – (8 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 6,623.00 | 3,779.00 |
| Queries per second | 66,230.00 | 37,790.00 |
| Minimum Latency (ms) | 1.18 | 1.84 |
| Average Latency (ms) | 1.51 | 2.64 |
| Maximum Latency (ms) | 5.59 | 24.55 |
| 95th Percentile Latency (ms) | 1.89 | 3.82 |
MySQL Write-only
| Linode – (8 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 5,748.00 | 4,044.00 |
| Queries per second | 57,480.00 | 40,440.00 |
| Minimum Latency (ms) | 1.02 | 1.4 |
| Average Latency (ms) | 1.74 | 2.47 |
| Maximum Latency (ms) | 47.81 | 13.46 |
| 95th Percentile Latency (ms) | 2.14 | 3.3 |
MySQL Read/Write
| Linode – (8 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 2,937.00 | 1,798.00 |
| Queries per second | 29,370.00 | 17,980.00 |
| Minimum Latency (ms) | 2.35 | 3.86 |
| Average Latency (ms) | 3.4 | 5.56 |
| Maximum Latency (ms) | 16.51 | 27.33 |
| 95th Percentile Latency (ms) | 4.33 | 6.91 |
MySQL INSERT
| Linode – (8 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,224.00 | 6,405.00 |
| Queries per second | 82,240.00 | 64,050.00 |
| Minimum Latency (ms) | 0.68 | 0.99 |
| Average Latency (ms) | 1.21 | 1.56 |
| Maximum Latency (ms) | 12.51 | 15.15 |
| 95th Percentile Latency (ms) | 1.55 | 2.03 |
MySQL Bulk INSERT
| Linode – (8 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 1,667,092.00 | 865,805.00 |
| Queries per second | 16,670,920.00 | 8,658,050.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0.01 |
| Maximum Latency (ms) | 309.8 | 538.25 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Linode – (8 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 152,316.00 | 126,618.00 |
| Queries per second | 1,523,160.00 | 1,266,180.00 |
| Minimum Latency (ms) | 0.04 | 0.05 |
| Average Latency (ms) | 0.07 | 0.08 |
| Maximum Latency (ms) | 9.55 | 2.46 |
| 95th Percentile Latency (ms) | 0.09 | 0.11 |
MySQL SELECT (Random Points)
| Linode – (8 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,470.00 | 3,674.00 |
| Queries per second | 84,700.00 | 36,740.00 |
| Minimum Latency (ms) | 0.41 | 1.07 |
| Average Latency (ms) | 1.18 | 2.72 |
| Maximum Latency (ms) | 4.46 | 6.45 |
| 95th Percentile Latency (ms) | 1.55 | 3.55 |
MySQL SELECT (Random Ranges)
| Linode – (8 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 7,587.00 | 2,728.00 |
| Queries per second | 75,870.00 | 27,280.00 |
| Minimum Latency (ms) | 0.44 | 1.3 |
| Average Latency (ms) | 1.32 | 3.66 |
| Maximum Latency (ms) | 4.91 | 11.85 |
| 95th Percentile Latency (ms) | 1.7 | 5 |
MySQL UPDATE (Indexed)
| Linode – (8 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,440.00 | 5,438.00 |
| Queries per second | 84,400.00 | 54,380.00 |
| Minimum Latency (ms) | 0.72 | 0.99 |
| Average Latency (ms) | 1.18 | 1.84 |
| Maximum Latency (ms) | 5.37 | 13.86 |
| 95th Percentile Latency (ms) | 1.44 | 2.71 |
MySQL UPDATE (Non-Indexed)
| Linode – (8 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,392.00 | 6,370.00 |
| Queries per second | 83,920.00 | 63,700.00 |
| Minimum Latency (ms) | 0.79 | 1.01 |
| Average Latency (ms) | 1.19 | 1.57 |
| Maximum Latency (ms) | 11.27 | 8.99 |
| 95th Percentile Latency (ms) | 1.39 | 2.07 |
MySQL DELETE
| Linode – (8 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 89,474.00 | 51,180.00 |
| Queries per second | 894,740.00 | 511,800.00 |
| Minimum Latency (ms) | 0.04 | 0.05 |
| Average Latency (ms) | 0.11 | 0.19 |
| Maximum Latency (ms) | 6.69 | 6.11 |
| 95th Percentile Latency (ms) | 0.12 | 1.39 |
Redis
| Linode – (8 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE per Second | 61,804.70 | 49,677.10 |
| PING_MBULK per Second | 72,516.32 | 45,372.05 |
| SET per Second | 68,119.89 | 45,392.64 |
| GET per Second | 73,529.41 | 53,163.21 |
| INCR per Second | 73,964.50 | 48,732.94 |
| LPUSH per Second | 75,131.48 | 50,327.12 |
| RPUSH per Second | 74,349.44 | 48,285.85 |
| LPOP per Second | 72,411.30 | 48,355.90 |
| RPOP per Second | 65,573.77 | 51,413.88 |
| SADD per Second | 69,396.25 | 48,332.53 |
| HSET per Second | 71,479.62 | 49,285.36 |
| SPOP per Second | 69,979.01 | 48,332.53 |
| ZADD per Second | 73,583.52 | 51,229.51 |
| ZPOPMIN per Second | 65,019.51 | 45,085.66 |
| LRANGE_100 (first 100 elements) per Second | 47,938.64 | 27,122.32 |
| LRANGE_300 (first 300 elements) per Second | 29,612.08 | 12,442.45 |
| LRANGE_500 (first 500 elements) per Second | 20,395.68 | 7,930.21 |
| LRANGE_600 (first 600 elements) per Second | 17,608.73 | 6,902.74 |
| MSET (10 keys) per Second | 59,844.41 | 45,146.73 |
Redis Average Latency (ms)
| Linode – (8 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE | 0.42 | 0.53 |
| PING_MBULK | 0.35 | 0.57 |
| SET | 0.38 | 0.57 |
| GET | 0.35 | 0.49 |
| INCR | 0.35 | 0.53 |
| LPUSH | 0.34 | 0.51 |
| RPUSH | 0.35 | 0.54 |
| LPOP | 0.36 | 0.54 |
| RPOP | 0.40 | 0.52 |
| SADD | 0.37 | 0.55 |
| HSET | 0.36 | 0.54 |
| SPOP | 0.37 | 0.54 |
| ZADD | 0.35 | 0.52 |
| ZPOPMIN | 0.40 | 0.57 |
| LRANGE_100 (first 100 elements) | 0.54 | 1.02 |
| LRANGE_300 (first 300 elements) | 0.88 | 2.29 |
| LRANGE_500 (first 500 elements) | 1.28 | 3.27 |
| LRANGE_600 (first 600 elements) | 1.49 | 3.91 |
| MSET (10 keys) | 0.49 | 0.78 |
Conclusion
From the friendly robots:
When comparing the benchmark performance of the Linode (8 GB) and Vultr (4 GB, 2 Cores) instances, it's clear that the Linode offers superior performance across the board. The Linode, with its more powerful AMD EPYC 7542 processor, delivers significantly higher Redis request rates per second and lower latencies, indicating faster processing times and better overall throughput. This instance also excels in CPU, file I/O, and memory benchmarks, showcasing superior multitasking capabilities and efficiency. Conversely, the Vultr instance, powered by a less powerful Intel Xeon Processor, lags behind in most benchmarks, especially in the more demanding tasks like long Redis LRANGE operations and CPU-intensive tasks. Therefore, the Linode is ideal for CPU-intensive and memory-heavy workloads, whereas the Vultr instance would be better suited for lighter, less demanding applications due to its lower resource allocation.
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.