Vultr High Performance AMD (2 GB, 2 Cores) vs. Vultr High Performance Intel (4 GB, 2 Cores)
Same showdown, different day. Today I've spun up some brand new instance from Vultr and ran my world famous suite of benchmarking scripts. Each instance was spun up with 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, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Last Benchmarked | Sun, 31 May 2026 07:00:52 GMT | Fri, 29 May 2026 08: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 | $24.00 |
| RAM (GB) | 2 | 4 |
| CPU Cores | 2 | 2 |
| Storage (TB) | 60 | 100 |
| Storage Type | NVMe | NVMe |
| Transfer (TB) | 4 | 5 |
CPU
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Vendor | AuthenticAMD | GenuineIntel |
| Model Name | AMD EPYC-Genoa Processor | Intel Xeon Processor (Cascadelake) |
| Clock Speed (MHz) | 2,899.99 | 2,992.93 |
| CPU Cache Size (KB) | 1,024.00 | 16,384.00 |
| BogoMips | 5,799.98 | 5,985.85 |
| Events per Second | 4,648.14 | 1,189.71 |
| Minimum Latency (ms) | 0.2 | 0.81 |
| Average Latency (ms) | 0.21 | 0.84 |
| Maximum Latency (ms) | 1.26 | 1.55 |
| 95th Percentile Latency (ms) | 0.23 | 0.92 |
Memory
Memory Read
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 7,548,502.85 | 5,388,530.93 |
| Mebibytes per second | 7,371.58 | 5,262.24 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.08 | 0.68 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 7,544,807.09 | 5,409,821.52 |
| Mebibytes per second | 7,367.98 | 5,283.03 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.12 | 1.24 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Reads per Second | 5,114.79 | 8,517.92 |
| Writes per Second | 3,409.86 | 5,678.61 |
| Fsyncs per Second | 10,914.44 | 18,177.32 |
| Read Mebibytes per Second | 79.92 | 133.09 |
| Written Mebibytes per Second | 53.28 | 88.73 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.05 | 0.03 |
| Maximum Latency (ms) | 3.7 | 3.66 |
| 95th Percentile Latency (ms) | 0.12 | 0.1 |
Mutex
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 574.03 | 731.16 |
| Average Latency (ms) | 637.47 | 765.98 |
| Maximum Latency (ms) | 663.74 | 804.13 |
| 95th Percentile Latency (ms) | 657.93 | 802.05 |
MySQL
MySQL Read-only
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 9,622.00 | 7,840.00 |
| Queries per second | 96,220.00 | 78,400.00 |
| Minimum Latency (ms) | 0.73 | 1.07 |
| Average Latency (ms) | 1.04 | 1.27 |
| Maximum Latency (ms) | 2.22 | 3.93 |
| 95th Percentile Latency (ms) | 1.12 | 1.73 |
MySQL Write-only
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 9,585.00 | 9,079.00 |
| Queries per second | 95,850.00 | 90,790.00 |
| Minimum Latency (ms) | 0.8 | 0.73 |
| Average Latency (ms) | 1.04 | 1.1 |
| Maximum Latency (ms) | 2.18 | 3.41 |
| 95th Percentile Latency (ms) | 1.32 | 1.44 |
MySQL Read/Write
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 4,686.00 | 4,084.00 |
| Queries per second | 46,860.00 | 40,840.00 |
| Minimum Latency (ms) | 1.57 | 1.98 |
| Average Latency (ms) | 2.13 | 2.45 |
| Maximum Latency (ms) | 4.26 | 6.6 |
| 95th Percentile Latency (ms) | 2.52 | 3.13 |
MySQL INSERT
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 15,965.00 | 16,065.00 |
| Queries per second | 159,650.00 | 160,650.00 |
| Minimum Latency (ms) | 0.45 | 0.4 |
| Average Latency (ms) | 0.62 | 0.62 |
| Maximum Latency (ms) | 2.23 | 2.84 |
| 95th Percentile Latency (ms) | 0.74 | 0.84 |
MySQL Bulk INSERT
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 3,065,092.00 | 1,608,842.00 |
| Queries per second | 30,650,920.00 | 16,088,420.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0.01 |
| Maximum Latency (ms) | 208.51 | 296.58 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 217,035.00 | 199,828.00 |
| Queries per second | 2,170,350.00 | 1,998,280.00 |
| Minimum Latency (ms) | 0.02 | 0.03 |
| Average Latency (ms) | 0.05 | 0.05 |
| Maximum Latency (ms) | 0.61 | 3.21 |
| 95th Percentile Latency (ms) | 0.06 | 0.07 |
MySQL SELECT (Random Points)
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 14,818.00 | 7,759.00 |
| Queries per second | 148,180.00 | 77,590.00 |
| Minimum Latency (ms) | 0.24 | 0.34 |
| Average Latency (ms) | 0.67 | 1.29 |
| Maximum Latency (ms) | 1.94 | 3.41 |
| 95th Percentile Latency (ms) | 0.86 | 1.7 |
MySQL SELECT (Random Ranges)
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 14,341.00 | 8,104.00 |
| Queries per second | 143,410.00 | 81,040.00 |
| Minimum Latency (ms) | 0.27 | 0.43 |
| Average Latency (ms) | 0.7 | 1.23 |
| Maximum Latency (ms) | 1.67 | 2.94 |
| 95th Percentile Latency (ms) | 0.89 | 1.64 |
MySQL UPDATE (Indexed)
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 14,864.00 | 16,223.00 |
| Queries per second | 148,640.00 | 162,230.00 |
| Minimum Latency (ms) | 0.47 | 0.4 |
| Average Latency (ms) | 0.67 | 0.62 |
| Maximum Latency (ms) | 2.36 | 8.91 |
| 95th Percentile Latency (ms) | 0.87 | 0.86 |
MySQL UPDATE (Non-Indexed)
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 15,284.00 | 17,156.00 |
| Queries per second | 152,840.00 | 171,560.00 |
| Minimum Latency (ms) | 0.46 | 0.39 |
| Average Latency (ms) | 0.65 | 0.58 |
| Maximum Latency (ms) | 1.65 | 2.17 |
| 95th Percentile Latency (ms) | 0.83 | 0.77 |
MySQL DELETE
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 151,536.00 | 146,778.00 |
| Queries per second | 1,515,360.00 | 1,467,780.00 |
| Minimum Latency (ms) | 0.02 | 0.03 |
| Average Latency (ms) | 0.07 | 0.07 |
| Maximum Latency (ms) | 4.83 | 3.33 |
| 95th Percentile Latency (ms) | 0.08 | 0.09 |
Redis
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE per Second | 55,991.04 | 67,069.08 |
| PING_MBULK per Second | 57,903.88 | 68,212.83 |
| SET per Second | 57,703.40 | 68,634.18 |
| GET per Second | 57,703.40 | 67,476.38 |
| INCR per Second | 57,372.34 | 67,704.80 |
| LPUSH per Second | 57,836.90 | 66,844.91 |
| RPUSH per Second | 58,173.36 | 69,541.03 |
| LPOP per Second | 58,343.06 | 68,870.52 |
| RPOP per Second | 58,343.06 | 67,888.66 |
| SADD per Second | 58,241.12 | 69,108.50 |
| HSET per Second | 58,858.15 | 68,917.99 |
| SPOP per Second | 58,892.82 | 68,027.21 |
| ZADD per Second | 57,504.31 | 68,681.32 |
| ZPOPMIN per Second | 57,870.37 | 67,796.61 |
| LRANGE_100 (first 100 elements) per Second | 49,236.83 | 51,361.07 |
| LRANGE_300 (first 300 elements) per Second | 34,818.94 | 27,382.26 |
| LRANGE_500 (first 500 elements) per Second | 26,766.60 | 19,157.09 |
| LRANGE_600 (first 600 elements) per Second | 24,207.21 | 17,301.04 |
| MSET (10 keys) per Second | 58,548.01 | 69,541.03 |
Redis Average Latency (ms)
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE | 0.48 | 0.39 |
| PING_MBULK | 0.44 | 0.38 |
| SET | 0.45 | 0.38 |
| GET | 0.45 | 0.38 |
| INCR | 0.45 | 0.38 |
| LPUSH | 0.44 | 0.39 |
| RPUSH | 0.44 | 0.37 |
| LPOP | 0.44 | 0.38 |
| RPOP | 0.44 | 0.38 |
| SADD | 0.44 | 0.37 |
| HSET | 0.44 | 0.38 |
| SPOP | 0.44 | 0.38 |
| ZADD | 0.45 | 0.38 |
| ZPOPMIN | 0.44 | 0.38 |
| LRANGE_100 (first 100 elements) | 0.53 | 0.51 |
| LRANGE_300 (first 300 elements) | 0.74 | 1.01 |
| LRANGE_500 (first 500 elements) | 0.95 | 1.45 |
| LRANGE_600 (first 600 elements) | 1.05 | 1.53 |
| MSET (10 keys) | 0.44 | 0.38 |
Conclusion
From the friendly robots:
Both instances showcase strong performance in various benchmarks, but the Vultr High Performance Intel (4 GB, 2 Cores) instance generally outperforms the Vultr High Performance AMD (2 GB, 2 Cores) in terms of metrics such as Redis throughput, CPU performance, and file I/O operations. The Intel variant excels in Redis commands like LRANGE with lower latencies and higher request per second rates, as well as in CPU event processing and file I/O operations, reflecting a more substantial throughput and lower average latencies. However, the AMD instance offers competitive performance in memory operations and mutex execution, alongside a lower monthly cost. Ideal use cases for the Intel instance would be CPU-intensive, high-throughput applications, while the AMD instance may be more suited for scenarios requiring balanced performance with a focus on cost-efficiency and adequate memory and I/O 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.