Linode Linode (2 GB) vs. Vultr High Performance AMD (4 GB, 2 Cores)
Same showdown, different day. Today I've spun up brand new instance from Linode and Vultr to run some benchmarks on. All instances were running 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 – Linode (2 GB) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Last Benchmarked | Thu, 02 Apr 2026 22:00:52 GMT | Fri, 03 Apr 2026 10:00:52 GMT |
| Linux Distro | Ubuntu 24.04 LTS x64 | Ubuntu 24.04 LTS x64 |
| Kernel Version | 6.8.0-71-generic | 6.8.0-107-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 | $24.00 |
| RAM (GB) | 2 | 4 |
| CPU Cores | 1 | 2 |
| Storage (TB) | 50 | 100 |
| Storage Type | SSD | NVMe |
| Transfer (TB) | 2 | 5 |
CPU
| Linode – Linode (2 GB) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Vendor | AuthenticAMD | AuthenticAMD |
| Model Name | AMD EPYC 7642 48-Core Processor | AMD EPYC-Genoa Processor |
| Clock Speed (MHz) | 2,300.00 | 3,250.02 |
| CPU Cache Size (KB) | 512.00 | 1,024.00 |
| BogoMips | 4,600.00 | 6,500.03 |
| Events per Second | 773.73 | 4,139.70 |
| Minimum Latency (ms) | 0.6 | 0.22 |
| Average Latency (ms) | 1.28 | 0.24 |
| Maximum Latency (ms) | 10.26 | 2.3 |
| 95th Percentile Latency (ms) | 2.57 | 0.27 |
Memory
Memory Read
| Linode – Linode (2 GB) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 2,511,043.99 | 6,384,949.59 |
| Mebibytes per second | 2,452.19 | 6,235.30 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 4.56 | 1.06 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Linode – Linode (2 GB) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 4,661,769.10 | 6,463,195.23 |
| Mebibytes per second | 4,552.51 | 6,311.71 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 10.2 | 0.65 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Linode – Linode (2 GB) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Reads per Second | 2,056.55 | 6,410.78 |
| Writes per Second | 1,371.04 | 4,273.85 |
| Fsyncs per Second | 4,399.41 | 13,688.92 |
| Read Mebibytes per Second | 32.13 | 100.17 |
| Written Mebibytes per Second | 21.42 | 66.78 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.13 | 0.04 |
| Maximum Latency (ms) | 40.3 | 12.76 |
| 95th Percentile Latency (ms) | 0.41 | 0.14 |
Mutex
| Linode – Linode (2 GB) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 1,855.73 | 829.08 |
| Average Latency (ms) | 1,880.80 | 880.59 |
| Maximum Latency (ms) | 1,894.74 | 921.34 |
| 95th Percentile Latency (ms) | 1,903.57 | 926.33 |
MySQL
MySQL Read-only
| Linode – Linode (2 GB) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 6,757.00 | 8,493.00 |
| Queries per second | 67,570.00 | 84,930.00 |
| Minimum Latency (ms) | 1.27 | 0.86 |
| Average Latency (ms) | 1.48 | 1.18 |
| Maximum Latency (ms) | 7.2 | 3.6 |
| 95th Percentile Latency (ms) | 1.82 | 1.47 |
MySQL Write-only
| Linode – Linode (2 GB) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 5,276.00 | 7,390.00 |
| Queries per second | 52,760.00 | 73,900.00 |
| Minimum Latency (ms) | 1.17 | 0.85 |
| Average Latency (ms) | 1.89 | 1.35 |
| Maximum Latency (ms) | 9.33 | 7.03 |
| 95th Percentile Latency (ms) | 2.76 | 1.86 |
MySQL Read/Write
| Linode – Linode (2 GB) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 2,398.00 | 3,730.00 |
| Queries per second | 23,980.00 | 37,300.00 |
| Minimum Latency (ms) | 2.71 | 1.79 |
| Average Latency (ms) | 4.17 | 2.68 |
| Maximum Latency (ms) | 14.15 | 19.46 |
| 95th Percentile Latency (ms) | 5.67 | 3.43 |
MySQL INSERT
| Linode – Linode (2 GB) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,369.00 | 11,228.00 |
| Queries per second | 83,690.00 | 112,280.00 |
| Minimum Latency (ms) | 0.64 | 0.46 |
| Average Latency (ms) | 1.19 | 0.89 |
| Maximum Latency (ms) | 9.25 | 10.08 |
| 95th Percentile Latency (ms) | 1.64 | 1.23 |
MySQL Bulk INSERT
| Linode – Linode (2 GB) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 1,113,717.00 | 2,133,092.00 |
| Queries per second | 11,137,170.00 | 21,330,920.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0 |
| Maximum Latency (ms) | 420.11 | 269.3 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Linode – Linode (2 GB) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 144,243.00 | 175,252.00 |
| Queries per second | 1,442,430.00 | 1,752,520.00 |
| Minimum Latency (ms) | 0.05 | 0.02 |
| Average Latency (ms) | 0.07 | 0.06 |
| Maximum Latency (ms) | 1.46 | 1.58 |
| 95th Percentile Latency (ms) | 0.09 | 0.09 |
MySQL SELECT (Random Points)
| Linode – Linode (2 GB) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 6,834.00 | 11,692.00 |
| Queries per second | 68,340.00 | 116,920.00 |
| Minimum Latency (ms) | 0.47 | 0.26 |
| Average Latency (ms) | 1.46 | 0.85 |
| Maximum Latency (ms) | 6.91 | 4.23 |
| 95th Percentile Latency (ms) | 2.07 | 1.27 |
MySQL SELECT (Random Ranges)
| Linode – Linode (2 GB) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 6,913.00 | 10,810.00 |
| Queries per second | 69,130.00 | 108,100.00 |
| Minimum Latency (ms) | 0.47 | 0.19 |
| Average Latency (ms) | 1.44 | 0.92 |
| Maximum Latency (ms) | 5.96 | 5.82 |
| 95th Percentile Latency (ms) | 2.03 | 1.37 |
MySQL UPDATE (Indexed)
| Linode – Linode (2 GB) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 7,858.00 | 10,619.00 |
| Queries per second | 78,580.00 | 106,190.00 |
| Minimum Latency (ms) | 0.65 | 0.5 |
| Average Latency (ms) | 1.27 | 0.94 |
| Maximum Latency (ms) | 22.39 | 6.61 |
| 95th Percentile Latency (ms) | 1.89 | 1.32 |
MySQL UPDATE (Non-Indexed)
| Linode – Linode (2 GB) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,144.00 | 9,811.00 |
| Queries per second | 81,440.00 | 98,110.00 |
| Minimum Latency (ms) | 0.72 | 0.5 |
| Average Latency (ms) | 1.23 | 1.02 |
| Maximum Latency (ms) | 25.8 | 14.97 |
| 95th Percentile Latency (ms) | 1.67 | 1.52 |
MySQL DELETE
| Linode – Linode (2 GB) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 42,483.00 | 103,619.00 |
| Queries per second | 424,830.00 | 1,036,190.00 |
| Minimum Latency (ms) | 0.05 | 0.02 |
| Average Latency (ms) | 0.23 | 0.1 |
| Maximum Latency (ms) | 139.44 | 12.74 |
| 95th Percentile Latency (ms) | 1.12 | 0.17 |
Redis
| Linode – Linode (2 GB) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE per Second | 42,229.73 | 56,401.58 |
| PING_MBULK per Second | 44,014.08 | 66,006.60 |
| SET per Second | 42,955.32 | 67,980.97 |
| GET per Second | 41,407.87 | 67,934.78 |
| INCR per Second | 36,737.70 | 65,061.81 |
| LPUSH per Second | 42,087.54 | 65,919.58 |
| RPUSH per Second | 43,029.26 | 64,432.99 |
| LPOP per Second | 39,904.23 | 58,139.54 |
| RPOP per Second | 42,735.04 | 67,613.25 |
| SADD per Second | 41,050.90 | 55,617.35 |
| HSET per Second | 42,354.93 | 56,753.69 |
| SPOP per Second | 43,535.05 | 55,096.42 |
| ZADD per Second | 41,946.31 | 54,824.56 |
| ZPOPMIN per Second | 43,066.32 | 55,834.73 |
| LRANGE_100 (first 100 elements) per Second | 28,232.64 | 48,285.85 |
| LRANGE_300 (first 300 elements) per Second | 16,023.07 | 28,034.76 |
| LRANGE_500 (first 500 elements) per Second | 10,780.51 | 21,968.37 |
| LRANGE_600 (first 600 elements) per Second | 7,896.40 | 19,538.88 |
| MSET (10 keys) per Second | 36,859.56 | 56,497.18 |
Redis Average Latency (ms)
| Linode – Linode (2 GB) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE | 0.80 | 0.48 |
| PING_MBULK | 0.77 | 0.39 |
| SET | 0.79 | 0.39 |
| GET | 0.82 | 0.39 |
| INCR | 0.91 | 0.40 |
| LPUSH | 0.81 | 0.39 |
| RPUSH | 0.80 | 0.40 |
| LPOP | 0.86 | 0.46 |
| RPOP | 0.81 | 0.39 |
| SADD | 0.83 | 0.47 |
| HSET | 0.81 | 0.47 |
| SPOP | 0.79 | 0.48 |
| ZADD | 0.82 | 0.48 |
| ZPOPMIN | 0.79 | 0.47 |
| LRANGE_100 (first 100 elements) | 1.24 | 0.61 |
| LRANGE_300 (first 300 elements) | 2.29 | 1.01 |
| LRANGE_500 (first 500 elements) | 3.38 | 1.27 |
| LRANGE_600 (first 600 elements) | 4.47 | 1.41 |
| MSET (10 keys) | 0.96 | 0.48 |
Conclusion
From the friendly robots:
After analyzing the benchmarks for both the Linode (2 GB) and Vultr High Performance AMD (4 GB, 2 Cores) instances, it is evident that Vultr offers superior raw performance, especially in CPU-intensive tasks and Redis operations. Vultr's benchmarks show significantly higher requests per second for Redis commands, greater throughput for file I/O operations, and faster overall CPU performance metrics. However, Linode's configuration is slightly better in handling memory operations and has more competitive latency results for specific Redis commands like LRANGE, suggesting that Linode might be preferable for workloads that are memory-intensive or require more precise latency control. Both instances are solid for general use, but if maximum throughput and CPU performance are priorities, the Vultr instance is the better choice, while Linode may edge out in scenarios demanding fine-tuned memory operations and lower latency.
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.