Vultr High Frequency Intel (2 GB, 2 Cores) vs. Vultr High Performance AMD (2 GB, 2 Cores)
Welcome to another round of the VPS Showdown. Today I've spun up some brand new instance from Vultr and ran some benchmarks. All instances were running Ubuntu 24.04 LTS x64 and were created in or around the New York / New Jersey area. Let's get into the numbers.
Overview
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Last Benchmarked | Sun, 31 May 2026 13:00:55 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 | $18.00 | $18.00 |
| RAM (GB) | 2 | 2 |
| CPU Cores | 2 | 2 |
| Storage (TB) | 80 | 60 |
| Storage Type | NVMe | NVMe |
| Transfer (TB) | 3 | 4 |
CPU
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Vendor | GenuineIntel | AuthenticAMD |
| Model Name | Intel Core Processor (Skylake, IBRS, no TSX) | AMD EPYC-Genoa Processor |
| Clock Speed (MHz) | 3,791.98 | 2,899.99 |
| CPU Cache Size (KB) | 16,384.00 | 1,024.00 |
| BogoMips | 7,583.95 | 5,799.98 |
| Events per Second | 1,552.05 | 4,648.14 |
| Minimum Latency (ms) | 0.62 | 0.2 |
| Average Latency (ms) | 0.64 | 0.21 |
| Maximum Latency (ms) | 4.61 | 1.26 |
| 95th Percentile Latency (ms) | 0.69 | 0.23 |
Memory
Memory Read
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 7,875,668.83 | 7,548,502.85 |
| Mebibytes per second | 7,691.08 | 7,371.58 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.12 | 0.08 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 7,729,812.11 | 7,544,807.09 |
| Mebibytes per second | 7,548.64 | 7,367.98 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.16 | 0.12 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Reads per Second | 4,671.85 | 5,114.79 |
| Writes per Second | 3,114.56 | 3,409.86 |
| Fsyncs per Second | 9,976.90 | 10,914.44 |
| Read Mebibytes per Second | 73.00 | 79.92 |
| Written Mebibytes per Second | 48.67 | 53.28 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.06 | 0.05 |
| Maximum Latency (ms) | 2.76 | 3.7 |
| 95th Percentile Latency (ms) | 0.17 | 0.12 |
Mutex
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 543.27 | 574.03 |
| Average Latency (ms) | 554.74 | 637.47 |
| Maximum Latency (ms) | 563.70 | 663.74 |
| 95th Percentile Latency (ms) | 559.50 | 657.93 |
MySQL
MySQL Read-only
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 10,621.00 | 9,622.00 |
| Queries per second | 106,210.00 | 96,220.00 |
| Minimum Latency (ms) | 0.86 | 0.73 |
| Average Latency (ms) | 0.94 | 1.04 |
| Maximum Latency (ms) | 2.5 | 2.22 |
| 95th Percentile Latency (ms) | 1.03 | 1.12 |
MySQL Write-only
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 10,229.00 | 9,585.00 |
| Queries per second | 102,290.00 | 95,850.00 |
| Minimum Latency (ms) | 0.64 | 0.8 |
| Average Latency (ms) | 0.98 | 1.04 |
| Maximum Latency (ms) | 2.08 | 2.18 |
| 95th Percentile Latency (ms) | 1.23 | 1.32 |
MySQL Read/Write
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 5,072.00 | 4,686.00 |
| Queries per second | 50,720.00 | 46,860.00 |
| Minimum Latency (ms) | 1.59 | 1.57 |
| Average Latency (ms) | 1.97 | 2.13 |
| Maximum Latency (ms) | 3.94 | 4.26 |
| 95th Percentile Latency (ms) | 2.39 | 2.52 |
MySQL INSERT
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 16,038.00 | 15,965.00 |
| Queries per second | 160,380.00 | 159,650.00 |
| Minimum Latency (ms) | 0.38 | 0.45 |
| Average Latency (ms) | 0.62 | 0.62 |
| Maximum Latency (ms) | 13.18 | 2.23 |
| 95th Percentile Latency (ms) | 0.8 | 0.74 |
MySQL Bulk INSERT
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 2,424,342.00 | 3,065,092.00 |
| Queries per second | 24,243,420.00 | 30,650,920.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 205.81 | 208.51 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 241,313.00 | 217,035.00 |
| Queries per second | 2,413,130.00 | 2,170,350.00 |
| Minimum Latency (ms) | 0.03 | 0.02 |
| Average Latency (ms) | 0.04 | 0.05 |
| Maximum Latency (ms) | 0.76 | 0.61 |
| 95th Percentile Latency (ms) | 0.05 | 0.06 |
MySQL SELECT (Random Points)
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 12,080.00 | 14,818.00 |
| Queries per second | 120,800.00 | 148,180.00 |
| Minimum Latency (ms) | 0.21 | 0.24 |
| Average Latency (ms) | 0.83 | 0.67 |
| Maximum Latency (ms) | 3.31 | 1.94 |
| 95th Percentile Latency (ms) | 1.04 | 0.86 |
MySQL SELECT (Random Ranges)
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 10,527.00 | 14,341.00 |
| Queries per second | 105,270.00 | 143,410.00 |
| Minimum Latency (ms) | 0.16 | 0.27 |
| Average Latency (ms) | 0.95 | 0.7 |
| Maximum Latency (ms) | 3.25 | 1.67 |
| 95th Percentile Latency (ms) | 1.23 | 0.89 |
MySQL UPDATE (Indexed)
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 17,123.00 | 14,864.00 |
| Queries per second | 171,230.00 | 148,640.00 |
| Minimum Latency (ms) | 0.38 | 0.47 |
| Average Latency (ms) | 0.58 | 0.67 |
| Maximum Latency (ms) | 2 | 2.36 |
| 95th Percentile Latency (ms) | 0.78 | 0.87 |
MySQL UPDATE (Non-Indexed)
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 16,979.00 | 15,284.00 |
| Queries per second | 169,790.00 | 152,840.00 |
| Minimum Latency (ms) | 0.38 | 0.46 |
| Average Latency (ms) | 0.59 | 0.65 |
| Maximum Latency (ms) | 4.13 | 1.65 |
| 95th Percentile Latency (ms) | 0.8 | 0.83 |
MySQL DELETE
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 156,424.00 | 151,536.00 |
| Queries per second | 1,564,240.00 | 1,515,360.00 |
| Minimum Latency (ms) | 0.03 | 0.02 |
| Average Latency (ms) | 0.06 | 0.07 |
| Maximum Latency (ms) | 4.87 | 4.83 |
| 95th Percentile Latency (ms) | 0.07 | 0.08 |
Redis
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE per Second | 88,652.48 | 55,991.04 |
| PING_MBULK per Second | 89,605.73 | 57,903.88 |
| SET per Second | 90,171.33 | 57,703.40 |
| GET per Second | 90,579.71 | 57,703.40 |
| INCR per Second | 90,744.10 | 57,372.34 |
| LPUSH per Second | 90,497.73 | 57,836.90 |
| RPUSH per Second | 90,415.91 | 58,173.36 |
| LPOP per Second | 90,909.09 | 58,343.06 |
| RPOP per Second | 90,661.83 | 58,343.06 |
| SADD per Second | 90,252.70 | 58,241.12 |
| HSET per Second | 90,415.91 | 58,858.15 |
| SPOP per Second | 89,928.05 | 58,892.82 |
| ZADD per Second | 90,415.91 | 57,504.31 |
| ZPOPMIN per Second | 90,009.01 | 57,870.37 |
| LRANGE_100 (first 100 elements) per Second | 66,533.60 | 49,236.83 |
| LRANGE_300 (first 300 elements) per Second | 36,179.45 | 34,818.94 |
| LRANGE_500 (first 500 elements) per Second | 26,239.83 | 26,766.60 |
| LRANGE_600 (first 600 elements) per Second | 22,547.91 | 24,207.21 |
| MSET (10 keys) per Second | 88,105.73 | 58,548.01 |
Redis Average Latency (ms)
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE | 0.30 | 0.48 |
| PING_MBULK | 0.29 | 0.44 |
| SET | 0.29 | 0.45 |
| GET | 0.29 | 0.45 |
| INCR | 0.28 | 0.45 |
| LPUSH | 0.29 | 0.44 |
| RPUSH | 0.29 | 0.44 |
| LPOP | 0.28 | 0.44 |
| RPOP | 0.28 | 0.44 |
| SADD | 0.29 | 0.44 |
| HSET | 0.29 | 0.44 |
| SPOP | 0.29 | 0.44 |
| ZADD | 0.29 | 0.45 |
| ZPOPMIN | 0.29 | 0.44 |
| LRANGE_100 (first 100 elements) | 0.39 | 0.53 |
| LRANGE_300 (first 300 elements) | 0.71 | 0.74 |
| LRANGE_500 (first 500 elements) | 0.97 | 0.95 |
| LRANGE_600 (first 600 elements) | 1.14 | 1.05 |
| MSET (10 keys) | 0.30 | 0.44 |
Conclusion
From the friendly robots:
Comparing the benchmarks, the Vultr High Frequency Intel instance delivers higher Redis performance rates for most operations, notably reaching around 91,000 requests per second for basic commands like GET and SET, and significantly better file I/O throughput with 70.39 MiB/s reads and 46.92 MiB/s writes. The AMD EPYC-based Vultr High Performance instance, while showing respectable performance, trails behind with lower Redis request rates averaging around 58,000 requests per second for similar commands and lower file I/O throughput at 79.27 MiB/s reads and 52.85 MiB/s writes. The Intel instance also excels in MySQL operations, particularly bulk inserts and read-heavy OLTP tasks. While both instances perform well in memory operations and thread fairness, the Intel instance maintains the edge in overall performance metrics, making it more suitable for CPU-intensive workloads and applications requiring high throughput and low latency. The AMD instance, despite its lower absolute performance, could still be a strong contender for applications that prioritize cost-effectiveness over peak performance.
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.