Vultr Cloud Compute (8 GB, 4 Cores) vs. Vultr High Performance AMD (4 GB, 2 Cores)
Same showdown, different day. Today I've spun up some brand new instance from Vultr and ran some benchmarks. Each instance was running Ubuntu 24.04 LTS x64 and all resided in or around the New York / New Jersey area. Time to see who showed up today.
Overview
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Last Benchmarked | Sat, 23 May 2026 11:00:52 GMT | Sat, 23 May 2026 05: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 | $40.00 | $24.00 |
| RAM (GB) | 8 | 4 |
| CPU Cores | 4 | 2 |
| Storage (TB) | 160 | 100 |
| Storage Type | SSD | NVMe |
| Transfer (TB) | 4 | 5 |
CPU
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Vendor | GenuineIntel | AuthenticAMD |
| Model Name | Intel Xeon Processor (Skylake, IBRS) | AMD EPYC-Genoa Processor |
| Clock Speed (MHz) | 2,593.90 | 2,900.00 |
| CPU Cache Size (KB) | 16,384.00 | 1,024.00 |
| BogoMips | 5,187.80 | 5,799.99 |
| Events per Second | 1,100.82 | 4,640.31 |
| Minimum Latency (ms) | 0.88 | 0.21 |
| Average Latency (ms) | 0.91 | 0.22 |
| Maximum Latency (ms) | 1.56 | 0.74 |
| 95th Percentile Latency (ms) | 0.97 | 0.22 |
Memory
Memory Read
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 3,685,781.23 | 7,508,399.45 |
| Mebibytes per second | 3,599.40 | 7,332.42 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 1.03 | 0.08 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 3,590,629.63 | 7,495,389.97 |
| Mebibytes per second | 3,506.47 | 7,319.72 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 1.16 | 0.8 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Reads per Second | 4,999.39 | 8,276.59 |
| Writes per Second | 3,332.93 | 5,517.73 |
| Fsyncs per Second | 10,670.47 | 17,667.60 |
| Read Mebibytes per Second | 78.12 | 129.32 |
| Written Mebibytes per Second | 52.08 | 86.21 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.05 | 0.03 |
| Maximum Latency (ms) | 37.52 | 1.78 |
| 95th Percentile Latency (ms) | 0.18 | 0.1 |
Mutex
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 369.37 | 639.03 |
| Average Latency (ms) | 416.22 | 656.06 |
| Maximum Latency (ms) | 441.77 | 672.70 |
| 95th Percentile Latency (ms) | 442.73 | 669.89 |
MySQL
MySQL Read-only
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 5,144.00 | 9,771.00 |
| Queries per second | 51,440.00 | 97,710.00 |
| Minimum Latency (ms) | 1.72 | 0.75 |
| Average Latency (ms) | 1.94 | 1.02 |
| Maximum Latency (ms) | 7.67 | 2.24 |
| 95th Percentile Latency (ms) | 2.35 | 1.14 |
MySQL Write-only
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 5,108.00 | 9,405.00 |
| Queries per second | 51,080.00 | 94,050.00 |
| Minimum Latency (ms) | 1.15 | 0.71 |
| Average Latency (ms) | 1.96 | 1.06 |
| Maximum Latency (ms) | 12.52 | 2.87 |
| 95th Percentile Latency (ms) | 2.71 | 1.39 |
MySQL Read/Write
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 2,247.00 | 4,988.00 |
| Queries per second | 22,470.00 | 49,880.00 |
| Minimum Latency (ms) | 3.08 | 1.54 |
| Average Latency (ms) | 4.45 | 2 |
| Maximum Latency (ms) | 29.7 | 4.34 |
| 95th Percentile Latency (ms) | 5.28 | 2.39 |
MySQL INSERT
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 7,630.00 | 15,596.00 |
| Queries per second | 76,300.00 | 155,960.00 |
| Minimum Latency (ms) | 0.71 | 0.46 |
| Average Latency (ms) | 1.31 | 0.64 |
| Maximum Latency (ms) | 29.81 | 2.32 |
| 95th Percentile Latency (ms) | 1.55 | 0.77 |
MySQL Bulk INSERT
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 898,571.00 | 2,919,467.00 |
| Queries per second | 8,985,710.00 | 29,194,670.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0 |
| Maximum Latency (ms) | 505.86 | 211.2 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 149,465.00 | 221,871.00 |
| Queries per second | 1,494,650.00 | 2,218,710.00 |
| Minimum Latency (ms) | 0.05 | 0.03 |
| Average Latency (ms) | 0.07 | 0.04 |
| Maximum Latency (ms) | 1.22 | 0.73 |
| 95th Percentile Latency (ms) | 0.09 | 0.06 |
MySQL SELECT (Random Points)
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 4,249.00 | 14,725.00 |
| Queries per second | 42,490.00 | 147,250.00 |
| Minimum Latency (ms) | 0.83 | 0.23 |
| Average Latency (ms) | 2.35 | 0.68 |
| Maximum Latency (ms) | 6.6 | 2.12 |
| 95th Percentile Latency (ms) | 3.02 | 0.87 |
MySQL SELECT (Random Ranges)
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 2,637.00 | 14,389.00 |
| Queries per second | 26,370.00 | 143,890.00 |
| Minimum Latency (ms) | 0.94 | 0.26 |
| Average Latency (ms) | 3.79 | 0.69 |
| Maximum Latency (ms) | 6.3 | 1.62 |
| 95th Percentile Latency (ms) | 5.09 | 0.9 |
MySQL UPDATE (Indexed)
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 7,166.00 | 14,769.00 |
| Queries per second | 71,660.00 | 147,690.00 |
| Minimum Latency (ms) | 0.7 | 0.44 |
| Average Latency (ms) | 1.39 | 0.68 |
| Maximum Latency (ms) | 28.84 | 2.16 |
| 95th Percentile Latency (ms) | 1.79 | 0.9 |
MySQL UPDATE (Non-Indexed)
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 7,661.00 | 15,277.00 |
| Queries per second | 76,610.00 | 152,770.00 |
| Minimum Latency (ms) | 0.7 | 0.43 |
| Average Latency (ms) | 1.3 | 0.65 |
| Maximum Latency (ms) | 33.97 | 1.93 |
| 95th Percentile Latency (ms) | 1.58 | 0.84 |
MySQL DELETE
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 69,690.00 | 148,783.00 |
| Queries per second | 696,900.00 | 1,487,830.00 |
| Minimum Latency (ms) | 0.05 | 0.02 |
| Average Latency (ms) | 0.14 | 0.07 |
| Maximum Latency (ms) | 27.73 | 1.99 |
| 95th Percentile Latency (ms) | 0.87 | 0.09 |
Redis
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE per Second | 54,436.58 | 64,350.06 |
| PING_MBULK per Second | 48,828.12 | 57,836.90 |
| SET per Second | 51,572.98 | 58,207.21 |
| GET per Second | 48,239.27 | 58,548.01 |
| INCR per Second | 52,328.62 | 58,788.95 |
| LPUSH per Second | 45,454.54 | 58,685.45 |
| RPUSH per Second | 49,751.24 | 59,031.88 |
| LPOP per Second | 53,390.28 | 58,823.53 |
| RPOP per Second | 53,648.07 | 60,168.47 |
| SADD per Second | 48,285.85 | 60,277.27 |
| HSET per Second | 51,493.30 | 64,102.57 |
| SPOP per Second | 52,910.05 | 57,937.43 |
| ZADD per Second | 53,504.55 | 57,903.88 |
| ZPOPMIN per Second | 53,590.57 | 57,903.88 |
| LRANGE_100 (first 100 elements) per Second | 28,645.09 | 48,899.75 |
| LRANGE_300 (first 300 elements) per Second | 13,131.98 | 34,317.09 |
| LRANGE_500 (first 500 elements) per Second | 8,529.51 | 26,295.03 |
| LRANGE_600 (first 600 elements) per Second | 7,479.99 | 24,195.50 |
| MSET (10 keys) per Second | 49,212.60 | 58,754.41 |
Redis Average Latency (ms)
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE | 0.47 | 0.41 |
| PING_MBULK | 0.53 | 0.45 |
| SET | 0.50 | 0.44 |
| GET | 0.54 | 0.44 |
| INCR | 0.49 | 0.44 |
| LPUSH | 0.58 | 0.44 |
| RPUSH | 0.52 | 0.44 |
| LPOP | 0.49 | 0.44 |
| RPOP | 0.48 | 0.43 |
| SADD | 0.54 | 0.43 |
| HSET | 0.53 | 0.40 |
| SPOP | 0.49 | 0.45 |
| ZADD | 0.48 | 0.44 |
| ZPOPMIN | 0.48 | 0.45 |
| LRANGE_100 (first 100 elements) | 0.91 | 0.54 |
| LRANGE_300 (first 300 elements) | 1.94 | 0.76 |
| LRANGE_500 (first 500 elements) | 3.00 | 0.97 |
| LRANGE_600 (first 600 elements) | 3.43 | 1.05 |
| MSET (10 keys) | 0.77 | 0.44 |
Conclusion
From the friendly robots:
Upon examining the benchmark results for both Vultr instances, it's evident that the Cloud Compute (8 GB, 4 Cores) excels in CPU-intensive tasks with high Redis and MySQL performance, suggesting it's ideal for applications requiring substantial computation power and memory, such as web servers, database servers, and high-load applications. The High Performance AMD (4 GB, 2 Cores), despite having fewer cores and less RAM, boasts superior Redis throughput and lower latency in file I/O operations, making it suitable for scenarios where the workload benefits from efficient memory usage and fast NVMe storage, such as caching services and applications that rely on quick data access. Both instances provide robust performance tailored to different needs, with the 8 GB, 4 Cores instance being more powerful and versatile for broader applications, while the 4 GB, 2 Cores instance offers optimized performance for memory-sensitive 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.