Vultr Cloud Compute (2 GB) vs. Vultr Cloud Compute (8 GB, 4 Cores)
My friend, I'm so glad you're here! 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 all resided in or around the New York / New Jersey area. Enough talk. Here's the data.
Overview
| Vultr – Cloud Compute (2 GB) | Vultr – Cloud Compute (8 GB, 4 Cores) | |
|---|---|---|
| Last Benchmarked | Sun, 24 May 2026 00:00:52 GMT | Sat, 23 May 2026 11: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 | $10.00 | $40.00 |
| RAM (GB) | 2 | 8 |
| CPU Cores | 1 | 4 |
| Storage (TB) | 50 | 160 |
| Storage Type | SSD | SSD |
| Transfer (TB) | 2 | 4 |
CPU
| Vultr – Cloud Compute (2 GB) | Vultr – Cloud Compute (8 GB, 4 Cores) | |
|---|---|---|
| Vendor | GenuineIntel | GenuineIntel |
| Model Name | Intel Core Processor (Skylake, IBRS, no TSX) | Intel Xeon Processor (Skylake, IBRS) |
| Clock Speed (MHz) | 3,792.00 | 2,593.90 |
| CPU Cache Size (KB) | 16,384.00 | 16,384.00 |
| BogoMips | 7,583.99 | 5,187.80 |
| Events per Second | 1,570.19 | 1,100.82 |
| Minimum Latency (ms) | 0.62 | 0.88 |
| Average Latency (ms) | 0.64 | 0.91 |
| Maximum Latency (ms) | 2.42 | 1.56 |
| 95th Percentile Latency (ms) | 0.68 | 0.97 |
Memory
Memory Read
| Vultr – Cloud Compute (2 GB) | Vultr – Cloud Compute (8 GB, 4 Cores) | |
|---|---|---|
| Operations per second | 7,754,811.85 | 3,685,781.23 |
| Mebibytes per second | 7,573.06 | 3,599.40 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.15 | 1.03 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – Cloud Compute (2 GB) | Vultr – Cloud Compute (8 GB, 4 Cores) | |
|---|---|---|
| Operations per second | 7,660,018.80 | 3,590,629.63 |
| Mebibytes per second | 7,480.49 | 3,506.47 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.16 | 1.16 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – Cloud Compute (2 GB) | Vultr – Cloud Compute (8 GB, 4 Cores) | |
|---|---|---|
| Reads per Second | 4,923.75 | 4,999.39 |
| Writes per Second | 3,282.50 | 3,332.93 |
| Fsyncs per Second | 10,516.60 | 10,670.47 |
| Read Mebibytes per Second | 76.93 | 78.12 |
| Written Mebibytes per Second | 51.29 | 52.08 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.05 | 0.05 |
| Maximum Latency (ms) | 1.71 | 37.52 |
| 95th Percentile Latency (ms) | 0.17 | 0.18 |
Mutex
| Vultr – Cloud Compute (2 GB) | Vultr – Cloud Compute (8 GB, 4 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 1,097.77 | 369.37 |
| Average Latency (ms) | 1,106.88 | 416.22 |
| Maximum Latency (ms) | 1,113.46 | 441.77 |
| 95th Percentile Latency (ms) | 1,109.09 | 442.73 |
MySQL
MySQL Read-only
| Vultr – Cloud Compute (2 GB) | Vultr – Cloud Compute (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 10,573.00 | 5,144.00 |
| Queries per second | 105,730.00 | 51,440.00 |
| Minimum Latency (ms) | 0.88 | 1.72 |
| Average Latency (ms) | 0.94 | 1.94 |
| Maximum Latency (ms) | 2.44 | 7.67 |
| 95th Percentile Latency (ms) | 1.01 | 2.35 |
MySQL Write-only
| Vultr – Cloud Compute (2 GB) | Vultr – Cloud Compute (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 9,479.00 | 5,108.00 |
| Queries per second | 94,790.00 | 51,080.00 |
| Minimum Latency (ms) | 0.68 | 1.15 |
| Average Latency (ms) | 1.05 | 1.96 |
| Maximum Latency (ms) | 3.67 | 12.52 |
| 95th Percentile Latency (ms) | 1.42 | 2.71 |
MySQL Read/Write
| Vultr – Cloud Compute (2 GB) | Vultr – Cloud Compute (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 4,345.00 | 2,247.00 |
| Queries per second | 43,450.00 | 22,470.00 |
| Minimum Latency (ms) | 1.81 | 3.08 |
| Average Latency (ms) | 2.3 | 4.45 |
| Maximum Latency (ms) | 16.56 | 29.7 |
| 95th Percentile Latency (ms) | 2.81 | 5.28 |
MySQL INSERT
| Vultr – Cloud Compute (2 GB) | Vultr – Cloud Compute (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 16,503.00 | 7,630.00 |
| Queries per second | 165,030.00 | 76,300.00 |
| Minimum Latency (ms) | 0.37 | 0.71 |
| Average Latency (ms) | 0.6 | 1.31 |
| Maximum Latency (ms) | 2.13 | 29.81 |
| 95th Percentile Latency (ms) | 0.78 | 1.55 |
MySQL Bulk INSERT
| Vultr – Cloud Compute (2 GB) | Vultr – Cloud Compute (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 2,103,967.00 | 898,571.00 |
| Queries per second | 21,039,670.00 | 8,985,710.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0.01 |
| Maximum Latency (ms) | 228.8 | 505.86 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – Cloud Compute (2 GB) | Vultr – Cloud Compute (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 231,690.00 | 149,465.00 |
| Queries per second | 2,316,900.00 | 1,494,650.00 |
| Minimum Latency (ms) | 0.04 | 0.05 |
| Average Latency (ms) | 0.04 | 0.07 |
| Maximum Latency (ms) | 0.93 | 1.22 |
| 95th Percentile Latency (ms) | 0.06 | 0.09 |
MySQL SELECT (Random Points)
| Vultr – Cloud Compute (2 GB) | Vultr – Cloud Compute (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 10,866.00 | 4,249.00 |
| Queries per second | 108,660.00 | 42,490.00 |
| Minimum Latency (ms) | 0.32 | 0.83 |
| Average Latency (ms) | 0.92 | 2.35 |
| Maximum Latency (ms) | 3.21 | 6.6 |
| 95th Percentile Latency (ms) | 1.18 | 3.02 |
MySQL SELECT (Random Ranges)
| Vultr – Cloud Compute (2 GB) | Vultr – Cloud Compute (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 10,969.00 | 2,637.00 |
| Queries per second | 109,690.00 | 26,370.00 |
| Minimum Latency (ms) | 0.23 | 0.94 |
| Average Latency (ms) | 0.91 | 3.79 |
| Maximum Latency (ms) | 2.54 | 6.3 |
| 95th Percentile Latency (ms) | 1.18 | 5.09 |
MySQL UPDATE (Indexed)
| Vultr – Cloud Compute (2 GB) | Vultr – Cloud Compute (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 15,225.00 | 7,166.00 |
| Queries per second | 152,250.00 | 71,660.00 |
| Minimum Latency (ms) | 0.38 | 0.7 |
| Average Latency (ms) | 0.66 | 1.39 |
| Maximum Latency (ms) | 2.32 | 28.84 |
| 95th Percentile Latency (ms) | 0.92 | 1.79 |
MySQL UPDATE (Non-Indexed)
| Vultr – Cloud Compute (2 GB) | Vultr – Cloud Compute (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 16,166.00 | 7,661.00 |
| Queries per second | 161,660.00 | 76,610.00 |
| Minimum Latency (ms) | 0.38 | 0.7 |
| Average Latency (ms) | 0.62 | 1.3 |
| Maximum Latency (ms) | 2.03 | 33.97 |
| 95th Percentile Latency (ms) | 0.81 | 1.58 |
MySQL DELETE
| Vultr – Cloud Compute (2 GB) | Vultr – Cloud Compute (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 141,631.00 | 69,690.00 |
| Queries per second | 1,416,310.00 | 696,900.00 |
| Minimum Latency (ms) | 0.04 | 0.05 |
| Average Latency (ms) | 0.07 | 0.14 |
| Maximum Latency (ms) | 4.27 | 27.73 |
| 95th Percentile Latency (ms) | 0.1 | 0.87 |
Redis
| Vultr – Cloud Compute (2 GB) | Vultr – Cloud Compute (8 GB, 4 Cores) | |
|---|---|---|
| PING_INLINE per Second | 54,083.29 | 54,436.58 |
| PING_MBULK per Second | 54,854.64 | 48,828.12 |
| SET per Second | 54,734.54 | 51,572.98 |
| GET per Second | 55,157.20 | 48,239.27 |
| INCR per Second | 55,218.11 | 52,328.62 |
| LPUSH per Second | 54,495.91 | 45,454.54 |
| RPUSH per Second | 53,276.50 | 49,751.24 |
| LPOP per Second | 52,994.17 | 53,390.28 |
| RPOP per Second | 53,022.27 | 53,648.07 |
| SADD per Second | 53,533.19 | 48,285.85 |
| HSET per Second | 53,219.80 | 51,493.30 |
| SPOP per Second | 53,333.33 | 52,910.05 |
| ZADD per Second | 54,585.15 | 53,504.55 |
| ZPOPMIN per Second | 55,340.34 | 53,590.57 |
| LRANGE_100 (first 100 elements) per Second | 37,202.38 | 28,645.09 |
| LRANGE_300 (first 300 elements) per Second | 20,316.95 | 13,131.98 |
| LRANGE_500 (first 500 elements) per Second | 14,148.27 | 8,529.51 |
| LRANGE_600 (first 600 elements) per Second | 12,487.51 | 7,479.99 |
| MSET (10 keys) per Second | 51,308.36 | 49,212.60 |
Redis Average Latency (ms)
| Vultr – Cloud Compute (2 GB) | Vultr – Cloud Compute (8 GB, 4 Cores) | |
|---|---|---|
| PING_INLINE | 0.61 | 0.47 |
| PING_MBULK | 0.59 | 0.53 |
| SET | 0.60 | 0.50 |
| GET | 0.59 | 0.54 |
| INCR | 0.59 | 0.49 |
| LPUSH | 0.60 | 0.58 |
| RPUSH | 0.62 | 0.52 |
| LPOP | 0.62 | 0.49 |
| RPOP | 0.62 | 0.48 |
| SADD | 0.61 | 0.54 |
| HSET | 0.62 | 0.53 |
| SPOP | 0.61 | 0.49 |
| ZADD | 0.60 | 0.48 |
| ZPOPMIN | 0.59 | 0.48 |
| LRANGE_100 (first 100 elements) | 0.92 | 0.91 |
| LRANGE_300 (first 300 elements) | 1.71 | 1.94 |
| LRANGE_500 (first 500 elements) | 2.54 | 3.00 |
| LRANGE_600 (first 600 elements) | 2.89 | 3.43 |
| MSET (10 keys) | 0.67 | 0.77 |
Conclusion
From the friendly robots:
After analyzing the benchmarks from both Vultr instances, it is evident that the Cloud Compute (8 GB, 4 Cores) instance significantly outperforms the Cloud Compute (2 GB) instance across various metrics. The 8 GB instance demonstrates much higher performance in Redis operations, achieving substantially higher requests per second and lower average latencies for most commands, alongside better CPU performance and greater I/O throughput. While the 2 GB instance has competitive I/O and memory performance metrics, its single CPU core and lower RAM limit its throughput and responsiveness, especially in CPU-intensive and I/O-heavy workloads. Therefore, the Cloud Compute (8 GB, 4 Cores) instance is recommended for use cases requiring high concurrency, intensive computation, or large datasets, such as high-traffic web applications, database servers, or large-scale caching solutions.
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.