Vultr Cloud Compute (8 GB, 4 Cores) vs. Vultr High Performance AMD (1 GB)
Same showdown, different day. Today I've spun up brand new instance from Vultr and did some benchmarking. Each instance was running 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 (1 GB) | |
|---|---|---|
| Last Benchmarked | Sat, 23 May 2026 11:00:52 GMT | Sat, 23 May 2026 07: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 | $6.00 |
| RAM (GB) | 8 | 1 |
| CPU Cores | 4 | 1 |
| Storage (TB) | 160 | 25 |
| Storage Type | SSD | NVMe |
| Transfer (TB) | 4 | 2 |
CPU
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| 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.01 |
| Events per Second | 1,100.82 | 4,573.31 |
| Minimum Latency (ms) | 0.88 | 0.2 |
| Average Latency (ms) | 0.91 | 0.22 |
| Maximum Latency (ms) | 1.56 | 3.23 |
| 95th Percentile Latency (ms) | 0.97 | 0.23 |
Memory
Memory Read
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Operations per second | 3,685,781.23 | 7,351,256.40 |
| Mebibytes per second | 3,599.40 | 7,178.96 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 1.03 | 0.59 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Operations per second | 3,590,629.63 | 7,439,366.29 |
| Mebibytes per second | 3,506.47 | 7,265.01 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 1.16 | 0.75 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Reads per Second | 4,999.39 | 5,103.47 |
| Writes per Second | 3,332.93 | 3,402.31 |
| Fsyncs per Second | 10,670.47 | 10,892.80 |
| Read Mebibytes per Second | 78.12 | 79.74 |
| Written Mebibytes per Second | 52.08 | 53.16 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.05 | 0.05 |
| Maximum Latency (ms) | 37.52 | 1.76 |
| 95th Percentile Latency (ms) | 0.18 | 0.11 |
Mutex
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Minimum Latency (ms) | 369.37 | 1,235.71 |
| Average Latency (ms) | 416.22 | 1,242.82 |
| Maximum Latency (ms) | 441.77 | 1,247.75 |
| 95th Percentile Latency (ms) | 442.73 | 1,258.08 |
MySQL
MySQL Read-only
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Transactions per second | 5,144.00 | 13,050.00 |
| Queries per second | 51,440.00 | 130,500.00 |
| Minimum Latency (ms) | 1.72 | 0.72 |
| Average Latency (ms) | 1.94 | 0.77 |
| Maximum Latency (ms) | 7.67 | 4.96 |
| 95th Percentile Latency (ms) | 2.35 | 0.81 |
MySQL Write-only
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Transactions per second | 5,108.00 | 9,966.00 |
| Queries per second | 51,080.00 | 99,660.00 |
| Minimum Latency (ms) | 1.15 | 0.66 |
| Average Latency (ms) | 1.96 | 1 |
| Maximum Latency (ms) | 12.52 | 7.04 |
| 95th Percentile Latency (ms) | 2.71 | 1.42 |
MySQL Read/Write
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Transactions per second | 2,247.00 | 5,017.00 |
| Queries per second | 22,470.00 | 50,170.00 |
| Minimum Latency (ms) | 3.08 | 1.61 |
| Average Latency (ms) | 4.45 | 1.99 |
| Maximum Latency (ms) | 29.7 | 5.56 |
| 95th Percentile Latency (ms) | 5.28 | 2.43 |
MySQL INSERT
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Transactions per second | 7,630.00 | 16,971.00 |
| Queries per second | 76,300.00 | 169,710.00 |
| Minimum Latency (ms) | 0.71 | 0.43 |
| Average Latency (ms) | 1.31 | 0.59 |
| Maximum Latency (ms) | 29.81 | 11.7 |
| 95th Percentile Latency (ms) | 1.55 | 0.73 |
MySQL Bulk INSERT
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Transactions per second | 898,571.00 | 2,424,342.00 |
| Queries per second | 8,985,710.00 | 24,243,420.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0 |
| Maximum Latency (ms) | 505.86 | 254.92 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Transactions per second | 149,465.00 | 337,545.00 |
| Queries per second | 1,494,650.00 | 3,375,450.00 |
| Minimum Latency (ms) | 0.05 | 0.02 |
| Average Latency (ms) | 0.07 | 0.03 |
| Maximum Latency (ms) | 1.22 | 2.65 |
| 95th Percentile Latency (ms) | 0.09 | 0.04 |
MySQL SELECT (Random Points)
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Transactions per second | 4,249.00 | 14,387.00 |
| Queries per second | 42,490.00 | 143,870.00 |
| Minimum Latency (ms) | 0.83 | 0.27 |
| Average Latency (ms) | 2.35 | 0.69 |
| Maximum Latency (ms) | 6.6 | 3.25 |
| 95th Percentile Latency (ms) | 3.02 | 0.9 |
MySQL SELECT (Random Ranges)
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Transactions per second | 2,637.00 | 14,628.00 |
| Queries per second | 26,370.00 | 146,280.00 |
| Minimum Latency (ms) | 0.94 | 0.27 |
| Average Latency (ms) | 3.79 | 0.68 |
| Maximum Latency (ms) | 6.3 | 2.03 |
| 95th Percentile Latency (ms) | 5.09 | 0.89 |
MySQL UPDATE (Indexed)
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Transactions per second | 7,166.00 | 15,835.00 |
| Queries per second | 71,660.00 | 158,350.00 |
| Minimum Latency (ms) | 0.7 | 0.42 |
| Average Latency (ms) | 1.39 | 0.63 |
| Maximum Latency (ms) | 28.84 | 5.28 |
| 95th Percentile Latency (ms) | 1.79 | 0.95 |
MySQL UPDATE (Non-Indexed)
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Transactions per second | 7,661.00 | 15,875.00 |
| Queries per second | 76,610.00 | 158,750.00 |
| Minimum Latency (ms) | 0.7 | 0.43 |
| Average Latency (ms) | 1.3 | 0.63 |
| Maximum Latency (ms) | 33.97 | 3.45 |
| 95th Percentile Latency (ms) | 1.58 | 0.89 |
MySQL DELETE
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Transactions per second | 69,690.00 | 209,119.00 |
| Queries per second | 696,900.00 | 2,091,190.00 |
| Minimum Latency (ms) | 0.05 | 0.02 |
| Average Latency (ms) | 0.14 | 0.05 |
| Maximum Latency (ms) | 27.73 | 5.7 |
| 95th Percentile Latency (ms) | 0.87 | 0.08 |
Redis
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| PING_INLINE per Second | 54,436.58 | 42,535.09 |
| PING_MBULK per Second | 48,828.12 | 42,390.84 |
| SET per Second | 51,572.98 | 42,698.55 |
| GET per Second | 48,239.27 | 43,497.17 |
| INCR per Second | 52,328.62 | 43,383.95 |
| LPUSH per Second | 45,454.54 | 43,047.79 |
| RPUSH per Second | 49,751.24 | 43,159.26 |
| LPOP per Second | 53,390.28 | 42,844.90 |
| RPOP per Second | 53,648.07 | 36,630.04 |
| SADD per Second | 48,285.85 | 42,607.59 |
| HSET per Second | 51,493.30 | 42,753.31 |
| SPOP per Second | 52,910.05 | 43,010.75 |
| ZADD per Second | 53,504.55 | 42,319.09 |
| ZPOPMIN per Second | 53,590.57 | 43,103.45 |
| LRANGE_100 (first 100 elements) per Second | 28,645.09 | 33,244.68 |
| LRANGE_300 (first 300 elements) per Second | 13,131.98 | 21,905.80 |
| LRANGE_500 (first 500 elements) per Second | 8,529.51 | 16,326.53 |
| LRANGE_600 (first 600 elements) per Second | 7,479.99 | 14,403.00 |
| MSET (10 keys) per Second | 49,212.60 | 36,954.91 |
Redis Average Latency (ms)
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| PING_INLINE | 0.47 | 0.78 |
| PING_MBULK | 0.53 | 0.78 |
| SET | 0.50 | 0.79 |
| GET | 0.54 | 0.77 |
| INCR | 0.49 | 0.77 |
| LPUSH | 0.58 | 0.78 |
| RPUSH | 0.52 | 0.78 |
| LPOP | 0.49 | 0.79 |
| RPOP | 0.48 | 0.95 |
| SADD | 0.54 | 0.79 |
| HSET | 0.53 | 0.79 |
| SPOP | 0.49 | 0.78 |
| ZADD | 0.48 | 0.79 |
| ZPOPMIN | 0.48 | 0.78 |
| LRANGE_100 (first 100 elements) | 0.91 | 1.00 |
| LRANGE_300 (first 300 elements) | 1.94 | 1.50 |
| LRANGE_500 (first 500 elements) | 3.00 | 2.06 |
| LRANGE_600 (first 600 elements) | 3.43 | 2.32 |
| MSET (10 keys) | 0.77 | 0.93 |
Conclusion
From the friendly robots:
Both instances from Vultr show distinct strengths tailored to different workloads. The Cloud Compute (8 GB, 4 Cores) instance excels in CPU-intensive tasks with higher performance in Redis benchmarks, better overall throughput in memory operations, and better file IO performance, making it ideal for applications demanding high multi-threading capabilities and memory operations. Conversely, the High Performance AMD (1 GB) instance provides superior performance in CPU-bound and memory-intensive tasks, with faster Redis operations, higher throughput in file operations, and more efficient MySQL performance, making it suitable for applications that require strong single-core processing power and high memory bandwidth. Depending on whether the workload favors multi-core processing or single-threaded efficiency, these instances present optimal choices.
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.