Vultr High Performance AMD (2 GB) vs. Vultr High Performance AMD (2 GB, 2 Cores)
My friend, I'm so glad you're here! Today I've spun up brand new instance from Vultr and ran my world famous suite of benchmarking scripts. 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
| Vultr – High Performance AMD (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Last Benchmarked | Fri, 29 May 2026 13: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-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 | $12.00 | $18.00 |
| RAM (GB) | 2 | 2 |
| CPU Cores | 1 | 2 |
| Storage (TB) | 50 | 60 |
| Storage Type | NVMe | NVMe |
| Transfer (TB) | 3 | 4 |
CPU
| Vultr – High Performance AMD (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Vendor | AuthenticAMD | AuthenticAMD |
| Model Name | AMD EPYC-Genoa Processor | AMD EPYC-Genoa Processor |
| Clock Speed (MHz) | 2,900.00 | 2,899.99 |
| CPU Cache Size (KB) | 1,024.00 | 1,024.00 |
| BogoMips | 5,800.00 | 5,799.98 |
| Events per Second | 4,571.75 | 4,648.14 |
| Minimum Latency (ms) | 0.21 | 0.2 |
| Average Latency (ms) | 0.22 | 0.21 |
| Maximum Latency (ms) | 3.35 | 1.26 |
| 95th Percentile Latency (ms) | 0.23 | 0.23 |
Memory
Memory Read
| Vultr – High Performance AMD (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 7,459,554.27 | 7,548,502.85 |
| Mebibytes per second | 7,284.72 | 7,371.58 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.58 | 0.08 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – High Performance AMD (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 7,475,561.40 | 7,544,807.09 |
| Mebibytes per second | 7,300.35 | 7,367.98 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.27 | 0.12 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – High Performance AMD (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Reads per Second | 5,083.40 | 5,114.79 |
| Writes per Second | 3,388.87 | 3,409.86 |
| Fsyncs per Second | 10,846.93 | 10,914.44 |
| Read Mebibytes per Second | 79.43 | 79.92 |
| Written Mebibytes per Second | 52.95 | 53.28 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.05 | 0.05 |
| Maximum Latency (ms) | 8.54 | 3.7 |
| 95th Percentile Latency (ms) | 0.12 | 0.12 |
Mutex
| Vultr – High Performance AMD (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 1,261.44 | 574.03 |
| Average Latency (ms) | 1,266.47 | 637.47 |
| Maximum Latency (ms) | 1,274.11 | 663.74 |
| 95th Percentile Latency (ms) | 1,280.93 | 657.93 |
MySQL
MySQL Read-only
| Vultr – High Performance AMD (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 12,567.00 | 9,622.00 |
| Queries per second | 125,670.00 | 96,220.00 |
| Minimum Latency (ms) | 0.71 | 0.73 |
| Average Latency (ms) | 0.79 | 1.04 |
| Maximum Latency (ms) | 3.08 | 2.22 |
| 95th Percentile Latency (ms) | 0.94 | 1.12 |
MySQL Write-only
| Vultr – High Performance AMD (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 10,288.00 | 9,585.00 |
| Queries per second | 102,880.00 | 95,850.00 |
| Minimum Latency (ms) | 0.65 | 0.8 |
| Average Latency (ms) | 0.97 | 1.04 |
| Maximum Latency (ms) | 3.2 | 2.18 |
| 95th Percentile Latency (ms) | 1.34 | 1.32 |
MySQL Read/Write
| Vultr – High Performance AMD (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 4,897.00 | 4,686.00 |
| Queries per second | 48,970.00 | 46,860.00 |
| Minimum Latency (ms) | 1.61 | 1.57 |
| Average Latency (ms) | 2.04 | 2.13 |
| Maximum Latency (ms) | 5.14 | 4.26 |
| 95th Percentile Latency (ms) | 2.57 | 2.52 |
MySQL INSERT
| Vultr – High Performance AMD (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 16,170.00 | 15,965.00 |
| Queries per second | 161,700.00 | 159,650.00 |
| Minimum Latency (ms) | 0.43 | 0.45 |
| Average Latency (ms) | 0.62 | 0.62 |
| Maximum Latency (ms) | 18.34 | 2.23 |
| 95th Percentile Latency (ms) | 0.74 | 0.74 |
MySQL Bulk INSERT
| Vultr – High Performance AMD (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 2,408,418.00 | 3,065,092.00 |
| Queries per second | 24,084,180.00 | 30,650,920.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 221.46 | 208.51 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – High Performance AMD (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 326,079.00 | 217,035.00 |
| Queries per second | 3,260,790.00 | 2,170,350.00 |
| Minimum Latency (ms) | 0.03 | 0.02 |
| Average Latency (ms) | 0.03 | 0.05 |
| Maximum Latency (ms) | 3.17 | 0.61 |
| 95th Percentile Latency (ms) | 0.04 | 0.06 |
MySQL SELECT (Random Points)
| Vultr – High Performance AMD (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 14,308.00 | 14,818.00 |
| Queries per second | 143,080.00 | 148,180.00 |
| Minimum Latency (ms) | 0.16 | 0.24 |
| Average Latency (ms) | 0.7 | 0.67 |
| Maximum Latency (ms) | 3.35 | 1.94 |
| 95th Percentile Latency (ms) | 0.89 | 0.86 |
MySQL SELECT (Random Ranges)
| Vultr – High Performance AMD (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 14,222.00 | 14,341.00 |
| Queries per second | 142,220.00 | 143,410.00 |
| Minimum Latency (ms) | 0.26 | 0.27 |
| Average Latency (ms) | 0.7 | 0.7 |
| Maximum Latency (ms) | 3.04 | 1.67 |
| 95th Percentile Latency (ms) | 0.9 | 0.89 |
MySQL UPDATE (Indexed)
| Vultr – High Performance AMD (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 15,111.00 | 14,864.00 |
| Queries per second | 151,110.00 | 148,640.00 |
| Minimum Latency (ms) | 0.43 | 0.47 |
| Average Latency (ms) | 0.66 | 0.67 |
| Maximum Latency (ms) | 3.73 | 2.36 |
| 95th Percentile Latency (ms) | 1.01 | 0.87 |
MySQL UPDATE (Non-Indexed)
| Vultr – High Performance AMD (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 15,910.00 | 15,284.00 |
| Queries per second | 159,100.00 | 152,840.00 |
| Minimum Latency (ms) | 0.42 | 0.46 |
| Average Latency (ms) | 0.63 | 0.65 |
| Maximum Latency (ms) | 3.9 | 1.65 |
| 95th Percentile Latency (ms) | 0.9 | 0.83 |
MySQL DELETE
| Vultr – High Performance AMD (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 194,308.00 | 151,536.00 |
| Queries per second | 1,943,080.00 | 1,515,360.00 |
| Minimum Latency (ms) | 0.02 | 0.02 |
| Average Latency (ms) | 0.05 | 0.07 |
| Maximum Latency (ms) | 3.02 | 4.83 |
| 95th Percentile Latency (ms) | 0.08 | 0.08 |
Redis
| Vultr – High Performance AMD (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE per Second | 40,273.86 | 55,991.04 |
| PING_MBULK per Second | 41,186.16 | 57,903.88 |
| SET per Second | 40,749.80 | 57,703.40 |
| GET per Second | 40,983.61 | 57,703.40 |
| INCR per Second | 40,866.37 | 57,372.34 |
| LPUSH per Second | 40,716.61 | 57,836.90 |
| RPUSH per Second | 40,766.41 | 58,173.36 |
| LPOP per Second | 40,966.82 | 58,343.06 |
| RPOP per Second | 35,536.61 | 58,343.06 |
| SADD per Second | 41,220.11 | 58,241.12 |
| HSET per Second | 40,453.08 | 58,858.15 |
| SPOP per Second | 41,649.31 | 58,892.82 |
| ZADD per Second | 41,631.97 | 57,504.31 |
| ZPOPMIN per Second | 41,963.91 | 57,870.37 |
| LRANGE_100 (first 100 elements) per Second | 32,701.11 | 49,236.83 |
| LRANGE_300 (first 300 elements) per Second | 21,114.87 | 34,818.94 |
| LRANGE_500 (first 500 elements) per Second | 15,974.44 | 26,766.60 |
| LRANGE_600 (first 600 elements) per Second | 14,202.53 | 24,207.21 |
| MSET (10 keys) per Second | 39,651.07 | 58,548.01 |
Redis Average Latency (ms)
| Vultr – High Performance AMD (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE | 0.82 | 0.48 |
| PING_MBULK | 0.81 | 0.44 |
| SET | 0.82 | 0.45 |
| GET | 0.81 | 0.45 |
| INCR | 0.81 | 0.45 |
| LPUSH | 0.81 | 0.44 |
| RPUSH | 0.81 | 0.44 |
| LPOP | 0.82 | 0.44 |
| RPOP | 0.95 | 0.44 |
| SADD | 0.81 | 0.44 |
| HSET | 0.83 | 0.44 |
| SPOP | 0.80 | 0.44 |
| ZADD | 0.80 | 0.45 |
| ZPOPMIN | 0.79 | 0.44 |
| LRANGE_100 (first 100 elements) | 1.01 | 0.53 |
| LRANGE_300 (first 300 elements) | 1.55 | 0.74 |
| LRANGE_500 (first 500 elements) | 2.08 | 0.95 |
| LRANGE_600 (first 600 elements) | 2.33 | 1.05 |
| MSET (10 keys) | 0.85 | 0.44 |
Conclusion
From the friendly robots:
After analyzing the benchmark results, it's evident that the Vultr High Performance AMD (2 GB, 2 Cores) instance outperforms the Vultr High Performance AMD (2 GB) instance in several key metrics. The dual-core version demonstrates significantly higher performance in Redis benchmarks, notably achieving much higher requests per second (rps) across various commands like PING_INLINE, SET, GET, and LPUSH, which suggests it handles concurrent read/write operations more efficiently. CPU performance also favors the dual-core instance, showing better thread fairness and lower latency in CPU-bound tasks. File I/O and memory benchmarks similarly reflect this trend with faster read and write operations per second, and lower latency in memory operations. For developers and sysadmins, the dual-core instance is ideal for CPU-intensive and I/O-heavy workloads where higher concurrency and throughput are critical, such as high-traffic web servers, database servers, or applications requiring substantial parallel processing.
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.