Vultr Cloud Compute (2 GB, 2 Cores) vs. Vultr High Performance AMD (2 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. All instances were spun up with 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 – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Last Benchmarked | Mon, 11 May 2026 04:00:52 GMT | Tue, 12 May 2026 10:00:52 GMT |
| Linux Distro | Ubuntu 24.04 LTS x64 | Ubuntu 24.04 LTS x64 |
| Kernel Version | 6.8.0-111-generic | 6.8.0-111-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 | $15.00 | $18.00 |
| RAM (GB) | 2 | 2 |
| CPU Cores | 2 | 2 |
| Storage (TB) | 65 | 60 |
| Storage Type | SSD | NVMe |
| Transfer (TB) | 3 | 4 |
CPU
| Vultr – Cloud Compute (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,792.00 | 2,900.01 |
| CPU Cache Size (KB) | 16,384.00 | 1,024.00 |
| BogoMips | 7,583.99 | 5,800.02 |
| Events per Second | 1,481.60 | 4,626.79 |
| Minimum Latency (ms) | 0.63 | 0.21 |
| Average Latency (ms) | 0.67 | 0.22 |
| Maximum Latency (ms) | 1.95 | 3.53 |
| 95th Percentile Latency (ms) | 0.77 | 0.23 |
Memory
Memory Read
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 6,401,389.08 | 7,533,354.82 |
| Mebibytes per second | 6,251.36 | 7,356.79 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.23 | 0.12 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 6,411,085.35 | 7,542,644.19 |
| Mebibytes per second | 6,260.83 | 7,365.86 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.18 | 0.6 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Reads per Second | 4,345.71 | 5,126.68 |
| Writes per Second | 2,897.07 | 3,417.78 |
| Fsyncs per Second | 9,273.19 | 10,937.41 |
| Read Mebibytes per Second | 67.90 | 80.10 |
| Written Mebibytes per Second | 45.27 | 53.40 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.06 | 0.05 |
| Maximum Latency (ms) | 2.92 | 2.38 |
| 95th Percentile Latency (ms) | 0.17 | 0.11 |
Mutex
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 214.63 | 612.54 |
| Average Latency (ms) | 569.72 | 642.87 |
| Maximum Latency (ms) | 636.55 | 659.60 |
| 95th Percentile Latency (ms) | 634.66 | 657.93 |
MySQL
MySQL Read-only
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,015.00 | 9,926.00 |
| Queries per second | 80,150.00 | 99,260.00 |
| Minimum Latency (ms) | 0.92 | 0.75 |
| Average Latency (ms) | 1.25 | 1.01 |
| Maximum Latency (ms) | 5.5 | 1.94 |
| 95th Percentile Latency (ms) | 1.86 | 1.06 |
MySQL Write-only
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,497.00 | 9,968.00 |
| Queries per second | 84,970.00 | 99,680.00 |
| Minimum Latency (ms) | 0.76 | 0.71 |
| Average Latency (ms) | 1.17 | 1 |
| Maximum Latency (ms) | 3.04 | 2.56 |
| 95th Percentile Latency (ms) | 1.55 | 1.27 |
MySQL Read/Write
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 3,726.00 | 4,907.00 |
| Queries per second | 37,260.00 | 49,070.00 |
| Minimum Latency (ms) | 1.78 | 1.59 |
| Average Latency (ms) | 2.68 | 2.04 |
| Maximum Latency (ms) | 5.82 | 12.58 |
| 95th Percentile Latency (ms) | 3.43 | 2.39 |
MySQL INSERT
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 15,028.00 | 16,597.00 |
| Queries per second | 150,280.00 | 165,970.00 |
| Minimum Latency (ms) | 0.41 | 0.44 |
| Average Latency (ms) | 0.66 | 0.6 |
| Maximum Latency (ms) | 2.42 | 2.75 |
| 95th Percentile Latency (ms) | 0.86 | 0.72 |
MySQL Bulk INSERT
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 1,696,217.00 | 3,065,092.00 |
| Queries per second | 16,962,170.00 | 30,650,920.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0 |
| Maximum Latency (ms) | 283.37 | 202.49 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 201,989.00 | 225,864.00 |
| Queries per second | 2,019,890.00 | 2,258,640.00 |
| Minimum Latency (ms) | 0.03 | 0.03 |
| Average Latency (ms) | 0.05 | 0.04 |
| Maximum Latency (ms) | 0.51 | 0.77 |
| 95th Percentile Latency (ms) | 0.07 | 0.05 |
MySQL SELECT (Random Points)
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,025.00 | 14,804.00 |
| Queries per second | 80,250.00 | 148,040.00 |
| Minimum Latency (ms) | 0.35 | 0.25 |
| Average Latency (ms) | 1.24 | 0.67 |
| Maximum Latency (ms) | 3.55 | 2.68 |
| 95th Percentile Latency (ms) | 2.07 | 0.86 |
MySQL SELECT (Random Ranges)
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,336.00 | 14,246.00 |
| Queries per second | 83,360.00 | 142,460.00 |
| Minimum Latency (ms) | 0.4 | 0.23 |
| Average Latency (ms) | 1.2 | 0.7 |
| Maximum Latency (ms) | 4.25 | 1.77 |
| 95th Percentile Latency (ms) | 2.22 | 0.9 |
MySQL UPDATE (Indexed)
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 13,858.00 | 15,609.00 |
| Queries per second | 138,580.00 | 156,090.00 |
| Minimum Latency (ms) | 0.42 | 0.46 |
| Average Latency (ms) | 0.72 | 0.64 |
| Maximum Latency (ms) | 6.33 | 1.62 |
| 95th Percentile Latency (ms) | 0.95 | 0.83 |
MySQL UPDATE (Non-Indexed)
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 14,587.00 | 16,050.00 |
| Queries per second | 145,870.00 | 160,500.00 |
| Minimum Latency (ms) | 0.4 | 0.45 |
| Average Latency (ms) | 0.68 | 0.62 |
| Maximum Latency (ms) | 11.69 | 1.98 |
| 95th Percentile Latency (ms) | 0.9 | 0.78 |
MySQL DELETE
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 129,013.00 | 163,936.00 |
| Queries per second | 1,290,130.00 | 1,639,360.00 |
| Minimum Latency (ms) | 0.03 | 0.02 |
| Average Latency (ms) | 0.08 | 0.06 |
| Maximum Latency (ms) | 2.61 | 3.58 |
| 95th Percentile Latency (ms) | 0.09 | 0.08 |
Redis
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE per Second | 78,247.26 | 56,850.48 |
| PING_MBULK per Second | 74,738.41 | 58,616.65 |
| SET per Second | 77,041.60 | 58,858.15 |
| GET per Second | 83,333.33 | 58,513.75 |
| INCR per Second | 80,971.66 | 58,038.30 |
| LPUSH per Second | 79,113.92 | 58,582.31 |
| RPUSH per Second | 77,160.49 | 57,971.02 |
| LPOP per Second | 81,499.59 | 58,719.91 |
| RPOP per Second | 82,440.23 | 58,513.75 |
| SADD per Second | 80,192.46 | 58,927.52 |
| HSET per Second | 83,612.04 | 58,962.27 |
| SPOP per Second | 85,034.02 | 58,411.21 |
| ZADD per Second | 83,263.95 | 58,651.02 |
| ZPOPMIN per Second | 82,987.55 | 58,309.04 |
| LRANGE_100 (first 100 elements) per Second | 55,555.56 | 48,685.49 |
| LRANGE_300 (first 300 elements) per Second | 28,851.70 | 33,134.53 |
| LRANGE_500 (first 500 elements) per Second | 19,391.12 | 25,322.87 |
| LRANGE_600 (first 600 elements) per Second | 17,211.71 | 22,820.63 |
| MSET (10 keys) per Second | 80,256.82 | 58,207.21 |
Redis Average Latency (ms)
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE | 0.34 | 0.46 |
| PING_MBULK | 0.35 | 0.44 |
| SET | 0.34 | 0.44 |
| GET | 0.32 | 0.44 |
| INCR | 0.32 | 0.44 |
| LPUSH | 0.34 | 0.44 |
| RPUSH | 0.34 | 0.44 |
| LPOP | 0.32 | 0.44 |
| RPOP | 0.32 | 0.44 |
| SADD | 0.32 | 0.44 |
| HSET | 0.31 | 0.44 |
| SPOP | 0.30 | 0.44 |
| ZADD | 0.31 | 0.44 |
| ZPOPMIN | 0.31 | 0.44 |
| LRANGE_100 (first 100 elements) | 0.54 | 0.53 |
| LRANGE_300 (first 300 elements) | 1.11 | 0.77 |
| LRANGE_500 (first 500 elements) | 1.62 | 1.01 |
| LRANGE_600 (first 600 elements) | 1.84 | 1.12 |
| MSET (10 keys) | 0.38 | 0.44 |
Conclusion
From the friendly robots:
When comparing the Vultr Cloud Compute (2 GB, 2 Cores) with the Vultr High Performance AMD (2 GB, 2 Cores), both instances show strong performance across various benchmarks, but they cater to different use cases. The Cloud Compute instance delivers higher Redis performance, particularly in commands like LRANGE, indicating better handling of memory-intensive tasks, which makes it a good choice for applications that heavily utilize in-memory databases. Meanwhile, the High Performance AMD instance boasts superior CPU performance in terms of raw processing speed and memory operations, suggesting it is better suited for CPU-intensive workloads such as computational tasks, high-frequency trading platforms, or any application needing high single-thread performance. For developers and sysadmins, choosing between these instances will largely depend on whether memory-based operations (Cloud Compute) or CPU-bound tasks (High Performance AMD) are more critical for their specific 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.