Vultr High Performance AMD (2 GB, 2 Cores) vs. Vultr High Performance AMD (8 GB, 4 Cores)
New day, new benchmarks. Today I've spun up some brand new instance from Vultr and did some benchmarking. 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
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance AMD (8 GB, 4 Cores) | |
|---|---|---|
| Last Benchmarked | Sun, 31 May 2026 07:00:52 GMT | Sat, 30 May 2026 23:00:52 GMT |
| Linux Distro | Ubuntu 24.04 LTS x64 | Ubuntu 24.04 LTS x64 |
| Kernel Version | 6.8.0-117-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 | $18.00 | $48.00 |
| RAM (GB) | 2 | 8 |
| CPU Cores | 2 | 4 |
| Storage (TB) | 60 | 180 |
| Storage Type | NVMe | NVMe |
| Transfer (TB) | 4 | 6 |
CPU
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance AMD (8 GB, 4 Cores) | |
|---|---|---|
| Vendor | AuthenticAMD | AuthenticAMD |
| Model Name | AMD EPYC-Genoa Processor | AMD EPYC-Genoa Processor |
| Clock Speed (MHz) | 2,899.99 | 2,900.00 |
| CPU Cache Size (KB) | 1,024.00 | 1,024.00 |
| BogoMips | 5,799.98 | 5,799.99 |
| Events per Second | 4,648.14 | 4,651.31 |
| Minimum Latency (ms) | 0.2 | 0.2 |
| Average Latency (ms) | 0.21 | 0.21 |
| Maximum Latency (ms) | 1.26 | 0.87 |
| 95th Percentile Latency (ms) | 0.23 | 0.22 |
Memory
Memory Read
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance AMD (8 GB, 4 Cores) | |
|---|---|---|
| Operations per second | 7,548,502.85 | 7,539,967.02 |
| Mebibytes per second | 7,371.58 | 7,363.25 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.08 | 0.06 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance AMD (8 GB, 4 Cores) | |
|---|---|---|
| Operations per second | 7,544,807.09 | 7,548,797.16 |
| Mebibytes per second | 7,367.98 | 7,371.87 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.12 | 0.08 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance AMD (8 GB, 4 Cores) | |
|---|---|---|
| Reads per Second | 5,114.79 | 7,813.30 |
| Writes per Second | 3,409.86 | 5,208.87 |
| Fsyncs per Second | 10,914.44 | 16,674.38 |
| Read Mebibytes per Second | 79.92 | 122.08 |
| Written Mebibytes per Second | 53.28 | 81.39 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.05 | 0.03 |
| Maximum Latency (ms) | 3.7 | 0.89 |
| 95th Percentile Latency (ms) | 0.12 | 0.11 |
Mutex
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance AMD (8 GB, 4 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 574.03 | 163.69 |
| Average Latency (ms) | 637.47 | 303.04 |
| Maximum Latency (ms) | 663.74 | 365.09 |
| 95th Percentile Latency (ms) | 657.93 | 363.18 |
MySQL
MySQL Read-only
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance AMD (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 9,622.00 | 9,620.00 |
| Queries per second | 96,220.00 | 96,200.00 |
| Minimum Latency (ms) | 0.73 | 0.79 |
| Average Latency (ms) | 1.04 | 1.04 |
| Maximum Latency (ms) | 2.22 | 1.94 |
| 95th Percentile Latency (ms) | 1.12 | 1.16 |
MySQL Write-only
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance AMD (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 9,585.00 | 8,700.00 |
| Queries per second | 95,850.00 | 87,000.00 |
| Minimum Latency (ms) | 0.8 | 0.84 |
| Average Latency (ms) | 1.04 | 1.15 |
| Maximum Latency (ms) | 2.18 | 7.82 |
| 95th Percentile Latency (ms) | 1.32 | 1.34 |
MySQL Read/Write
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance AMD (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 4,686.00 | 4,664.00 |
| Queries per second | 46,860.00 | 46,640.00 |
| Minimum Latency (ms) | 1.57 | 1.63 |
| Average Latency (ms) | 2.13 | 2.14 |
| Maximum Latency (ms) | 4.26 | 4.23 |
| 95th Percentile Latency (ms) | 2.52 | 2.57 |
MySQL INSERT
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance AMD (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 15,965.00 | 13,911.00 |
| Queries per second | 159,650.00 | 139,110.00 |
| Minimum Latency (ms) | 0.45 | 0.45 |
| Average Latency (ms) | 0.62 | 0.72 |
| Maximum Latency (ms) | 2.23 | 2.28 |
| 95th Percentile Latency (ms) | 0.74 | 0.89 |
MySQL Bulk INSERT
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance AMD (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 3,065,092.00 | 2,715,592.00 |
| Queries per second | 30,650,920.00 | 27,155,920.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 208.51 | 213.69 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance AMD (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 217,035.00 | 219,615.00 |
| Queries per second | 2,170,350.00 | 2,196,150.00 |
| Minimum Latency (ms) | 0.02 | 0.02 |
| Average Latency (ms) | 0.05 | 0.05 |
| Maximum Latency (ms) | 0.61 | 0.86 |
| 95th Percentile Latency (ms) | 0.06 | 0.06 |
MySQL SELECT (Random Points)
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance AMD (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 14,818.00 | 14,319.00 |
| Queries per second | 148,180.00 | 143,190.00 |
| Minimum Latency (ms) | 0.24 | 0.23 |
| Average Latency (ms) | 0.67 | 0.7 |
| Maximum Latency (ms) | 1.94 | 3.5 |
| 95th Percentile Latency (ms) | 0.86 | 0.9 |
MySQL SELECT (Random Ranges)
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance AMD (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 14,341.00 | 13,994.00 |
| Queries per second | 143,410.00 | 139,940.00 |
| Minimum Latency (ms) | 0.27 | 0.23 |
| Average Latency (ms) | 0.7 | 0.71 |
| Maximum Latency (ms) | 1.67 | 1.63 |
| 95th Percentile Latency (ms) | 0.89 | 0.94 |
MySQL UPDATE (Indexed)
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance AMD (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 14,864.00 | 13,411.00 |
| Queries per second | 148,640.00 | 134,110.00 |
| Minimum Latency (ms) | 0.47 | 0.48 |
| Average Latency (ms) | 0.67 | 0.75 |
| Maximum Latency (ms) | 2.36 | 13.33 |
| 95th Percentile Latency (ms) | 0.87 | 0.94 |
MySQL UPDATE (Non-Indexed)
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance AMD (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 15,284.00 | 13,309.00 |
| Queries per second | 152,840.00 | 133,090.00 |
| Minimum Latency (ms) | 0.46 | 0.49 |
| Average Latency (ms) | 0.65 | 0.75 |
| Maximum Latency (ms) | 1.65 | 3.45 |
| 95th Percentile Latency (ms) | 0.83 | 0.94 |
MySQL DELETE
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance AMD (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 151,536.00 | 144,026.00 |
| Queries per second | 1,515,360.00 | 1,440,260.00 |
| Minimum Latency (ms) | 0.02 | 0.02 |
| Average Latency (ms) | 0.07 | 0.07 |
| Maximum Latency (ms) | 4.83 | 2.07 |
| 95th Percentile Latency (ms) | 0.08 | 0.08 |
Redis
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance AMD (8 GB, 4 Cores) | |
|---|---|---|
| PING_INLINE per Second | 55,991.04 | 68,119.89 |
| PING_MBULK per Second | 57,903.88 | 64,184.86 |
| SET per Second | 57,703.40 | 63,371.36 |
| GET per Second | 57,703.40 | 66,401.06 |
| INCR per Second | 57,372.34 | 62,305.30 |
| LPUSH per Second | 57,836.90 | 60,827.25 |
| RPUSH per Second | 58,173.36 | 67,114.09 |
| LPOP per Second | 58,343.06 | 63,613.23 |
| RPOP per Second | 58,343.06 | 67,340.07 |
| SADD per Second | 58,241.12 | 70,521.86 |
| HSET per Second | 58,858.15 | 66,401.06 |
| SPOP per Second | 58,892.82 | 62,695.92 |
| ZADD per Second | 57,504.31 | 58,685.45 |
| ZPOPMIN per Second | 57,870.37 | 57,971.02 |
| LRANGE_100 (first 100 elements) per Second | 49,236.83 | 55,586.44 |
| LRANGE_300 (first 300 elements) per Second | 34,818.94 | 35,026.27 |
| LRANGE_500 (first 500 elements) per Second | 26,766.60 | 26,357.41 |
| LRANGE_600 (first 600 elements) per Second | 24,207.21 | 23,906.29 |
| MSET (10 keys) per Second | 58,548.01 | 66,577.90 |
Redis Average Latency (ms)
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance AMD (8 GB, 4 Cores) | |
|---|---|---|
| PING_INLINE | 0.48 | 0.38 |
| PING_MBULK | 0.44 | 0.40 |
| SET | 0.45 | 0.41 |
| GET | 0.45 | 0.39 |
| INCR | 0.45 | 0.41 |
| LPUSH | 0.44 | 0.42 |
| RPUSH | 0.44 | 0.38 |
| LPOP | 0.44 | 0.41 |
| RPOP | 0.44 | 0.38 |
| SADD | 0.44 | 0.36 |
| HSET | 0.44 | 0.39 |
| SPOP | 0.44 | 0.41 |
| ZADD | 0.45 | 0.44 |
| ZPOPMIN | 0.44 | 0.44 |
| LRANGE_100 (first 100 elements) | 0.53 | 0.46 |
| LRANGE_300 (first 300 elements) | 0.74 | 0.75 |
| LRANGE_500 (first 500 elements) | 0.95 | 0.98 |
| LRANGE_600 (first 600 elements) | 1.05 | 1.10 |
| MSET (10 keys) | 0.44 | 0.39 |
Conclusion
From the friendly robots:
In comparing the two Vultr instances, the "High Performance AMD (2 GB, 2 Cores)" shows strong performance in Redis operations, achieving high requests per second with low latencies, and demonstrates solid CPU and memory handling capabilities, with particularly impressive file I/O performance and low latency for memory operations. The "High Performance AMD (8 GB, 4 Cores)" instance also excels in Redis benchmarks with slightly higher requests per second and slightly lower latencies, and it outperforms in CPU handling, showing more throughput and better file I/O capabilities. For CPU-intensive and memory-intensive workloads, the larger configuration with more cores and RAM is superior, while for scenarios focusing on lower latency and high throughput in file I/O operations, the smaller instance is a compelling choice. Therefore, choose the 8 GB, 4 Cores instance for demanding multi-threaded applications and the 2 GB, 2 Cores instance for tasks prioritizing high-speed data handling and lower latency in file operations.
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 link for Vultr.
You can also support me directly by buying me a coffee.