Vultr Cloud Compute (4 GB, 2 Cores) vs. Vultr High Performance AMD (4 GB, 2 Cores)
My friend, I'm so glad you're here! Today I've spun up brand new instance from Vultr and ran my world famous suite of benchmarking scripts. Each instance was running Ubuntu 24.04 LTS x64 and were created in or around the New York / New Jersey area. Let's get into the numbers.
Overview
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Last Benchmarked | Thu, 11 Jun 2026 09:00:52 GMT | Wed, 10 Jun 2026 20:00:52 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 | $24.00 |
| RAM (GB) | 4 | 4 |
| CPU Cores | 2 | 2 |
| Storage (TB) | 80 | 100 |
| Storage Type | SSD | NVMe |
| Transfer (TB) | 3 | 5 |
CPU
| Vultr – Cloud Compute (4 GB, 2 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.91 | 2,900.01 |
| CPU Cache Size (KB) | 16,384.00 | 1,024.00 |
| BogoMips | 5,187.81 | 5,800.01 |
| Events per Second | 1,022.39 | 4,642.06 |
| Minimum Latency (ms) | 0.88 | 0.2 |
| Average Latency (ms) | 0.98 | 0.22 |
| Maximum Latency (ms) | 1.77 | 1.11 |
| 95th Percentile Latency (ms) | 1.21 | 0.22 |
Memory
Memory Read
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 3,523,809.57 | 7,536,291.50 |
| Mebibytes per second | 3,441.22 | 7,359.66 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.22 | 0.09 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 3,568,203.77 | 7,514,898.61 |
| Mebibytes per second | 3,484.57 | 7,338.77 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 1.02 | 0.11 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Reads per Second | 2,972.63 | 7,322.40 |
| Writes per Second | 1,981.75 | 4,881.60 |
| Fsyncs per Second | 6,347.81 | 15,631.91 |
| Read Mebibytes per Second | 46.45 | 114.41 |
| Written Mebibytes per Second | 30.96 | 76.27 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.09 | 0.04 |
| Maximum Latency (ms) | 17.12 | 12.52 |
| 95th Percentile Latency (ms) | 0.33 | 0.11 |
Mutex
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 899.28 | 606.58 |
| Average Latency (ms) | 935.93 | 639.42 |
| Maximum Latency (ms) | 969.92 | 670.29 |
| 95th Percentile Latency (ms) | 977.74 | 669.89 |
MySQL
MySQL Read-only
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 3,779.00 | 9,572.00 |
| Queries per second | 37,790.00 | 95,720.00 |
| Minimum Latency (ms) | 1.84 | 0.77 |
| Average Latency (ms) | 2.64 | 1.04 |
| Maximum Latency (ms) | 24.55 | 1.97 |
| 95th Percentile Latency (ms) | 3.82 | 1.18 |
MySQL Write-only
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 4,044.00 | 9,531.00 |
| Queries per second | 40,440.00 | 95,310.00 |
| Minimum Latency (ms) | 1.4 | 0.8 |
| Average Latency (ms) | 2.47 | 1.05 |
| Maximum Latency (ms) | 13.46 | 2.22 |
| 95th Percentile Latency (ms) | 3.3 | 1.32 |
MySQL Read/Write
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 1,798.00 | 4,819.00 |
| Queries per second | 17,980.00 | 48,190.00 |
| Minimum Latency (ms) | 3.86 | 1.55 |
| Average Latency (ms) | 5.56 | 2.07 |
| Maximum Latency (ms) | 27.33 | 14.51 |
| 95th Percentile Latency (ms) | 6.91 | 2.43 |
MySQL INSERT
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 6,405.00 | 15,411.00 |
| Queries per second | 64,050.00 | 154,110.00 |
| Minimum Latency (ms) | 0.99 | 0.44 |
| Average Latency (ms) | 1.56 | 0.65 |
| Maximum Latency (ms) | 15.15 | 2.56 |
| 95th Percentile Latency (ms) | 2.03 | 0.8 |
MySQL Bulk INSERT
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 865,805.00 | 2,919,467.00 |
| Queries per second | 8,658,050.00 | 29,194,670.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0 |
| Maximum Latency (ms) | 538.25 | 207.11 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 126,618.00 | 218,761.00 |
| Queries per second | 1,266,180.00 | 2,187,610.00 |
| Minimum Latency (ms) | 0.05 | 0.02 |
| Average Latency (ms) | 0.08 | 0.05 |
| Maximum Latency (ms) | 2.46 | 9.06 |
| 95th Percentile Latency (ms) | 0.11 | 0.06 |
MySQL SELECT (Random Points)
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 3,674.00 | 14,742.00 |
| Queries per second | 36,740.00 | 147,420.00 |
| Minimum Latency (ms) | 1.07 | 0.24 |
| Average Latency (ms) | 2.72 | 0.68 |
| Maximum Latency (ms) | 6.45 | 2.4 |
| 95th Percentile Latency (ms) | 3.55 | 0.87 |
MySQL SELECT (Random Ranges)
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 2,728.00 | 14,182.00 |
| Queries per second | 27,280.00 | 141,820.00 |
| Minimum Latency (ms) | 1.3 | 0.17 |
| Average Latency (ms) | 3.66 | 0.7 |
| Maximum Latency (ms) | 11.85 | 3.2 |
| 95th Percentile Latency (ms) | 5 | 0.92 |
MySQL UPDATE (Indexed)
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 5,438.00 | 15,010.00 |
| Queries per second | 54,380.00 | 150,100.00 |
| Minimum Latency (ms) | 0.99 | 0.45 |
| Average Latency (ms) | 1.84 | 0.67 |
| Maximum Latency (ms) | 13.86 | 2.15 |
| 95th Percentile Latency (ms) | 2.71 | 0.87 |
MySQL UPDATE (Non-Indexed)
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 6,370.00 | 15,508.00 |
| Queries per second | 63,700.00 | 155,080.00 |
| Minimum Latency (ms) | 1.01 | 0.45 |
| Average Latency (ms) | 1.57 | 0.64 |
| Maximum Latency (ms) | 8.99 | 1.68 |
| 95th Percentile Latency (ms) | 2.07 | 0.83 |
MySQL DELETE
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 51,180.00 | 152,406.00 |
| Queries per second | 511,800.00 | 1,524,060.00 |
| Minimum Latency (ms) | 0.05 | 0.02 |
| Average Latency (ms) | 0.19 | 0.07 |
| Maximum Latency (ms) | 6.11 | 1.97 |
| 95th Percentile Latency (ms) | 1.39 | 0.08 |
Redis
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE per Second | 49,677.10 | 55,617.35 |
| PING_MBULK per Second | 45,372.05 | 57,175.53 |
| SET per Second | 45,392.64 | 56,915.20 |
| GET per Second | 53,163.21 | 57,736.72 |
| INCR per Second | 48,732.94 | 58,173.36 |
| LPUSH per Second | 50,327.12 | 57,937.43 |
| RPUSH per Second | 48,285.85 | 57,836.90 |
| LPOP per Second | 48,355.90 | 57,736.72 |
| RPOP per Second | 51,413.88 | 56,497.18 |
| SADD per Second | 48,332.53 | 57,937.43 |
| HSET per Second | 49,285.36 | 57,803.47 |
| SPOP per Second | 48,332.53 | 57,770.08 |
| ZADD per Second | 51,229.51 | 57,339.45 |
| ZPOPMIN per Second | 45,085.66 | 57,175.53 |
| LRANGE_100 (first 100 elements) per Second | 27,122.32 | 49,751.24 |
| LRANGE_300 (first 300 elements) per Second | 12,442.45 | 33,852.40 |
| LRANGE_500 (first 500 elements) per Second | 7,930.21 | 26,068.82 |
| LRANGE_600 (first 600 elements) per Second | 6,902.74 | 23,724.79 |
| MSET (10 keys) per Second | 45,146.73 | 58,241.12 |
Redis Average Latency (ms)
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE | 0.53 | 0.48 |
| PING_MBULK | 0.57 | 0.45 |
| SET | 0.57 | 0.45 |
| GET | 0.49 | 0.45 |
| INCR | 0.53 | 0.44 |
| LPUSH | 0.51 | 0.45 |
| RPUSH | 0.54 | 0.45 |
| LPOP | 0.54 | 0.45 |
| RPOP | 0.52 | 0.46 |
| SADD | 0.55 | 0.44 |
| HSET | 0.54 | 0.45 |
| SPOP | 0.54 | 0.45 |
| ZADD | 0.52 | 0.45 |
| ZPOPMIN | 0.57 | 0.45 |
| LRANGE_100 (first 100 elements) | 1.02 | 0.52 |
| LRANGE_300 (first 300 elements) | 2.29 | 0.75 |
| LRANGE_500 (first 500 elements) | 3.27 | 0.99 |
| LRANGE_600 (first 600 elements) | 3.91 | 1.07 |
| MSET (10 keys) | 0.78 | 0.44 |
Conclusion
From the friendly robots:
Upon analyzing the benchmark results for both instances, the Vultr Cloud Compute (4 GB, 2 Cores) instance with Intel Xeon processors shows robust performance in memory operations and MySQL workloads, maintaining low latencies and high throughputs for various database operations and memory benchmarks, although it lags slightly behind in CPU-intensive tasks. In contrast, the Vultr High Performance AMD (4 GB, 2 Cores) instance, featuring AMD EPYC-Genoa processors, excels in CPU-centric tasks with higher events per second and significantly better Redis performance metrics, though it exhibits slightly higher latencies in file I/O and MySQL operations. The AMD instance also shows superior overall throughput in memory read and write operations. Thus, the Intel-based instance is ideal for applications prioritizing low latency in memory and database operations, while the AMD-based instance would be better suited for CPU-intensive workloads and scenarios demanding high throughput in memory 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.