Vultr Cloud Compute (2 GB, 2 Cores) vs. Vultr High Performance AMD (1 GB)
New day, new benchmarks. 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. Without further ado, here's the results.
Overview
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Last Benchmarked | Mon, 11 May 2026 04:00:52 GMT | Sun, 10 May 2026 21:00:52 GMT |
| Linux Distro | Ubuntu 24.04 LTS x64 | Ubuntu 24.04 LTS x64 |
| Kernel Version | 6.8.0-111-generic | 6.8.0-111-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 | $15.00 | $6.00 |
| RAM (GB) | 2 | 1 |
| CPU Cores | 2 | 1 |
| Storage (TB) | 65 | 25 |
| Storage Type | SSD | NVMe |
| Transfer (TB) | 3 | 2 |
CPU
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Vendor | GenuineIntel | AuthenticAMD |
| Model Name | Intel Core Processor (Skylake, IBRS, no TSX) | AMD EPYC-Genoa Processor |
| Clock Speed (MHz) | 3,792.00 | 2,899.97 |
| CPU Cache Size (KB) | 16,384.00 | 1,024.00 |
| BogoMips | 7,583.99 | 5,799.93 |
| Events per Second | 1,481.60 | 4,622.39 |
| Minimum Latency (ms) | 0.63 | 0.2 |
| Average Latency (ms) | 0.67 | 0.22 |
| Maximum Latency (ms) | 1.95 | 1.95 |
| 95th Percentile Latency (ms) | 0.77 | 0.23 |
Memory
Memory Read
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Operations per second | 6,401,389.08 | 7,509,543.91 |
| Mebibytes per second | 6,251.36 | 7,333.54 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.23 | 4.72 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Operations per second | 6,411,085.35 | 7,535,339.68 |
| Mebibytes per second | 6,260.83 | 7,358.73 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.18 | 0.31 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Reads per Second | 4,345.71 | 4,902.51 |
| Writes per Second | 2,897.07 | 3,268.27 |
| Fsyncs per Second | 9,273.19 | 10,464.22 |
| Read Mebibytes per Second | 67.90 | 76.60 |
| Written Mebibytes per Second | 45.27 | 51.07 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.06 | 0.05 |
| Maximum Latency (ms) | 2.92 | 1.71 |
| 95th Percentile Latency (ms) | 0.17 | 0.11 |
Mutex
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Minimum Latency (ms) | 214.63 | 1,231.80 |
| Average Latency (ms) | 569.72 | 1,235.99 |
| Maximum Latency (ms) | 636.55 | 1,242.95 |
| 95th Percentile Latency (ms) | 634.66 | 1,235.62 |
MySQL
MySQL Read-only
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Transactions per second | 8,015.00 | 13,277.00 |
| Queries per second | 80,150.00 | 132,770.00 |
| Minimum Latency (ms) | 0.92 | 0.69 |
| Average Latency (ms) | 1.25 | 0.75 |
| Maximum Latency (ms) | 5.5 | 3.74 |
| 95th Percentile Latency (ms) | 1.86 | 0.8 |
MySQL Write-only
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Transactions per second | 8,497.00 | 10,040.00 |
| Queries per second | 84,970.00 | 100,400.00 |
| Minimum Latency (ms) | 0.76 | 0.67 |
| Average Latency (ms) | 1.17 | 0.99 |
| Maximum Latency (ms) | 3.04 | 4.8 |
| 95th Percentile Latency (ms) | 1.55 | 1.39 |
MySQL Read/Write
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Transactions per second | 3,726.00 | 5,116.00 |
| Queries per second | 37,260.00 | 51,160.00 |
| Minimum Latency (ms) | 1.78 | 1.57 |
| Average Latency (ms) | 2.68 | 1.95 |
| Maximum Latency (ms) | 5.82 | 6.23 |
| 95th Percentile Latency (ms) | 3.43 | 2.39 |
MySQL INSERT
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Transactions per second | 15,028.00 | 17,372.00 |
| Queries per second | 150,280.00 | 173,720.00 |
| Minimum Latency (ms) | 0.41 | 0.43 |
| Average Latency (ms) | 0.66 | 0.57 |
| Maximum Latency (ms) | 2.42 | 2.19 |
| 95th Percentile Latency (ms) | 0.86 | 0.7 |
MySQL Bulk INSERT
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Transactions per second | 1,696,217.00 | 2,569,967.00 |
| Queries per second | 16,962,170.00 | 25,699,670.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0 |
| Maximum Latency (ms) | 283.37 | 244.33 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Transactions per second | 201,989.00 | 350,666.00 |
| Queries per second | 2,019,890.00 | 3,506,660.00 |
| Minimum Latency (ms) | 0.03 | 0.02 |
| Average Latency (ms) | 0.05 | 0.03 |
| Maximum Latency (ms) | 0.51 | 3.48 |
| 95th Percentile Latency (ms) | 0.07 | 0.04 |
MySQL SELECT (Random Points)
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Transactions per second | 8,025.00 | 14,543.00 |
| Queries per second | 80,250.00 | 145,430.00 |
| Minimum Latency (ms) | 0.35 | 0.24 |
| Average Latency (ms) | 1.24 | 0.69 |
| Maximum Latency (ms) | 3.55 | 3.06 |
| 95th Percentile Latency (ms) | 2.07 | 0.87 |
MySQL SELECT (Random Ranges)
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Transactions per second | 8,336.00 | 14,708.00 |
| Queries per second | 83,360.00 | 147,080.00 |
| Minimum Latency (ms) | 0.4 | 0.24 |
| Average Latency (ms) | 1.2 | 0.68 |
| Maximum Latency (ms) | 4.25 | 2.34 |
| 95th Percentile Latency (ms) | 2.22 | 0.87 |
MySQL UPDATE (Indexed)
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Transactions per second | 13,858.00 | 14,482.00 |
| Queries per second | 138,580.00 | 144,820.00 |
| Minimum Latency (ms) | 0.42 | 0.43 |
| Average Latency (ms) | 0.72 | 0.69 |
| Maximum Latency (ms) | 6.33 | 12.9 |
| 95th Percentile Latency (ms) | 0.95 | 1.06 |
MySQL UPDATE (Non-Indexed)
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Transactions per second | 14,587.00 | 16,290.00 |
| Queries per second | 145,870.00 | 162,900.00 |
| Minimum Latency (ms) | 0.4 | 0.43 |
| Average Latency (ms) | 0.68 | 0.61 |
| Maximum Latency (ms) | 11.69 | 3.81 |
| 95th Percentile Latency (ms) | 0.9 | 0.87 |
MySQL DELETE
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| Transactions per second | 129,013.00 | 221,408.00 |
| Queries per second | 1,290,130.00 | 2,214,080.00 |
| Minimum Latency (ms) | 0.03 | 0.02 |
| Average Latency (ms) | 0.08 | 0.04 |
| Maximum Latency (ms) | 2.61 | 4.12 |
| 95th Percentile Latency (ms) | 0.09 | 0.07 |
Redis
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| PING_INLINE per Second | 78,247.26 | 43,233.89 |
| PING_MBULK per Second | 74,738.41 | 43,936.73 |
| SET per Second | 77,041.60 | 43,459.36 |
| GET per Second | 83,333.33 | 43,365.13 |
| INCR per Second | 80,971.66 | 43,516.10 |
| LPUSH per Second | 79,113.92 | 43,402.78 |
| RPUSH per Second | 77,160.49 | 43,402.78 |
| LPOP per Second | 81,499.59 | 43,047.79 |
| RPOP per Second | 82,440.23 | 43,233.89 |
| SADD per Second | 80,192.46 | 43,687.20 |
| HSET per Second | 83,612.04 | 43,290.04 |
| SPOP per Second | 85,034.02 | 38,684.72 |
| ZADD per Second | 83,263.95 | 42,992.26 |
| ZPOPMIN per Second | 82,987.55 | 43,706.29 |
| LRANGE_100 (first 100 elements) per Second | 55,555.56 | 33,670.04 |
| LRANGE_300 (first 300 elements) per Second | 28,851.70 | 21,743.86 |
| LRANGE_500 (first 500 elements) per Second | 19,391.12 | 16,334.53 |
| LRANGE_600 (first 600 elements) per Second | 17,211.71 | 14,539.11 |
| MSET (10 keys) per Second | 80,256.82 | 41,476.57 |
Redis Average Latency (ms)
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance AMD (1 GB) | |
|---|---|---|
| PING_INLINE | 0.34 | 0.77 |
| PING_MBULK | 0.35 | 0.76 |
| SET | 0.34 | 0.77 |
| GET | 0.32 | 0.77 |
| INCR | 0.32 | 0.77 |
| LPUSH | 0.34 | 0.78 |
| RPUSH | 0.34 | 0.77 |
| LPOP | 0.32 | 0.78 |
| RPOP | 0.32 | 0.78 |
| SADD | 0.32 | 0.77 |
| HSET | 0.31 | 0.77 |
| SPOP | 0.30 | 0.89 |
| ZADD | 0.31 | 0.77 |
| ZPOPMIN | 0.31 | 0.76 |
| LRANGE_100 (first 100 elements) | 0.54 | 0.99 |
| LRANGE_300 (first 300 elements) | 1.11 | 1.50 |
| LRANGE_500 (first 500 elements) | 1.62 | 2.05 |
| LRANGE_600 (first 600 elements) | 1.84 | 2.30 |
| MSET (10 keys) | 0.38 | 0.81 |
Conclusion
From the friendly robots:
Both VPS instances from Vultr demonstrate solid performance, but they excel in different areas. The "Cloud Compute (2 GB, 2 Cores)" instance shows higher throughput rates for Redis operations and file I/O, indicating better random read/write speeds and memory bandwidth. It also performs better for MySQL and general CPU-intensive tasks. However, the "High Performance AMD (1 GB)" instance, powered by an AMD EPYC processor, exhibits superior performance in CPU-bound benchmarks, lower latency in file I/O operations, and slightly better Redis performance. Ideal use cases for the former include applications requiring moderate CPU power with extensive I/O operations, such as web servers with heavy database interaction. The latter is better suited for CPU-intensive workloads like high-performance computing tasks, low-latency requirements, and applications needing robust memory performance.
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.