Vultr Cloud Compute (2 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 and did some benchmarking. All instances were running Ubuntu 24.04 LTS x64 and all resided in or around the New York / New Jersey area. Enough talk. Here's the data.
Overview
| Vultr – Cloud Compute (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Last Benchmarked | Sat, 30 May 2026 03: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 | $10.00 | $18.00 |
| RAM (GB) | 2 | 2 |
| CPU Cores | 1 | 2 |
| Storage (TB) | 50 | 60 |
| Storage Type | SSD | NVMe |
| Transfer (TB) | 2 | 4 |
CPU
| Vultr – Cloud Compute (2 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,791.92 | 2,899.99 |
| CPU Cache Size (KB) | 16,384.00 | 1,024.00 |
| BogoMips | 7,583.84 | 5,799.98 |
| Events per Second | 1,473.75 | 4,648.14 |
| Minimum Latency (ms) | 0.63 | 0.2 |
| Average Latency (ms) | 0.68 | 0.21 |
| Maximum Latency (ms) | 3.12 | 1.26 |
| 95th Percentile Latency (ms) | 0.75 | 0.23 |
Memory
Memory Read
| Vultr – Cloud Compute (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 6,820,350.62 | 7,548,502.85 |
| Mebibytes per second | 6,660.50 | 7,371.58 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.31 | 0.08 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – Cloud Compute (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 6,454,818.09 | 7,544,807.09 |
| Mebibytes per second | 6,303.53 | 7,367.98 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.66 | 0.12 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – Cloud Compute (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Reads per Second | 4,389.79 | 5,114.79 |
| Writes per Second | 2,926.52 | 3,409.86 |
| Fsyncs per Second | 9,376.39 | 10,914.44 |
| Read Mebibytes per Second | 68.59 | 79.92 |
| Written Mebibytes per Second | 45.73 | 53.28 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.06 | 0.05 |
| Maximum Latency (ms) | 31.02 | 3.7 |
| 95th Percentile Latency (ms) | 0.17 | 0.12 |
Mutex
| Vultr – Cloud Compute (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 1,262.77 | 574.03 |
| Average Latency (ms) | 1,272.88 | 637.47 |
| Maximum Latency (ms) | 1,285.30 | 663.74 |
| 95th Percentile Latency (ms) | 1,280.93 | 657.93 |
MySQL
MySQL Read-only
| Vultr – Cloud Compute (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 9,122.00 | 9,622.00 |
| Queries per second | 91,220.00 | 96,220.00 |
| Minimum Latency (ms) | 0.92 | 0.73 |
| Average Latency (ms) | 1.09 | 1.04 |
| Maximum Latency (ms) | 3.36 | 2.22 |
| 95th Percentile Latency (ms) | 1.5 | 1.12 |
MySQL Write-only
| Vultr – Cloud Compute (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 6,552.00 | 9,585.00 |
| Queries per second | 65,520.00 | 95,850.00 |
| Minimum Latency (ms) | 0.68 | 0.8 |
| Average Latency (ms) | 1.52 | 1.04 |
| Maximum Latency (ms) | 263.27 | 2.18 |
| 95th Percentile Latency (ms) | 1.61 | 1.32 |
MySQL Read/Write
| Vultr – Cloud Compute (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 3,107.00 | 4,686.00 |
| Queries per second | 31,070.00 | 46,860.00 |
| Minimum Latency (ms) | 2.29 | 1.57 |
| Average Latency (ms) | 3.22 | 2.13 |
| Maximum Latency (ms) | 47.81 | 4.26 |
| 95th Percentile Latency (ms) | 4.18 | 2.52 |
MySQL INSERT
| Vultr – Cloud Compute (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 15,510.00 | 15,965.00 |
| Queries per second | 155,100.00 | 159,650.00 |
| Minimum Latency (ms) | 0.39 | 0.45 |
| Average Latency (ms) | 0.64 | 0.62 |
| Maximum Latency (ms) | 16.42 | 2.23 |
| 95th Percentile Latency (ms) | 0.87 | 0.74 |
MySQL Bulk INSERT
| Vultr – Cloud Compute (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 1,463,217.00 | 3,065,092.00 |
| Queries per second | 14,632,170.00 | 30,650,920.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0 |
| Maximum Latency (ms) | 376.55 | 208.51 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – Cloud Compute (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 210,316.00 | 217,035.00 |
| Queries per second | 2,103,160.00 | 2,170,350.00 |
| Minimum Latency (ms) | 0.04 | 0.02 |
| Average Latency (ms) | 0.05 | 0.05 |
| Maximum Latency (ms) | 1.67 | 0.61 |
| 95th Percentile Latency (ms) | 0.07 | 0.06 |
MySQL SELECT (Random Points)
| Vultr – Cloud Compute (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,048.00 | 14,818.00 |
| Queries per second | 80,480.00 | 148,180.00 |
| Minimum Latency (ms) | 0.37 | 0.24 |
| Average Latency (ms) | 1.24 | 0.67 |
| Maximum Latency (ms) | 4.78 | 1.94 |
| 95th Percentile Latency (ms) | 1.96 | 0.86 |
MySQL SELECT (Random Ranges)
| Vultr – Cloud Compute (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,555.00 | 14,341.00 |
| Queries per second | 85,550.00 | 143,410.00 |
| Minimum Latency (ms) | 0.32 | 0.27 |
| Average Latency (ms) | 1.17 | 0.7 |
| Maximum Latency (ms) | 5.25 | 1.67 |
| 95th Percentile Latency (ms) | 2.48 | 0.89 |
MySQL UPDATE (Indexed)
| Vultr – Cloud Compute (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 11,650.00 | 14,864.00 |
| Queries per second | 116,500.00 | 148,640.00 |
| Minimum Latency (ms) | 0.4 | 0.47 |
| Average Latency (ms) | 0.86 | 0.67 |
| Maximum Latency (ms) | 39.27 | 2.36 |
| 95th Percentile Latency (ms) | 1.39 | 0.87 |
MySQL UPDATE (Non-Indexed)
| Vultr – Cloud Compute (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 13,004.00 | 15,284.00 |
| Queries per second | 130,040.00 | 152,840.00 |
| Minimum Latency (ms) | 0.4 | 0.46 |
| Average Latency (ms) | 0.77 | 0.65 |
| Maximum Latency (ms) | 13.05 | 1.65 |
| 95th Percentile Latency (ms) | 1.1 | 0.83 |
MySQL DELETE
| Vultr – Cloud Compute (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 110,717.00 | 151,536.00 |
| Queries per second | 1,107,170.00 | 1,515,360.00 |
| Minimum Latency (ms) | 0.04 | 0.02 |
| Average Latency (ms) | 0.09 | 0.07 |
| Maximum Latency (ms) | 25.53 | 4.83 |
| 95th Percentile Latency (ms) | 0.13 | 0.08 |
Redis
| Vultr – Cloud Compute (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE per Second | 52,882.07 | 55,991.04 |
| PING_MBULK per Second | 55,218.11 | 57,903.88 |
| SET per Second | 53,191.49 | 57,703.40 |
| GET per Second | 53,705.69 | 57,703.40 |
| INCR per Second | 52,273.91 | 57,372.34 |
| LPUSH per Second | 46,904.32 | 57,836.90 |
| RPUSH per Second | 52,002.08 | 58,173.36 |
| LPOP per Second | 53,078.56 | 58,343.06 |
| RPOP per Second | 52,742.62 | 58,343.06 |
| SADD per Second | 52,938.06 | 58,241.12 |
| HSET per Second | 53,106.74 | 58,858.15 |
| SPOP per Second | 50,403.23 | 58,892.82 |
| ZADD per Second | 49,726.51 | 57,504.31 |
| ZPOPMIN per Second | 53,504.55 | 57,870.37 |
| LRANGE_100 (first 100 elements) per Second | 34,770.52 | 49,236.83 |
| LRANGE_300 (first 300 elements) per Second | 17,091.10 | 34,818.94 |
| LRANGE_500 (first 500 elements) per Second | 11,966.02 | 26,766.60 |
| LRANGE_600 (first 600 elements) per Second | 10,231.23 | 24,207.21 |
| MSET (10 keys) per Second | 49,358.34 | 58,548.01 |
Redis Average Latency (ms)
| Vultr – Cloud Compute (2 GB) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE | 0.62 | 0.48 |
| PING_MBULK | 0.58 | 0.44 |
| SET | 0.62 | 0.45 |
| GET | 0.61 | 0.45 |
| INCR | 0.63 | 0.45 |
| LPUSH | 0.71 | 0.44 |
| RPUSH | 0.63 | 0.44 |
| LPOP | 0.63 | 0.44 |
| RPOP | 0.63 | 0.44 |
| SADD | 0.62 | 0.44 |
| HSET | 0.62 | 0.44 |
| SPOP | 0.65 | 0.44 |
| ZADD | 0.67 | 0.45 |
| ZPOPMIN | 0.62 | 0.44 |
| LRANGE_100 (first 100 elements) | 0.98 | 0.53 |
| LRANGE_300 (first 300 elements) | 2.06 | 0.74 |
| LRANGE_500 (first 500 elements) | 2.98 | 0.95 |
| LRANGE_600 (first 600 elements) | 3.47 | 1.05 |
| MSET (10 keys) | 0.70 | 0.44 |
Conclusion
From the friendly robots:
After analyzing the benchmark performance of the Vultr Cloud Compute (2 GB) and Vultr High Performance AMD (2 GB, 2 Cores) instances, it is clear that the AMD instance excels in multi-core performance metrics, demonstrating higher throughput in Redis operations, CPU event handling, file I/O, and MySQL operations compared to the single-core Intel instance. The AMD instance offers significantly better performance in handling concurrent operations and data-intensive tasks due to its dual-core architecture, resulting in lower latency and higher requests per second in various benchmarks. Conversely, the Cloud Compute instance, while still competent, lags in multi-threaded tasks, showcasing higher latencies in certain benchmarks. The AMD instance is ideal for workloads that benefit from multiple cores and higher throughput, such as data processing, web servers with high concurrency, or databases, while the Cloud Compute instance might be more suitable for simpler, less data-intensive tasks or for cost-sensitive applications where a single core suffices.
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.