Vultr High Frequency Intel (1 GB) vs. Vultr High Performance AMD (2 GB, 2 Cores)
New day, new benchmarks. Today I've spun up some brand new instance from Vultr to run some benchmarks on. Each instance was 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 Frequency Intel (1 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Last Benchmarked | Sat, 30 May 2026 12: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) | 32 | 60 |
| Storage Type | NVMe | NVMe |
| Transfer (TB) | 1 | 4 |
CPU
| Vultr – High Frequency Intel (1 GB) | 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,792.05 | 2,899.99 |
| CPU Cache Size (KB) | 16,384.00 | 1,024.00 |
| BogoMips | 7,584.09 | 5,799.98 |
| Events per Second | 1,546.10 | 4,648.14 |
| Minimum Latency (ms) | 0.62 | 0.2 |
| Average Latency (ms) | 0.65 | 0.21 |
| Maximum Latency (ms) | 2.56 | 1.26 |
| 95th Percentile Latency (ms) | 0.74 | 0.23 |
Memory
Memory Read
| Vultr – High Frequency Intel (1 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 7,548,382.97 | 7,548,502.85 |
| Mebibytes per second | 7,371.47 | 7,371.58 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 1.24 | 0.08 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – High Frequency Intel (1 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 7,119,813.26 | 7,544,807.09 |
| Mebibytes per second | 6,952.94 | 7,367.98 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.15 | 0.12 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – High Frequency Intel (1 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Reads per Second | 4,315.27 | 5,114.79 |
| Writes per Second | 2,876.81 | 3,409.86 |
| Fsyncs per Second | 9,210.59 | 10,914.44 |
| Read Mebibytes per Second | 67.43 | 79.92 |
| Written Mebibytes per Second | 44.95 | 53.28 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.06 | 0.05 |
| Maximum Latency (ms) | 1.42 | 3.7 |
| 95th Percentile Latency (ms) | 0.18 | 0.12 |
Mutex
| Vultr – High Frequency Intel (1 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 1,097.72 | 574.03 |
| Average Latency (ms) | 1,103.69 | 637.47 |
| Maximum Latency (ms) | 1,109.05 | 663.74 |
| 95th Percentile Latency (ms) | 1,109.09 | 657.93 |
MySQL
MySQL Read-only
| Vultr – High Frequency Intel (1 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 10,280.00 | 9,622.00 |
| Queries per second | 102,800.00 | 96,220.00 |
| Minimum Latency (ms) | 0.9 | 0.73 |
| Average Latency (ms) | 0.97 | 1.04 |
| Maximum Latency (ms) | 5.51 | 2.22 |
| 95th Percentile Latency (ms) | 1.06 | 1.12 |
MySQL Write-only
| Vultr – High Frequency Intel (1 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 9,640.00 | 9,585.00 |
| Queries per second | 96,400.00 | 95,850.00 |
| Minimum Latency (ms) | 0.67 | 0.8 |
| Average Latency (ms) | 1.04 | 1.04 |
| Maximum Latency (ms) | 7.17 | 2.18 |
| 95th Percentile Latency (ms) | 1.32 | 1.32 |
MySQL Read/Write
| Vultr – High Frequency Intel (1 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 4,205.00 | 4,686.00 |
| Queries per second | 42,050.00 | 46,860.00 |
| Minimum Latency (ms) | 1.76 | 1.57 |
| Average Latency (ms) | 2.38 | 2.13 |
| Maximum Latency (ms) | 11.16 | 4.26 |
| 95th Percentile Latency (ms) | 3.13 | 2.52 |
MySQL INSERT
| Vultr – High Frequency Intel (1 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 17,283.00 | 15,965.00 |
| Queries per second | 172,830.00 | 159,650.00 |
| Minimum Latency (ms) | 0.38 | 0.45 |
| Average Latency (ms) | 0.58 | 0.62 |
| Maximum Latency (ms) | 5.55 | 2.23 |
| 95th Percentile Latency (ms) | 0.77 | 0.74 |
MySQL Bulk INSERT
| Vultr – High Frequency Intel (1 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 1,841,842.00 | 3,065,092.00 |
| Queries per second | 18,418,420.00 | 30,650,920.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0 |
| Maximum Latency (ms) | 261.29 | 208.51 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – High Frequency Intel (1 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 221,775.00 | 217,035.00 |
| Queries per second | 2,217,750.00 | 2,170,350.00 |
| Minimum Latency (ms) | 0.04 | 0.02 |
| Average Latency (ms) | 0.04 | 0.05 |
| Maximum Latency (ms) | 3.29 | 0.61 |
| 95th Percentile Latency (ms) | 0.06 | 0.06 |
MySQL SELECT (Random Points)
| Vultr – High Frequency Intel (1 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 10,706.00 | 14,818.00 |
| Queries per second | 107,060.00 | 148,180.00 |
| Minimum Latency (ms) | 0.31 | 0.24 |
| Average Latency (ms) | 0.93 | 0.67 |
| Maximum Latency (ms) | 3.42 | 1.94 |
| 95th Percentile Latency (ms) | 1.18 | 0.86 |
MySQL SELECT (Random Ranges)
| Vultr – High Frequency Intel (1 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 11,049.00 | 14,341.00 |
| Queries per second | 110,490.00 | 143,410.00 |
| Minimum Latency (ms) | 0.28 | 0.27 |
| Average Latency (ms) | 0.9 | 0.7 |
| Maximum Latency (ms) | 2.07 | 1.67 |
| 95th Percentile Latency (ms) | 1.16 | 0.89 |
MySQL UPDATE (Indexed)
| Vultr – High Frequency Intel (1 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 15,798.00 | 14,864.00 |
| Queries per second | 157,980.00 | 148,640.00 |
| Minimum Latency (ms) | 0.38 | 0.47 |
| Average Latency (ms) | 0.63 | 0.67 |
| Maximum Latency (ms) | 10.97 | 2.36 |
| 95th Percentile Latency (ms) | 0.86 | 0.87 |
MySQL UPDATE (Non-Indexed)
| Vultr – High Frequency Intel (1 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 15,941.00 | 15,284.00 |
| Queries per second | 159,410.00 | 152,840.00 |
| Minimum Latency (ms) | 0.39 | 0.46 |
| Average Latency (ms) | 0.63 | 0.65 |
| Maximum Latency (ms) | 3.15 | 1.65 |
| 95th Percentile Latency (ms) | 0.84 | 0.83 |
MySQL DELETE
| Vultr – High Frequency Intel (1 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 142,642.00 | 151,536.00 |
| Queries per second | 1,426,420.00 | 1,515,360.00 |
| Minimum Latency (ms) | 0.04 | 0.02 |
| Average Latency (ms) | 0.07 | 0.07 |
| Maximum Latency (ms) | 3.9 | 4.83 |
| 95th Percentile Latency (ms) | 0.1 | 0.08 |
Redis
| Vultr – High Frequency Intel (1 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE per Second | 54,259.36 | 55,991.04 |
| PING_MBULK per Second | 54,764.51 | 57,903.88 |
| SET per Second | 54,259.36 | 57,703.40 |
| GET per Second | 51,786.64 | 57,703.40 |
| INCR per Second | 54,141.85 | 57,372.34 |
| LPUSH per Second | 54,318.30 | 57,836.90 |
| RPUSH per Second | 51,098.62 | 58,173.36 |
| LPOP per Second | 54,141.85 | 58,343.06 |
| RPOP per Second | 54,436.58 | 58,343.06 |
| SADD per Second | 55,218.11 | 58,241.12 |
| HSET per Second | 54,288.82 | 58,858.15 |
| SPOP per Second | 55,524.71 | 58,892.82 |
| ZADD per Second | 54,674.69 | 57,504.31 |
| ZPOPMIN per Second | 54,945.05 | 57,870.37 |
| LRANGE_100 (first 100 elements) per Second | 35,014.01 | 49,236.83 |
| LRANGE_300 (first 300 elements) per Second | 20,161.29 | 34,818.94 |
| LRANGE_500 (first 500 elements) per Second | 14,124.29 | 26,766.60 |
| LRANGE_600 (first 600 elements) per Second | 11,522.06 | 24,207.21 |
| MSET (10 keys) per Second | 44,702.73 | 58,548.01 |
Redis Average Latency (ms)
| Vultr – High Frequency Intel (1 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE | 0.60 | 0.48 |
| PING_MBULK | 0.59 | 0.44 |
| SET | 0.60 | 0.45 |
| GET | 0.63 | 0.45 |
| INCR | 0.60 | 0.45 |
| LPUSH | 0.60 | 0.44 |
| RPUSH | 0.64 | 0.44 |
| LPOP | 0.60 | 0.44 |
| RPOP | 0.60 | 0.44 |
| SADD | 0.58 | 0.44 |
| HSET | 0.60 | 0.44 |
| SPOP | 0.58 | 0.44 |
| ZADD | 0.59 | 0.45 |
| ZPOPMIN | 0.59 | 0.44 |
| LRANGE_100 (first 100 elements) | 0.98 | 0.53 |
| LRANGE_300 (first 300 elements) | 1.73 | 0.74 |
| LRANGE_500 (first 500 elements) | 2.55 | 0.95 |
| LRANGE_600 (first 600 elements) | 3.12 | 1.05 |
| MSET (10 keys) | 0.78 | 0.44 |
Conclusion
From the friendly robots:
The Vultr High Frequency Intel (1 GB) instance shows strong performance for Redis commands with high requests per second (rps) and relatively low latencies, making it ideal for applications that require high Redis throughput, such as cache servers or real-time data processing systems. On the other hand, the Vultr High Performance AMD (2 GB, 2 Cores) instance provides better multi-core performance and is better suited for CPU-intensive workloads, such as large-scale web applications, database servers, or any task that benefits from parallel processing, despite slightly lower Redis rps and higher latencies in some benchmarks. The AMD instance also demonstrates better file I/O and memory performance, which could be advantageous for applications that require high I/O throughput and fast memory operations. Overall, the Intel instance is more cost-effective for memory- and Redis-heavy workloads, while the AMD instance excels in CPU-bound and multi-threaded tasks.
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.