Vultr Cloud Compute (4 GB, 2 Cores) vs. Vultr High Performance AMD (1 GB)
Same showdown, different day. 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 the New York area (or close to it). Enough talk. Here's the data.
Overview
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Last Benchmarked | Thu, 11 Jun 2026 09:00:52 GMT | Wed, 10 Jun 2026 23: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 | $6.00 |
| RAM (GB) | 4 | 1 |
| CPU Cores | 2 | 1 |
| Storage (TB) | 80 | 25 |
| Storage Type | SSD | NVMe |
| Transfer (TB) | 3 | 2 |
CPU
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Vendor | GenuineIntel | AuthenticAMD |
| Model Name | Intel Xeon Processor (Skylake, IBRS) | AMD EPYC-Milan Processor |
| Clock Speed (MHz) | 2,593.91 | 2,900.00 |
| CPU Cache Size (KB) | 16,384.00 | 512.00 |
| BogoMips | 5,187.81 | 5,799.99 |
| Events per Second | 1,022.39 | 4,583.32 |
| Minimum Latency (ms) | 0.88 | 0.2 |
| Average Latency (ms) | 0.98 | 0.22 |
| Maximum Latency (ms) | 1.77 | 3.24 |
| 95th Percentile Latency (ms) | 1.21 | 0.23 |
Memory
Memory Read
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Operations per second | 3,523,809.57 | 7,399,820.46 |
| Mebibytes per second | 3,441.22 | 7,226.39 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.22 | 0.52 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Operations per second | 3,568,203.77 | 7,440,595.74 |
| Mebibytes per second | 3,484.57 | 7,266.21 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 1.02 | 0.28 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Reads per Second | 2,972.63 | 4,569.62 |
| Writes per Second | 1,981.75 | 3,046.42 |
| Fsyncs per Second | 6,347.81 | 9,757.62 |
| Read Mebibytes per Second | 46.45 | 71.40 |
| Written Mebibytes per Second | 30.96 | 47.60 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.09 | 0.06 |
| Maximum Latency (ms) | 17.12 | 3.92 |
| 95th Percentile Latency (ms) | 0.33 | 0.13 |
Mutex
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Minimum Latency (ms) | 899.28 | 1,262.92 |
| Average Latency (ms) | 935.93 | 1,273.51 |
| Maximum Latency (ms) | 969.92 | 1,282.16 |
| 95th Percentile Latency (ms) | 977.74 | 1,280.93 |
MySQL
MySQL Read-only
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Transactions per second | 3,779.00 | 12,555.00 |
| Queries per second | 37,790.00 | 125,550.00 |
| Minimum Latency (ms) | 1.84 | 0.71 |
| Average Latency (ms) | 2.64 | 0.8 |
| Maximum Latency (ms) | 24.55 | 6.39 |
| 95th Percentile Latency (ms) | 3.82 | 0.87 |
MySQL Write-only
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Transactions per second | 4,044.00 | 9,796.00 |
| Queries per second | 40,440.00 | 97,960.00 |
| Minimum Latency (ms) | 1.4 | 0.68 |
| Average Latency (ms) | 2.47 | 1.02 |
| Maximum Latency (ms) | 13.46 | 3.22 |
| 95th Percentile Latency (ms) | 3.3 | 1.42 |
MySQL Read/Write
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Transactions per second | 1,798.00 | 4,827.00 |
| Queries per second | 17,980.00 | 48,270.00 |
| Minimum Latency (ms) | 3.86 | 1.6 |
| Average Latency (ms) | 5.56 | 2.07 |
| Maximum Latency (ms) | 27.33 | 13.49 |
| 95th Percentile Latency (ms) | 6.91 | 2.61 |
MySQL INSERT
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Transactions per second | 6,405.00 | 16,851.00 |
| Queries per second | 64,050.00 | 168,510.00 |
| Minimum Latency (ms) | 0.99 | 0.42 |
| Average Latency (ms) | 1.56 | 0.59 |
| Maximum Latency (ms) | 15.15 | 2.61 |
| 95th Percentile Latency (ms) | 2.03 | 0.73 |
MySQL Bulk INSERT
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Transactions per second | 865,805.00 | 2,191,342.00 |
| Queries per second | 8,658,050.00 | 21,913,420.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0 |
| Maximum Latency (ms) | 538.25 | 255.22 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Transactions per second | 126,618.00 | 331,398.00 |
| Queries per second | 1,266,180.00 | 3,313,980.00 |
| Minimum Latency (ms) | 0.05 | 0.02 |
| Average Latency (ms) | 0.08 | 0.03 |
| Maximum Latency (ms) | 2.46 | 2.51 |
| 95th Percentile Latency (ms) | 0.11 | 0.04 |
MySQL SELECT (Random Points)
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Transactions per second | 3,674.00 | 14,223.00 |
| Queries per second | 36,740.00 | 142,230.00 |
| Minimum Latency (ms) | 1.07 | 0.24 |
| Average Latency (ms) | 2.72 | 0.7 |
| Maximum Latency (ms) | 6.45 | 125.45 |
| 95th Percentile Latency (ms) | 3.55 | 0.9 |
MySQL SELECT (Random Ranges)
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Transactions per second | 2,728.00 | 14,211.00 |
| Queries per second | 27,280.00 | 142,110.00 |
| Minimum Latency (ms) | 1.3 | 0.23 |
| Average Latency (ms) | 3.66 | 0.7 |
| Maximum Latency (ms) | 11.85 | 1.88 |
| 95th Percentile Latency (ms) | 5 | 0.9 |
MySQL UPDATE (Indexed)
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Transactions per second | 5,438.00 | 14,865.00 |
| Queries per second | 54,380.00 | 148,650.00 |
| Minimum Latency (ms) | 0.99 | 0.45 |
| Average Latency (ms) | 1.84 | 0.67 |
| Maximum Latency (ms) | 13.86 | 2.92 |
| 95th Percentile Latency (ms) | 2.71 | 1.01 |
MySQL UPDATE (Non-Indexed)
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Transactions per second | 6,370.00 | 15,337.00 |
| Queries per second | 63,700.00 | 153,370.00 |
| Minimum Latency (ms) | 1.01 | 0.45 |
| Average Latency (ms) | 1.57 | 0.65 |
| Maximum Latency (ms) | 8.99 | 5.99 |
| 95th Percentile Latency (ms) | 2.07 | 0.92 |
MySQL DELETE
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Transactions per second | 51,180.00 | 195,634.00 |
| Queries per second | 511,800.00 | 1,956,340.00 |
| Minimum Latency (ms) | 0.05 | 0.02 |
| Average Latency (ms) | 0.19 | 0.05 |
| Maximum Latency (ms) | 6.11 | 2.37 |
| 95th Percentile Latency (ms) | 1.39 | 0.08 |
Redis
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| PING_INLINE per Second | 49,677.10 | 40,048.06 |
| PING_MBULK per Second | 45,372.05 | 42,283.30 |
| SET per Second | 45,392.64 | 41,407.87 |
| GET per Second | 53,163.21 | 40,833.00 |
| INCR per Second | 48,732.94 | 40,783.04 |
| LPUSH per Second | 50,327.12 | 41,649.31 |
| RPUSH per Second | 48,285.85 | 41,631.97 |
| LPOP per Second | 48,355.90 | 40,420.37 |
| RPOP per Second | 51,413.88 | 41,017.23 |
| SADD per Second | 48,332.53 | 41,893.59 |
| HSET per Second | 49,285.36 | 41,806.02 |
| SPOP per Second | 48,332.53 | 42,247.57 |
| ZADD per Second | 51,229.51 | 41,101.52 |
| ZPOPMIN per Second | 45,085.66 | 41,034.06 |
| LRANGE_100 (first 100 elements) per Second | 27,122.32 | 32,552.08 |
| LRANGE_300 (first 300 elements) per Second | 12,442.45 | 20,951.19 |
| LRANGE_500 (first 500 elements) per Second | 7,930.21 | 15,537.60 |
| LRANGE_600 (first 600 elements) per Second | 6,902.74 | 14,064.70 |
| MSET (10 keys) per Second | 45,146.73 | 39,761.43 |
Redis Average Latency (ms)
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| PING_INLINE | 0.53 | 0.82 |
| PING_MBULK | 0.57 | 0.79 |
| SET | 0.57 | 0.80 |
| GET | 0.49 | 0.81 |
| INCR | 0.53 | 0.81 |
| LPUSH | 0.51 | 0.81 |
| RPUSH | 0.54 | 0.80 |
| LPOP | 0.54 | 0.82 |
| RPOP | 0.52 | 0.81 |
| SADD | 0.55 | 0.80 |
| HSET | 0.54 | 0.80 |
| SPOP | 0.54 | 0.79 |
| ZADD | 0.52 | 0.81 |
| ZPOPMIN | 0.57 | 0.80 |
| LRANGE_100 (first 100 elements) | 1.02 | 1.02 |
| LRANGE_300 (first 300 elements) | 2.29 | 1.56 |
| LRANGE_500 (first 500 elements) | 3.27 | 2.13 |
| LRANGE_600 (first 600 elements) | 3.91 | 2.37 |
| MSET (10 keys) | 0.78 | 0.84 |
Conclusion
From the friendly robots:
After analyzing the benchmarks, it's clear that the Vultr Cloud Compute instance with 4 GB of RAM and 2 cores provides significantly better performance across various metrics compared to the High Performance AMD instance with 1 GB of RAM and 1 core, especially in CPU-intensive tasks, memory operations, and Redis benchmarks. The Cloud Compute instance handles more requests per second and has lower latency for most operations, including file I/O and database operations. Ideal use cases for the Cloud Compute instance would be scenarios requiring higher CPU power and memory, such as web servers, application servers, or database workloads, while the High Performance AMD instance might be more suitable for less demanding tasks, like lightweight web services or simple data processing 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.