Vultr High Performance Intel (1 GB) vs. Vultr High Performance AMD (2 GB, 2 Cores)
Same showdown, different day. 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 all resided in or around the New York / New Jersey area. Let's get into the numbers.
Overview
| Vultr – High Performance Intel (1 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Last Benchmarked | Sat, 30 May 2026 16:00:52 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 | $6.00 | $18.00 |
| RAM (GB) | 1 | 2 |
| CPU Cores | 1 | 2 |
| Storage (TB) | 25 | 60 |
| Storage Type | NVMe | NVMe |
| Transfer (TB) | 2 | 4 |
CPU
| Vultr – High Performance Intel (1 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Vendor | GenuineIntel | AuthenticAMD |
| Model Name | Intel Xeon Processor (Cascadelake) | AMD EPYC-Genoa Processor |
| Clock Speed (MHz) | 2,893.17 | 2,899.99 |
| CPU Cache Size (KB) | 16,384.00 | 1,024.00 |
| BogoMips | 5,786.33 | 5,799.98 |
| Events per Second | 1,117.86 | 4,648.14 |
| Minimum Latency (ms) | 0.83 | 0.2 |
| Average Latency (ms) | 0.89 | 0.21 |
| Maximum Latency (ms) | 3.92 | 1.26 |
| 95th Percentile Latency (ms) | 1.04 | 0.23 |
Memory
Memory Read
| Vultr – High Performance Intel (1 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 4,957,996.46 | 7,548,502.85 |
| Mebibytes per second | 4,841.79 | 7,371.58 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.83 | 0.08 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – High Performance Intel (1 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 4,994,957.56 | 7,544,807.09 |
| Mebibytes per second | 4,877.89 | 7,367.98 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.96 | 0.12 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – High Performance Intel (1 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Reads per Second | 4,047.78 | 5,114.79 |
| Writes per Second | 2,698.52 | 3,409.86 |
| Fsyncs per Second | 8,646.86 | 10,914.44 |
| Read Mebibytes per Second | 63.25 | 79.92 |
| Written Mebibytes per Second | 42.16 | 53.28 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.06 | 0.05 |
| Maximum Latency (ms) | 3.35 | 3.7 |
| 95th Percentile Latency (ms) | 0.19 | 0.12 |
Mutex
| Vultr – High Performance Intel (1 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 1,571.60 | 574.03 |
| Average Latency (ms) | 1,588.95 | 637.47 |
| Maximum Latency (ms) | 1,599.96 | 663.74 |
| 95th Percentile Latency (ms) | 1,589.90 | 657.93 |
MySQL
MySQL Read-only
| Vultr – High Performance Intel (1 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,137.00 | 9,622.00 |
| Queries per second | 81,370.00 | 96,220.00 |
| Minimum Latency (ms) | 1.08 | 0.73 |
| Average Latency (ms) | 1.23 | 1.04 |
| Maximum Latency (ms) | 6.86 | 2.22 |
| 95th Percentile Latency (ms) | 1.42 | 1.12 |
MySQL Write-only
| Vultr – High Performance Intel (1 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 7,462.00 | 9,585.00 |
| Queries per second | 74,620.00 | 95,850.00 |
| Minimum Latency (ms) | 0.77 | 0.8 |
| Average Latency (ms) | 1.34 | 1.04 |
| Maximum Latency (ms) | 5.26 | 2.18 |
| 95th Percentile Latency (ms) | 1.93 | 1.32 |
MySQL Read/Write
| Vultr – High Performance Intel (1 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 3,070.00 | 4,686.00 |
| Queries per second | 30,700.00 | 46,860.00 |
| Minimum Latency (ms) | 2.45 | 1.57 |
| Average Latency (ms) | 3.25 | 2.13 |
| Maximum Latency (ms) | 8.6 | 4.26 |
| 95th Percentile Latency (ms) | 4.18 | 2.52 |
MySQL INSERT
| Vultr – High Performance Intel (1 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 15,069.00 | 15,965.00 |
| Queries per second | 150,690.00 | 159,650.00 |
| Minimum Latency (ms) | 0.43 | 0.45 |
| Average Latency (ms) | 0.66 | 0.62 |
| Maximum Latency (ms) | 3.39 | 2.23 |
| 95th Percentile Latency (ms) | 0.87 | 0.74 |
MySQL Bulk INSERT
| Vultr – High Performance Intel (1 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 964,103.00 | 3,065,092.00 |
| Queries per second | 9,641,030.00 | 30,650,920.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0 |
| Maximum Latency (ms) | 458.6 | 208.51 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – High Performance Intel (1 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 213,306.00 | 217,035.00 |
| Queries per second | 2,133,060.00 | 2,170,350.00 |
| Minimum Latency (ms) | 0.04 | 0.02 |
| Average Latency (ms) | 0.05 | 0.05 |
| Maximum Latency (ms) | 4.3 | 0.61 |
| 95th Percentile Latency (ms) | 0.07 | 0.06 |
MySQL SELECT (Random Points)
| Vultr – High Performance Intel (1 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 5,672.00 | 14,818.00 |
| Queries per second | 56,720.00 | 148,180.00 |
| Minimum Latency (ms) | 0.58 | 0.24 |
| Average Latency (ms) | 1.76 | 0.67 |
| Maximum Latency (ms) | 8.16 | 1.94 |
| 95th Percentile Latency (ms) | 2.52 | 0.86 |
MySQL SELECT (Random Ranges)
| Vultr – High Performance Intel (1 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 7,910.00 | 14,341.00 |
| Queries per second | 79,100.00 | 143,410.00 |
| Minimum Latency (ms) | 0.43 | 0.27 |
| Average Latency (ms) | 1.26 | 0.7 |
| Maximum Latency (ms) | 3.43 | 1.67 |
| 95th Percentile Latency (ms) | 1.67 | 0.89 |
MySQL UPDATE (Indexed)
| Vultr – High Performance Intel (1 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 13,874.00 | 14,864.00 |
| Queries per second | 138,740.00 | 148,640.00 |
| Minimum Latency (ms) | 0.43 | 0.47 |
| Average Latency (ms) | 0.72 | 0.67 |
| Maximum Latency (ms) | 10.49 | 2.36 |
| 95th Percentile Latency (ms) | 1.08 | 0.87 |
MySQL UPDATE (Non-Indexed)
| Vultr – High Performance Intel (1 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 15,344.00 | 15,284.00 |
| Queries per second | 153,440.00 | 152,840.00 |
| Minimum Latency (ms) | 0.42 | 0.46 |
| Average Latency (ms) | 0.65 | 0.65 |
| Maximum Latency (ms) | 4.43 | 1.65 |
| 95th Percentile Latency (ms) | 0.86 | 0.83 |
MySQL DELETE
| Vultr – High Performance Intel (1 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 83,214.00 | 151,536.00 |
| Queries per second | 832,140.00 | 1,515,360.00 |
| Minimum Latency (ms) | 0.05 | 0.02 |
| Average Latency (ms) | 0.12 | 0.07 |
| Maximum Latency (ms) | 4.88 | 4.83 |
| 95th Percentile Latency (ms) | 0.31 | 0.08 |
Redis
| Vultr – High Performance Intel (1 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE per Second | 45,998.16 | 55,991.04 |
| PING_MBULK per Second | 46,210.72 | 57,903.88 |
| SET per Second | 48,756.70 | 57,703.40 |
| GET per Second | 47,014.57 | 57,703.40 |
| INCR per Second | 46,707.14 | 57,372.34 |
| LPUSH per Second | 46,296.29 | 57,836.90 |
| RPUSH per Second | 45,248.87 | 58,173.36 |
| LPOP per Second | 47,551.12 | 58,343.06 |
| RPOP per Second | 47,573.74 | 58,343.06 |
| SADD per Second | 46,794.57 | 58,241.12 |
| HSET per Second | 42,662.11 | 58,858.15 |
| SPOP per Second | 46,794.57 | 58,892.82 |
| ZADD per Second | 45,433.89 | 57,504.31 |
| ZPOPMIN per Second | 46,296.29 | 57,870.37 |
| LRANGE_100 (first 100 elements) per Second | 24,260.07 | 49,236.83 |
| LRANGE_300 (first 300 elements) per Second | 14,120.31 | 34,818.94 |
| LRANGE_500 (first 500 elements) per Second | 9,612.61 | 26,766.60 |
| LRANGE_600 (first 600 elements) per Second | 8,560.91 | 24,207.21 |
| MSET (10 keys) per Second | 43,859.65 | 58,548.01 |
Redis Average Latency (ms)
| Vultr – High Performance Intel (1 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE | 0.71 | 0.48 |
| PING_MBULK | 0.70 | 0.44 |
| SET | 0.68 | 0.45 |
| GET | 0.70 | 0.45 |
| INCR | 0.71 | 0.45 |
| LPUSH | 0.72 | 0.44 |
| RPUSH | 0.73 | 0.44 |
| LPOP | 0.70 | 0.44 |
| RPOP | 0.70 | 0.44 |
| SADD | 0.70 | 0.44 |
| HSET | 0.76 | 0.44 |
| SPOP | 0.70 | 0.44 |
| ZADD | 0.72 | 0.45 |
| ZPOPMIN | 0.70 | 0.44 |
| LRANGE_100 (first 100 elements) | 1.42 | 0.53 |
| LRANGE_300 (first 300 elements) | 2.51 | 0.74 |
| LRANGE_500 (first 500 elements) | 3.69 | 0.95 |
| LRANGE_600 (first 600 elements) | 4.14 | 1.05 |
| MSET (10 keys) | 0.78 | 0.44 |
Conclusion
From the friendly robots:
Analyzing the benchmark data for both Vultr instances reveals that the AMD-based High Performance AMD (2 GB, 2 Cores) instance generally outperforms the Intel-based High Performance Intel (1 GB) in most metrics. The AMD instance achieves higher requests per second (rps) in Redis operations and better average latencies across various commands, indicating superior single-threaded and multi-threaded performance. The AMD instance also demonstrates higher file I/O throughput and better MySQL performance, with faster bulk inserts and OLTP operations. While both instances perform well, the AMD-based instance's superior metrics in CPU, memory, and I/O operations suggest it is better suited for CPU-intensive and I/O-heavy workloads, making it ideal for applications that benefit from multi-core processing and high data throughput, whereas the Intel-based instance, despite its lower cost, might be more appropriate for simpler, less demanding applications.
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.