Linode Linode (2 GB) vs. Vultr High Performance AMD (2 GB, 2 Cores)
Welcome to another round of the VPS Showdown. Today I've spun up brand new instance from Linode and Vultr and ran some benchmarks. All instances were spun up with Ubuntu 24.04 LTS x64 and were created in the New York area (or close to it). Time to see who showed up today.
Overview
| Linode – (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Last Benchmarked | Fri, 29 May 2026 14:00:53 GMT | Sun, 31 May 2026 07: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 | $12.00 | $18.00 |
| RAM (GB) | 2 | 2 |
| CPU Cores | 1 | 2 |
| Storage (TB) | 50 | 60 |
| Storage Type | SSD | NVMe |
| Transfer (TB) | 2 | 4 |
CPU
| Linode – (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Vendor | AuthenticAMD | AuthenticAMD |
| Model Name | AMD EPYC 7713 64-Core Processor | AMD EPYC-Genoa Processor |
| Clock Speed (MHz) | 2,000.00 | 2,899.99 |
| CPU Cache Size (KB) | 512.00 | 1,024.00 |
| BogoMips | 4,000.00 | 5,799.98 |
| Events per Second | 1,650.27 | 4,648.14 |
| Minimum Latency (ms) | 0.28 | 0.2 |
| Average Latency (ms) | 0.59 | 0.21 |
| Maximum Latency (ms) | 7.39 | 1.26 |
| 95th Percentile Latency (ms) | 2.91 | 0.23 |
Memory
Memory Read
| Linode – (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 2,585,804.56 | 7,548,502.85 |
| Mebibytes per second | 2,525.20 | 7,371.58 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 10.45 | 0.08 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Linode – (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 2,653,044.04 | 7,544,807.09 |
| Mebibytes per second | 2,590.86 | 7,367.98 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 3.55 | 0.12 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Linode – (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Reads per Second | 2,276.83 | 5,114.79 |
| Writes per Second | 1,517.85 | 3,409.86 |
| Fsyncs per Second | 4,857.45 | 10,914.44 |
| Read Mebibytes per Second | 35.58 | 79.92 |
| Written Mebibytes per Second | 23.72 | 53.28 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.12 | 0.05 |
| Maximum Latency (ms) | 6.09 | 3.7 |
| 95th Percentile Latency (ms) | 0.33 | 0.12 |
Mutex
| Linode – (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 1,670.96 | 574.03 |
| Average Latency (ms) | 1,684.24 | 637.47 |
| Maximum Latency (ms) | 1,690.89 | 663.74 |
| 95th Percentile Latency (ms) | 1,678.14 | 657.93 |
MySQL
MySQL Read-only
| Linode – (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 7,383.00 | 9,622.00 |
| Queries per second | 73,830.00 | 96,220.00 |
| Minimum Latency (ms) | 1.22 | 0.73 |
| Average Latency (ms) | 1.35 | 1.04 |
| Maximum Latency (ms) | 10.4 | 2.22 |
| 95th Percentile Latency (ms) | 1.55 | 1.12 |
MySQL Write-only
| Linode – (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 5,152.00 | 9,585.00 |
| Queries per second | 51,520.00 | 95,850.00 |
| Minimum Latency (ms) | 1.13 | 0.8 |
| Average Latency (ms) | 1.94 | 1.04 |
| Maximum Latency (ms) | 9.03 | 2.18 |
| 95th Percentile Latency (ms) | 2.66 | 1.32 |
MySQL Read/Write
| Linode – (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 2,524.00 | 4,686.00 |
| Queries per second | 25,240.00 | 46,860.00 |
| Minimum Latency (ms) | 2.7 | 1.57 |
| Average Latency (ms) | 3.96 | 2.13 |
| Maximum Latency (ms) | 45.47 | 4.26 |
| 95th Percentile Latency (ms) | 4.91 | 2.52 |
MySQL INSERT
| Linode – (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,292.00 | 15,965.00 |
| Queries per second | 82,920.00 | 159,650.00 |
| Minimum Latency (ms) | 0.69 | 0.45 |
| Average Latency (ms) | 1.2 | 0.62 |
| Maximum Latency (ms) | 6.2 | 2.23 |
| 95th Percentile Latency (ms) | 1.55 | 0.74 |
MySQL Bulk INSERT
| Linode – (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 1,392,639.00 | 3,065,092.00 |
| Queries per second | 13,926,390.00 | 30,650,920.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0 |
| Maximum Latency (ms) | 382.7 | 208.51 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Linode – (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 150,326.00 | 217,035.00 |
| Queries per second | 1,503,260.00 | 2,170,350.00 |
| Minimum Latency (ms) | 0.05 | 0.02 |
| Average Latency (ms) | 0.07 | 0.05 |
| Maximum Latency (ms) | 3.4 | 0.61 |
| 95th Percentile Latency (ms) | 0.09 | 0.06 |
MySQL SELECT (Random Points)
| Linode – (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 9,042.00 | 14,818.00 |
| Queries per second | 90,420.00 | 148,180.00 |
| Minimum Latency (ms) | 0.25 | 0.24 |
| Average Latency (ms) | 1.1 | 0.67 |
| Maximum Latency (ms) | 7.95 | 1.94 |
| 95th Percentile Latency (ms) | 1.5 | 0.86 |
MySQL SELECT (Random Ranges)
| Linode – (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 9,605.00 | 14,341.00 |
| Queries per second | 96,050.00 | 143,410.00 |
| Minimum Latency (ms) | 0.34 | 0.27 |
| Average Latency (ms) | 1.04 | 0.7 |
| Maximum Latency (ms) | 5.88 | 1.67 |
| 95th Percentile Latency (ms) | 1.34 | 0.89 |
MySQL UPDATE (Indexed)
| Linode – (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 4,886.00 | 14,864.00 |
| Queries per second | 48,860.00 | 148,640.00 |
| Minimum Latency (ms) | 0.73 | 0.47 |
| Average Latency (ms) | 2.04 | 0.67 |
| Maximum Latency (ms) | 42.05 | 2.36 |
| 95th Percentile Latency (ms) | 4.49 | 0.87 |
MySQL UPDATE (Non-Indexed)
| Linode – (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 6,557.00 | 15,284.00 |
| Queries per second | 65,570.00 | 152,840.00 |
| Minimum Latency (ms) | 0.74 | 0.46 |
| Average Latency (ms) | 1.52 | 0.65 |
| Maximum Latency (ms) | 26.53 | 1.65 |
| 95th Percentile Latency (ms) | 3.43 | 0.83 |
MySQL DELETE
| Linode – (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 71,618.00 | 151,536.00 |
| Queries per second | 716,180.00 | 1,515,360.00 |
| Minimum Latency (ms) | 0.05 | 0.02 |
| Average Latency (ms) | 0.14 | 0.07 |
| Maximum Latency (ms) | 6.07 | 4.83 |
| 95th Percentile Latency (ms) | 0.9 | 0.08 |
Redis
| Linode – (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE per Second | 39,840.64 | 55,991.04 |
| PING_MBULK per Second | 39,968.02 | 57,903.88 |
| SET per Second | 39,308.18 | 57,703.40 |
| GET per Second | 38,580.25 | 57,703.40 |
| INCR per Second | 38,789.76 | 57,372.34 |
| LPUSH per Second | 37,565.74 | 57,836.90 |
| RPUSH per Second | 38,211.69 | 58,173.36 |
| LPOP per Second | 37,664.79 | 58,343.06 |
| RPOP per Second | 38,314.18 | 58,343.06 |
| SADD per Second | 39,292.73 | 58,241.12 |
| HSET per Second | 38,684.72 | 58,858.15 |
| SPOP per Second | 39,001.56 | 58,892.82 |
| ZADD per Second | 38,255.55 | 57,504.31 |
| ZPOPMIN per Second | 39,215.69 | 57,870.37 |
| LRANGE_100 (first 100 elements) per Second | 27,107.62 | 49,236.83 |
| LRANGE_300 (first 300 elements) per Second | 14,956.63 | 34,818.94 |
| LRANGE_500 (first 500 elements) per Second | 11,341.73 | 26,766.60 |
| LRANGE_600 (first 600 elements) per Second | 9,931.47 | 24,207.21 |
| MSET (10 keys) per Second | 35,829.45 | 58,548.01 |
Redis Average Latency (ms)
| Linode – (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE | 0.83 | 0.48 |
| PING_MBULK | 0.83 | 0.44 |
| SET | 0.85 | 0.45 |
| GET | 0.85 | 0.45 |
| INCR | 0.85 | 0.45 |
| LPUSH | 0.88 | 0.44 |
| RPUSH | 0.86 | 0.44 |
| LPOP | 0.89 | 0.44 |
| RPOP | 0.87 | 0.44 |
| SADD | 0.84 | 0.44 |
| HSET | 0.85 | 0.44 |
| SPOP | 0.85 | 0.44 |
| ZADD | 0.87 | 0.45 |
| ZPOPMIN | 0.84 | 0.44 |
| LRANGE_100 (first 100 elements) | 1.25 | 0.53 |
| LRANGE_300 (first 300 elements) | 2.24 | 0.74 |
| LRANGE_500 (first 500 elements) | 2.96 | 0.95 |
| LRANGE_600 (first 600 elements) | 3.42 | 1.05 |
| MSET (10 keys) | 0.94 | 0.44 |
Conclusion
From the friendly robots:
In summary, the Vultr High Performance AMD (2 GB, 2 Cores) instance outperformed the Linode (2 GB) in most benchmarks, especially in Redis operations, CPU throughput, and MySQL bulk insert operations. The Vultr instance achieved significantly higher requests per second and lower latency across most Redis commands, with a more pronounced improvement in CPU performance, boasting higher events per second and lower average latency. File I/O operations also saw better throughput and lower latency on the Vultr instance. The Linode instance, while providing competitive performance, especially in memory operations, lags behind in CPU-intensive tasks and bulk insert operations in MySQL. For users prioritizing higher throughput and lower latency in CPU-intensive, memory-bound, and database operations, the Vultr instance is the better choice. Conversely, for those where memory operations and more balanced performance across different tasks are key, the Linode instance might be more suitable.
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.