Vultr Cloud Compute (8 GB, 4 Cores) vs. Vultr High Performance AMD (2 GB, 2 Cores)
Fresh benchmarks coming at ya. Today I've spun up some brand new instance from Vultr to run some benchmarks on. Each instance was spun up with Ubuntu 24.04 LTS x64 and were created 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 (2 GB, 2 Cores) | |
|---|---|---|
| Last Benchmarked | Sat, 23 May 2026 11:00:52 GMT | Thu, 21 May 2026 16:00:53 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 | $18.00 |
| RAM (GB) | 8 | 2 |
| CPU Cores | 4 | 2 |
| Storage (TB) | 160 | 60 |
| Storage Type | SSD | NVMe |
| Transfer (TB) | 4 | 4 |
CPU
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (2 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.01 |
| CPU Cache Size (KB) | 16,384.00 | 1,024.00 |
| BogoMips | 5,187.80 | 5,800.02 |
| Events per Second | 1,100.82 | 4,648.80 |
| Minimum Latency (ms) | 0.88 | 0.2 |
| Average Latency (ms) | 0.91 | 0.21 |
| Maximum Latency (ms) | 1.56 | 3.31 |
| 95th Percentile Latency (ms) | 0.97 | 0.23 |
Memory
Memory Read
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 3,685,781.23 | 7,514,331.55 |
| Mebibytes per second | 3,599.40 | 7,338.21 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 1.03 | 0.09 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 3,590,629.63 | 7,550,541.56 |
| Mebibytes per second | 3,506.47 | 7,373.58 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 1.16 | 0.12 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Reads per Second | 4,999.39 | 5,283.64 |
| Writes per Second | 3,332.93 | 3,522.42 |
| Fsyncs per Second | 10,670.47 | 11,283.45 |
| Read Mebibytes per Second | 78.12 | 82.56 |
| Written Mebibytes per Second | 52.08 | 55.04 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.05 | 0.05 |
| Maximum Latency (ms) | 37.52 | 2.12 |
| 95th Percentile Latency (ms) | 0.18 | 0.11 |
Mutex
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 369.37 | 643.06 |
| Average Latency (ms) | 416.22 | 654.65 |
| Maximum Latency (ms) | 441.77 | 666.20 |
| 95th Percentile Latency (ms) | 442.73 | 669.89 |
MySQL
MySQL Read-only
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 5,144.00 | 9,906.00 |
| Queries per second | 51,440.00 | 99,060.00 |
| Minimum Latency (ms) | 1.72 | 0.76 |
| Average Latency (ms) | 1.94 | 1.01 |
| Maximum Latency (ms) | 7.67 | 2.02 |
| 95th Percentile Latency (ms) | 2.35 | 1.08 |
MySQL Write-only
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 5,108.00 | 9,889.00 |
| Queries per second | 51,080.00 | 98,890.00 |
| Minimum Latency (ms) | 1.15 | 0.76 |
| Average Latency (ms) | 1.96 | 1.01 |
| Maximum Latency (ms) | 12.52 | 3.21 |
| 95th Percentile Latency (ms) | 2.71 | 1.3 |
MySQL Read/Write
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 2,247.00 | 4,953.00 |
| Queries per second | 22,470.00 | 49,530.00 |
| Minimum Latency (ms) | 3.08 | 1.48 |
| Average Latency (ms) | 4.45 | 2.02 |
| Maximum Latency (ms) | 29.7 | 4.9 |
| 95th Percentile Latency (ms) | 5.28 | 2.39 |
MySQL INSERT
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 7,630.00 | 16,430.00 |
| Queries per second | 76,300.00 | 164,300.00 |
| Minimum Latency (ms) | 0.71 | 0.44 |
| Average Latency (ms) | 1.31 | 0.61 |
| Maximum Latency (ms) | 29.81 | 2.32 |
| 95th Percentile Latency (ms) | 1.55 | 0.74 |
MySQL Bulk INSERT
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 898,571.00 | 3,035,967.00 |
| Queries per second | 8,985,710.00 | 30,359,670.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0 |
| Maximum Latency (ms) | 505.86 | 203.7 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 149,465.00 | 226,685.00 |
| Queries per second | 1,494,650.00 | 2,266,850.00 |
| Minimum Latency (ms) | 0.05 | 0.02 |
| Average Latency (ms) | 0.07 | 0.04 |
| Maximum Latency (ms) | 1.22 | 0.8 |
| 95th Percentile Latency (ms) | 0.09 | 0.05 |
MySQL SELECT (Random Points)
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 4,249.00 | 15,126.00 |
| Queries per second | 42,490.00 | 151,260.00 |
| Minimum Latency (ms) | 0.83 | 0.26 |
| Average Latency (ms) | 2.35 | 0.66 |
| Maximum Latency (ms) | 6.6 | 2.14 |
| 95th Percentile Latency (ms) | 3.02 | 0.83 |
MySQL SELECT (Random Ranges)
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 2,637.00 | 14,121.00 |
| Queries per second | 26,370.00 | 141,210.00 |
| Minimum Latency (ms) | 0.94 | 0.19 |
| Average Latency (ms) | 3.79 | 0.71 |
| Maximum Latency (ms) | 6.3 | 1.75 |
| 95th Percentile Latency (ms) | 5.09 | 0.9 |
MySQL UPDATE (Indexed)
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 7,166.00 | 15,302.00 |
| Queries per second | 71,660.00 | 153,020.00 |
| Minimum Latency (ms) | 0.7 | 0.46 |
| Average Latency (ms) | 1.39 | 0.65 |
| Maximum Latency (ms) | 28.84 | 3.28 |
| 95th Percentile Latency (ms) | 1.79 | 0.86 |
MySQL UPDATE (Non-Indexed)
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 7,661.00 | 16,239.00 |
| Queries per second | 76,610.00 | 162,390.00 |
| Minimum Latency (ms) | 0.7 | 0.43 |
| Average Latency (ms) | 1.3 | 0.62 |
| Maximum Latency (ms) | 33.97 | 1.82 |
| 95th Percentile Latency (ms) | 1.58 | 0.78 |
MySQL DELETE
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 69,690.00 | 155,529.00 |
| Queries per second | 696,900.00 | 1,555,290.00 |
| Minimum Latency (ms) | 0.05 | 0.02 |
| Average Latency (ms) | 0.14 | 0.06 |
| Maximum Latency (ms) | 27.73 | 2.23 |
| 95th Percentile Latency (ms) | 0.87 | 0.08 |
Redis
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE per Second | 54,436.58 | 56,497.18 |
| PING_MBULK per Second | 48,828.12 | 58,207.21 |
| SET per Second | 51,572.98 | 58,139.54 |
| GET per Second | 48,239.27 | 57,372.34 |
| INCR per Second | 52,328.62 | 58,377.11 |
| LPUSH per Second | 45,454.54 | 59,276.82 |
| RPUSH per Second | 49,751.24 | 60,386.47 |
| LPOP per Second | 53,390.28 | 59,241.71 |
| RPOP per Second | 53,648.07 | 58,377.11 |
| SADD per Second | 48,285.85 | 59,844.41 |
| HSET per Second | 51,493.30 | 59,665.87 |
| SPOP per Second | 52,910.05 | 59,453.03 |
| ZADD per Second | 53,504.55 | 60,975.61 |
| ZPOPMIN per Second | 53,590.57 | 60,532.69 |
| LRANGE_100 (first 100 elements) per Second | 28,645.09 | 49,091.80 |
| LRANGE_300 (first 300 elements) per Second | 13,131.98 | 33,967.39 |
| LRANGE_500 (first 500 elements) per Second | 8,529.51 | 26,288.12 |
| LRANGE_600 (first 600 elements) per Second | 7,479.99 | 24,336.82 |
| MSET (10 keys) per Second | 49,212.60 | 58,377.11 |
Redis Average Latency (ms)
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (2 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE | 0.47 | 0.46 |
| PING_MBULK | 0.53 | 0.44 |
| SET | 0.50 | 0.44 |
| GET | 0.54 | 0.45 |
| INCR | 0.49 | 0.44 |
| LPUSH | 0.58 | 0.43 |
| RPUSH | 0.52 | 0.43 |
| LPOP | 0.49 | 0.43 |
| RPOP | 0.48 | 0.44 |
| SADD | 0.54 | 0.43 |
| HSET | 0.53 | 0.43 |
| SPOP | 0.49 | 0.43 |
| ZADD | 0.48 | 0.42 |
| ZPOPMIN | 0.48 | 0.43 |
| LRANGE_100 (first 100 elements) | 0.91 | 0.52 |
| LRANGE_300 (first 300 elements) | 1.94 | 0.75 |
| 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:
In benchmarking performance, the Vultr Cloud Compute instance with 8 GB RAM and 4 cores outmatches the High Performance AMD instance with 2 GB RAM and 2 cores in CPU-intensive tasks, as evidenced by higher Redis operations per second (rps) and lower latency across a variety of commands, as well as more robust MySQL and file I/O capabilities. However, the AMD instance excels in memory throughput and read/write operations per second, suggesting it's better suited for workloads that benefit from high memory bandwidth and quick file I/O operations. Consequently, the 8 GB, 4-core instance is ideal for CPU-intensive, memory-demanding applications, while the 2 GB, 2-core AMD instance is better for applications that prioritize high memory throughput and efficient file operations.
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.