Vultr Cloud Compute (4 GB, 2 Cores) vs. Vultr High Performance AMD (8 GB, 4 Cores)
Welcome to another round of the VPS Showdown. Today I've spun up brand new instance from Vultr and did some benchmarking. All instances were spun up with 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 (4 GB, 2 Cores) | Vultr – High Performance AMD (8 GB, 4 Cores) | |
|---|---|---|
| Last Benchmarked | Thu, 11 Jun 2026 09:00:52 GMT | Fri, 12 Jun 2026 06:00:51 GMT |
| Linux Distro | Ubuntu 24.04 LTS x64 | Ubuntu 24.04 LTS x64 |
| Kernel Version | 6.8.0-124-generic | 6.8.0-124-generic |
| MySQL Version | 8.0.46-0ubuntu0.24.04.2 | 8.0.46-0ubuntu0.24.04.2 |
| Redis Version | 7.0.15 | 7.0.15 |
| Location | Newark, NJ | Newark, NJ |
| Monthly Price | $20.00 | $48.00 |
| RAM (GB) | 4 | 8 |
| CPU Cores | 2 | 4 |
| Storage (TB) | 80 | 180 |
| Storage Type | SSD | NVMe |
| Transfer (TB) | 3 | 6 |
CPU
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (8 GB, 4 Cores) | |
|---|---|---|
| Vendor | GenuineIntel | AuthenticAMD |
| Model Name | Intel Xeon Processor (Skylake, IBRS) | AMD EPYC-Milan Processor |
| Clock Speed (MHz) | 2,593.91 | 3,250.04 |
| CPU Cache Size (KB) | 16,384.00 | 512.00 |
| BogoMips | 5,187.81 | 6,500.07 |
| Events per Second | 1,022.39 | 4,087.32 |
| Minimum Latency (ms) | 0.88 | 0.22 |
| Average Latency (ms) | 0.98 | 0.24 |
| Maximum Latency (ms) | 1.77 | 4.73 |
| 95th Percentile Latency (ms) | 1.21 | 0.26 |
Memory
Memory Read
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (8 GB, 4 Cores) | |
|---|---|---|
| Operations per second | 3,523,809.57 | 6,258,703.19 |
| Mebibytes per second | 3,441.22 | 6,112.01 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.22 | 7.07 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (8 GB, 4 Cores) | |
|---|---|---|
| Operations per second | 3,568,203.77 | 6,237,153.32 |
| Mebibytes per second | 3,484.57 | 6,090.97 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 1.02 | 0.97 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (8 GB, 4 Cores) | |
|---|---|---|
| Reads per Second | 2,972.63 | 6,174.73 |
| Writes per Second | 1,981.75 | 4,116.49 |
| Fsyncs per Second | 6,347.81 | 13,174.66 |
| Read Mebibytes per Second | 46.45 | 96.48 |
| Written Mebibytes per Second | 30.96 | 64.32 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.09 | 0.04 |
| Maximum Latency (ms) | 17.12 | 5.9 |
| 95th Percentile Latency (ms) | 0.33 | 0.14 |
Mutex
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (8 GB, 4 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 899.28 | 218.37 |
| Average Latency (ms) | 935.93 | 405.98 |
| Maximum Latency (ms) | 969.92 | 476.60 |
| 95th Percentile Latency (ms) | 977.74 | 475.79 |
MySQL
MySQL Read-only
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 3,779.00 | 7,175.00 |
| Queries per second | 37,790.00 | 71,750.00 |
| Minimum Latency (ms) | 1.84 | 0.86 |
| Average Latency (ms) | 2.64 | 1.39 |
| Maximum Latency (ms) | 24.55 | 21.2 |
| 95th Percentile Latency (ms) | 3.82 | 1.86 |
MySQL Write-only
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 4,044.00 | 5,697.00 |
| Queries per second | 40,440.00 | 56,970.00 |
| Minimum Latency (ms) | 1.4 | 0.95 |
| Average Latency (ms) | 2.47 | 1.75 |
| Maximum Latency (ms) | 13.46 | 16.25 |
| 95th Percentile Latency (ms) | 3.3 | 2.86 |
MySQL Read/Write
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 1,798.00 | 2,788.00 |
| Queries per second | 17,980.00 | 27,880.00 |
| Minimum Latency (ms) | 3.86 | 1.99 |
| Average Latency (ms) | 5.56 | 3.59 |
| Maximum Latency (ms) | 27.33 | 18.46 |
| 95th Percentile Latency (ms) | 6.91 | 6.21 |
MySQL INSERT
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 6,405.00 | 8,093.00 |
| Queries per second | 64,050.00 | 80,930.00 |
| Minimum Latency (ms) | 0.99 | 0.55 |
| Average Latency (ms) | 1.56 | 1.23 |
| Maximum Latency (ms) | 15.15 | 11.2 |
| 95th Percentile Latency (ms) | 2.03 | 1.89 |
MySQL Bulk INSERT
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 865,805.00 | 2,074,842.00 |
| Queries per second | 8,658,050.00 | 20,748,420.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0 |
| Maximum Latency (ms) | 538.25 | 265.89 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 126,618.00 | 168,615.00 |
| Queries per second | 1,266,180.00 | 1,686,150.00 |
| Minimum Latency (ms) | 0.05 | 0.02 |
| Average Latency (ms) | 0.08 | 0.06 |
| Maximum Latency (ms) | 2.46 | 6.55 |
| 95th Percentile Latency (ms) | 0.11 | 0.09 |
MySQL SELECT (Random Points)
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 3,674.00 | 10,060.00 |
| Queries per second | 36,740.00 | 100,600.00 |
| Minimum Latency (ms) | 1.07 | 0.28 |
| Average Latency (ms) | 2.72 | 0.99 |
| Maximum Latency (ms) | 6.45 | 11.29 |
| 95th Percentile Latency (ms) | 3.55 | 1.47 |
MySQL SELECT (Random Ranges)
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 2,728.00 | 9,265.00 |
| Queries per second | 27,280.00 | 92,650.00 |
| Minimum Latency (ms) | 1.3 | 0.31 |
| Average Latency (ms) | 3.66 | 1.08 |
| Maximum Latency (ms) | 11.85 | 14.49 |
| 95th Percentile Latency (ms) | 5 | 1.61 |
MySQL UPDATE (Indexed)
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 5,438.00 | 7,519.00 |
| Queries per second | 54,380.00 | 75,190.00 |
| Minimum Latency (ms) | 0.99 | 0.56 |
| Average Latency (ms) | 1.84 | 1.33 |
| Maximum Latency (ms) | 13.86 | 17.25 |
| 95th Percentile Latency (ms) | 2.71 | 2.14 |
MySQL UPDATE (Non-Indexed)
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 6,370.00 | 8,217.00 |
| Queries per second | 63,700.00 | 82,170.00 |
| Minimum Latency (ms) | 1.01 | 0.59 |
| Average Latency (ms) | 1.57 | 1.22 |
| Maximum Latency (ms) | 8.99 | 16.82 |
| 95th Percentile Latency (ms) | 2.07 | 1.93 |
MySQL DELETE
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 51,180.00 | 94,972.00 |
| Queries per second | 511,800.00 | 949,720.00 |
| Minimum Latency (ms) | 0.05 | 0.03 |
| Average Latency (ms) | 0.19 | 0.1 |
| Maximum Latency (ms) | 6.11 | 9.88 |
| 95th Percentile Latency (ms) | 1.39 | 0.18 |
Redis
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (8 GB, 4 Cores) | |
|---|---|---|
| PING_INLINE per Second | 49,677.10 | 53,361.79 |
| PING_MBULK per Second | 45,372.05 | 54,674.69 |
| SET per Second | 45,392.64 | 57,836.90 |
| GET per Second | 53,163.21 | 57,803.47 |
| INCR per Second | 48,732.94 | 58,892.82 |
| LPUSH per Second | 50,327.12 | 55,959.71 |
| RPUSH per Second | 48,285.85 | 56,882.82 |
| LPOP per Second | 48,355.90 | 61,919.50 |
| RPOP per Second | 51,413.88 | 55,432.37 |
| SADD per Second | 48,332.53 | 60,386.47 |
| HSET per Second | 49,285.36 | 55,370.98 |
| SPOP per Second | 48,332.53 | 58,377.11 |
| ZADD per Second | 51,229.51 | 54,764.51 |
| ZPOPMIN per Second | 45,085.66 | 60,096.15 |
| LRANGE_100 (first 100 elements) per Second | 27,122.32 | 48,169.56 |
| LRANGE_300 (first 300 elements) per Second | 12,442.45 | 28,074.12 |
| LRANGE_500 (first 500 elements) per Second | 7,930.21 | 20,533.88 |
| LRANGE_600 (first 600 elements) per Second | 6,902.74 | 20,044.10 |
| MSET (10 keys) per Second | 45,146.73 | 60,204.70 |
Redis Average Latency (ms)
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (8 GB, 4 Cores) | |
|---|---|---|
| PING_INLINE | 0.53 | 0.52 |
| PING_MBULK | 0.57 | 0.50 |
| SET | 0.57 | 0.46 |
| GET | 0.49 | 0.46 |
| INCR | 0.53 | 0.45 |
| LPUSH | 0.51 | 0.48 |
| RPUSH | 0.54 | 0.46 |
| LPOP | 0.54 | 0.42 |
| RPOP | 0.52 | 0.48 |
| SADD | 0.55 | 0.44 |
| HSET | 0.54 | 0.48 |
| SPOP | 0.54 | 0.45 |
| ZADD | 0.52 | 0.48 |
| ZPOPMIN | 0.57 | 0.44 |
| LRANGE_100 (first 100 elements) | 1.02 | 0.59 |
| LRANGE_300 (first 300 elements) | 2.29 | 0.98 |
| LRANGE_500 (first 500 elements) | 3.27 | 1.47 |
| LRANGE_600 (first 600 elements) | 3.91 | 1.39 |
| MSET (10 keys) | 0.78 | 0.45 |
Conclusion
From the friendly robots:
The Vultr High Performance AMD instance outperforms the Cloud Compute instance in almost every metric, reflecting the higher computational power and memory of the former. The AMD EPYC-Milan processor provides better performance in Redis benchmarks, with higher requests per second and lower latency, and similar results for CPU, file I/O, and memory operations. The High Performance AMD instance also excels in MySQL benchmarks, showing lower latencies across operations and more efficient thread management. It's ideal for CPU-intensive and I/O-heavy workloads, whereas the Cloud Compute instance, with its lower cost and adequate performance for less demanding tasks, is suitable for applications that don't require the higher specs of the AMD server.
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.