Linode Linode (2 GB) vs. Vultr Cloud Compute (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 were created in the New York area (or close to it). Let's get into the numbers.
Overview
| Linode – (2 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Last Benchmarked | Wed, 10 Jun 2026 22: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 | $12.00 | $20.00 |
| RAM (GB) | 2 | 4 |
| CPU Cores | 1 | 2 |
| Storage (TB) | 50 | 80 |
| Storage Type | SSD | SSD |
| Transfer (TB) | 2 | 3 |
CPU
| Linode – (2 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Vendor | AuthenticAMD | GenuineIntel |
| Model Name | AMD EPYC 7713 64-Core Processor | Intel Xeon Processor (Skylake, IBRS) |
| Clock Speed (MHz) | 2,000.00 | 2,593.91 |
| CPU Cache Size (KB) | 512.00 | 16,384.00 |
| BogoMips | 3,999.99 | 5,187.81 |
| Events per Second | 1,652.64 | 1,022.39 |
| Minimum Latency (ms) | 0.28 | 0.88 |
| Average Latency (ms) | 0.6 | 0.98 |
| Maximum Latency (ms) | 17.18 | 1.77 |
| 95th Percentile Latency (ms) | 2.81 | 1.21 |
Memory
Memory Read
| Linode – (2 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 2,514,244.82 | 3,523,809.57 |
| Mebibytes per second | 2,455.32 | 3,441.22 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 7.93 | 0.22 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Linode – (2 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 2,533,070.29 | 3,568,203.77 |
| Mebibytes per second | 2,473.70 | 3,484.57 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 7.74 | 1.02 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Linode – (2 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Reads per Second | 2,675.64 | 2,972.63 |
| Writes per Second | 1,783.73 | 1,981.75 |
| Fsyncs per Second | 5,714.01 | 6,347.81 |
| Read Mebibytes per Second | 41.81 | 46.45 |
| Written Mebibytes per Second | 27.87 | 30.96 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.1 | 0.09 |
| Maximum Latency (ms) | 13.04 | 17.12 |
| 95th Percentile Latency (ms) | 0.23 | 0.33 |
Mutex
| Linode – (2 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 1,762.36 | 899.28 |
| Average Latency (ms) | 1,768.99 | 935.93 |
| Maximum Latency (ms) | 1,778.05 | 969.92 |
| 95th Percentile Latency (ms) | 1,771.29 | 977.74 |
MySQL
MySQL Read-only
| Linode – (2 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 6,271.00 | 3,779.00 |
| Queries per second | 62,710.00 | 37,790.00 |
| Minimum Latency (ms) | 1.3 | 1.84 |
| Average Latency (ms) | 1.59 | 2.64 |
| Maximum Latency (ms) | 9.59 | 24.55 |
| 95th Percentile Latency (ms) | 1.96 | 3.82 |
MySQL Write-only
| Linode – (2 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 4,694.00 | 4,044.00 |
| Queries per second | 46,940.00 | 40,440.00 |
| Minimum Latency (ms) | 1.42 | 1.4 |
| Average Latency (ms) | 2.13 | 2.47 |
| Maximum Latency (ms) | 9.79 | 13.46 |
| 95th Percentile Latency (ms) | 2.91 | 3.3 |
MySQL Read/Write
| Linode – (2 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 1,846.00 | 1,798.00 |
| Queries per second | 18,460.00 | 17,980.00 |
| Minimum Latency (ms) | 3.25 | 3.86 |
| Average Latency (ms) | 5.41 | 5.56 |
| Maximum Latency (ms) | 175.66 | 27.33 |
| 95th Percentile Latency (ms) | 9.91 | 6.91 |
MySQL INSERT
| Linode – (2 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 7,307.00 | 6,405.00 |
| Queries per second | 73,070.00 | 64,050.00 |
| Minimum Latency (ms) | 0.85 | 0.99 |
| Average Latency (ms) | 1.36 | 1.56 |
| Maximum Latency (ms) | 8.73 | 15.15 |
| 95th Percentile Latency (ms) | 1.76 | 2.03 |
MySQL Bulk INSERT
| Linode – (2 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 1,084,592.00 | 865,805.00 |
| Queries per second | 10,845,920.00 | 8,658,050.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0.01 |
| Maximum Latency (ms) | 550.13 | 538.25 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Linode – (2 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 127,669.00 | 126,618.00 |
| Queries per second | 1,276,690.00 | 1,266,180.00 |
| Minimum Latency (ms) | 0.06 | 0.05 |
| Average Latency (ms) | 0.08 | 0.08 |
| Maximum Latency (ms) | 8.36 | 2.46 |
| 95th Percentile Latency (ms) | 0.11 | 0.11 |
MySQL SELECT (Random Points)
| Linode – (2 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 7,743.00 | 3,674.00 |
| Queries per second | 77,430.00 | 36,740.00 |
| Minimum Latency (ms) | 0.35 | 1.07 |
| Average Latency (ms) | 1.29 | 2.72 |
| Maximum Latency (ms) | 12.54 | 6.45 |
| 95th Percentile Latency (ms) | 2.52 | 3.55 |
MySQL SELECT (Random Ranges)
| Linode – (2 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,936.00 | 2,728.00 |
| Queries per second | 89,360.00 | 27,280.00 |
| Minimum Latency (ms) | 0.35 | 1.3 |
| Average Latency (ms) | 1.12 | 3.66 |
| Maximum Latency (ms) | 6.99 | 11.85 |
| 95th Percentile Latency (ms) | 1.5 | 5 |
MySQL UPDATE (Indexed)
| Linode – (2 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 6,853.00 | 5,438.00 |
| Queries per second | 68,530.00 | 54,380.00 |
| Minimum Latency (ms) | 0.79 | 0.99 |
| Average Latency (ms) | 1.46 | 1.84 |
| Maximum Latency (ms) | 23.71 | 13.86 |
| 95th Percentile Latency (ms) | 2.07 | 2.71 |
MySQL UPDATE (Non-Indexed)
| Linode – (2 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 7,367.00 | 6,370.00 |
| Queries per second | 73,670.00 | 63,700.00 |
| Minimum Latency (ms) | 0.77 | 1.01 |
| Average Latency (ms) | 1.36 | 1.57 |
| Maximum Latency (ms) | 9.42 | 8.99 |
| 95th Percentile Latency (ms) | 1.79 | 2.07 |
MySQL DELETE
| Linode – (2 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 61,270.00 | 51,180.00 |
| Queries per second | 612,700.00 | 511,800.00 |
| Minimum Latency (ms) | 0.05 | 0.05 |
| Average Latency (ms) | 0.16 | 0.19 |
| Maximum Latency (ms) | 8.2 | 6.11 |
| 95th Percentile Latency (ms) | 1.06 | 1.39 |
Redis
| Linode – (2 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE per Second | 29,342.72 | 49,677.10 |
| PING_MBULK per Second | 30,138.64 | 45,372.05 |
| SET per Second | 29,976.02 | 45,392.64 |
| GET per Second | 30,193.24 | 53,163.21 |
| INCR per Second | 29,664.79 | 48,732.94 |
| LPUSH per Second | 29,377.20 | 50,327.12 |
| RPUSH per Second | 29,717.68 | 48,285.85 |
| LPOP per Second | 29,334.12 | 48,355.90 |
| RPOP per Second | 29,559.56 | 51,413.88 |
| SADD per Second | 29,542.10 | 48,332.53 |
| HSET per Second | 29,824.04 | 49,285.36 |
| SPOP per Second | 30,111.41 | 48,332.53 |
| ZADD per Second | 29,655.99 | 51,229.51 |
| ZPOPMIN per Second | 29,368.58 | 45,085.66 |
| LRANGE_100 (first 100 elements) per Second | 21,445.42 | 27,122.32 |
| LRANGE_300 (first 300 elements) per Second | 13,147.52 | 12,442.45 |
| LRANGE_500 (first 500 elements) per Second | 9,106.64 | 7,930.21 |
| LRANGE_600 (first 600 elements) per Second | 9,053.87 | 6,902.74 |
| MSET (10 keys) per Second | 27,247.96 | 45,146.73 |
Redis Average Latency (ms)
| Linode – (2 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE | 1.07 | 0.53 |
| PING_MBULK | 1.04 | 0.57 |
| SET | 1.06 | 0.57 |
| GET | 1.04 | 0.49 |
| INCR | 1.06 | 0.53 |
| LPUSH | 1.08 | 0.51 |
| RPUSH | 1.07 | 0.54 |
| LPOP | 1.09 | 0.54 |
| RPOP | 1.07 | 0.52 |
| SADD | 1.07 | 0.55 |
| HSET | 1.06 | 0.54 |
| SPOP | 1.04 | 0.54 |
| ZADD | 1.07 | 0.52 |
| ZPOPMIN | 1.07 | 0.57 |
| LRANGE_100 (first 100 elements) | 1.51 | 1.02 |
| LRANGE_300 (first 300 elements) | 2.48 | 2.29 |
| LRANGE_500 (first 500 elements) | 3.59 | 3.27 |
| LRANGE_600 (first 600 elements) | 3.70 | 3.91 |
| MSET (10 keys) | 1.19 | 0.78 |
Conclusion
From the friendly robots:
In comparing the two VPS instances, the Linode (2 GB) shows strong performance with high Redis request rates per second (rps) and relatively low latencies, making it a good choice for CPU-intensive workloads or applications that benefit from low latency and high throughput. On the other hand, the Vultr Cloud Compute (4 GB, 2 Cores) instance offers even higher Redis rps with lower average latencies across a wider range of operations, indicating superior overall performance. While it has slightly higher maximum latencies, its double CPU cores and more RAM provide a significant advantage for multi-threaded tasks, making it ideal for I/O-heavy workloads or larger applications requiring more resources. Cost-wise, Vultr is also more economical, though this factor may vary based on specific use case and 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.