Vultr Cloud Compute (1 GB) vs. Vultr Cloud Compute (2 GB)
Welcome to another round of the VPS Showdown. Today I've spun up some brand new instance from Vultr to run some benchmarks on. Each instance was running Ubuntu 24.04 LTS x64 and all resided in or around the New York / New Jersey area. Time to see who showed up today.
Overview
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Last Benchmarked | Wed, 18 Feb 2026 07:00:51 GMT | Wed, 18 Feb 2026 18:00:52 GMT |
| Linux Distro | Ubuntu 24.04 LTS x64 | Ubuntu 24.04 LTS x64 |
| Kernel Version | 6.8.0-100-generic | 6.8.0-100-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 | $5.00 | $10.00 |
| RAM (GB) | 1 | 2 |
| CPU Cores | 1 | 1 |
| Storage (TB) | 25 | 50 |
| Storage Type | SSD | SSD |
| Transfer (TB) | 1 | 2 |
CPU
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Vendor | GenuineIntel | GenuineIntel |
| Model Name | Intel Core Processor (Haswell, no TSX, IBRS) | Intel Xeon Processor (Skylake, IBRS) |
| Clock Speed (MHz) | 2,400.00 | 2,593.90 |
| CPU Cache Size (KB) | 16,384.00 | 16,384.00 |
| BogoMips | 4,799.99 | 5,187.80 |
| Events per Second | 789.59 | 1,010.84 |
| Minimum Latency (ms) | 1.16 | 0.88 |
| Average Latency (ms) | 1.27 | 0.99 |
| Maximum Latency (ms) | 3.45 | 3.02 |
| 95th Percentile Latency (ms) | 1.34 | 1.25 |
Memory
Memory Read
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Operations per second | 3,918,177.35 | 3,619,674.26 |
| Mebibytes per second | 3,826.35 | 3,534.84 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.23 | 0.65 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Operations per second | 3,908,567.36 | 3,570,885.50 |
| Mebibytes per second | 3,816.96 | 3,487.19 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.45 | 0.41 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Reads per Second | 1,594.63 | 2,872.19 |
| Writes per Second | 1,063.09 | 1,914.80 |
| Fsyncs per Second | 3,407.62 | 6,137.94 |
| Read Mebibytes per Second | 24.92 | 44.88 |
| Written Mebibytes per Second | 16.61 | 29.92 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.16 | 0.09 |
| Maximum Latency (ms) | 32.52 | 6.82 |
| 95th Percentile Latency (ms) | 0.42 | 0.23 |
Mutex
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Minimum Latency (ms) | 2,039.00 | 2,157.93 |
| Average Latency (ms) | 2,047.18 | 2,174.09 |
| Maximum Latency (ms) | 2,058.11 | 2,179.35 |
| 95th Percentile Latency (ms) | 2,045.74 | 2,198.52 |
MySQL
MySQL Read-only
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 4,857.00 | 5,398.00 |
| Queries per second | 48,570.00 | 53,980.00 |
| Minimum Latency (ms) | 1.84 | 1.54 |
| Average Latency (ms) | 2.06 | 1.85 |
| Maximum Latency (ms) | 8.4 | 4.98 |
| 95th Percentile Latency (ms) | 2.18 | 2.22 |
MySQL Write-only
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 2,825.00 | 5,053.00 |
| Queries per second | 28,250.00 | 50,530.00 |
| Minimum Latency (ms) | 1.95 | 1.25 |
| Average Latency (ms) | 3.54 | 1.98 |
| Maximum Latency (ms) | 32.06 | 15.79 |
| 95th Percentile Latency (ms) | 6.32 | 2.81 |
MySQL Read/Write
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 1,532.00 | 2,184.00 |
| Queries per second | 15,320.00 | 21,840.00 |
| Minimum Latency (ms) | 4.34 | 3.44 |
| Average Latency (ms) | 6.52 | 4.57 |
| Maximum Latency (ms) | 35 | 17.5 |
| 95th Percentile Latency (ms) | 10.27 | 5.88 |
MySQL INSERT
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 4,892.00 | 8,876.00 |
| Queries per second | 48,920.00 | 88,760.00 |
| Minimum Latency (ms) | 1.12 | 0.67 |
| Average Latency (ms) | 2.04 | 1.12 |
| Maximum Latency (ms) | 19.75 | 8.5 |
| 95th Percentile Latency (ms) | 3.96 | 1.44 |
MySQL Bulk INSERT
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 833,039.00 | 701,975.00 |
| Queries per second | 8,330,390.00 | 7,019,750.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0.01 |
| Maximum Latency (ms) | 655.03 | 715.07 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 102,586.00 | 162,598.00 |
| Queries per second | 1,025,860.00 | 1,625,980.00 |
| Minimum Latency (ms) | 0.07 | 0.05 |
| Average Latency (ms) | 0.1 | 0.06 |
| Maximum Latency (ms) | 2.33 | 1.64 |
| 95th Percentile Latency (ms) | 0.13 | 0.09 |
MySQL SELECT (Random Points)
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 5,155.00 | 3,804.00 |
| Queries per second | 51,550.00 | 38,040.00 |
| Minimum Latency (ms) | 0.65 | 1.09 |
| Average Latency (ms) | 1.94 | 2.63 |
| Maximum Latency (ms) | 10.67 | 6.21 |
| 95th Percentile Latency (ms) | 2.52 | 3.49 |
MySQL SELECT (Random Ranges)
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 5,999.00 | 2,550.00 |
| Queries per second | 59,990.00 | 25,500.00 |
| Minimum Latency (ms) | 0.53 | 1.28 |
| Average Latency (ms) | 1.67 | 3.92 |
| Maximum Latency (ms) | 7.75 | 12.53 |
| 95th Percentile Latency (ms) | 2.18 | 5.37 |
MySQL UPDATE (Indexed)
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 3,979.00 | 8,470.00 |
| Queries per second | 39,790.00 | 84,700.00 |
| Minimum Latency (ms) | 1.1 | 0.65 |
| Average Latency (ms) | 2.51 | 1.18 |
| Maximum Latency (ms) | 36.68 | 8.3 |
| 95th Percentile Latency (ms) | 4.91 | 1.79 |
MySQL UPDATE (Non-Indexed)
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 4,131.00 | 9,227.00 |
| Queries per second | 41,310.00 | 92,270.00 |
| Minimum Latency (ms) | 1.21 | 0.66 |
| Average Latency (ms) | 2.42 | 1.08 |
| Maximum Latency (ms) | 24.52 | 9.2 |
| 95th Percentile Latency (ms) | 4.91 | 1.37 |
MySQL DELETE
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 30,696.00 | 71,146.00 |
| Queries per second | 306,960.00 | 711,460.00 |
| Minimum Latency (ms) | 0.08 | 0.05 |
| Average Latency (ms) | 0.32 | 0.14 |
| Maximum Latency (ms) | 51.16 | 7.62 |
| 95th Percentile Latency (ms) | 1.76 | 0.89 |
Redis
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| PING_INLINE per Second | 33,715.44 | 35,248.50 |
| PING_MBULK per Second | 35,663.34 | 37,313.43 |
| SET per Second | 34,602.07 | 35,523.98 |
| GET per Second | 37,243.95 | 34,698.12 |
| INCR per Second | 35,310.73 | 35,599.86 |
| LPUSH per Second | 35,549.23 | 35,186.49 |
| RPUSH per Second | 35,739.81 | 32,393.91 |
| LPOP per Second | 36,818.85 | 31,525.85 |
| RPOP per Second | 35,460.99 | 34,376.07 |
| SADD per Second | 36,589.83 | 35,574.53 |
| HSET per Second | 36,114.12 | 35,398.23 |
| SPOP per Second | 37,299.52 | 35,868.00 |
| ZADD per Second | 35,511.36 | 36,179.45 |
| ZPOPMIN per Second | 37,009.62 | 35,335.69 |
| LRANGE_100 (first 100 elements) per Second | 23,986.57 | 15,060.24 |
| LRANGE_300 (first 300 elements) per Second | 12,658.23 | 6,957.49 |
| LRANGE_500 (first 500 elements) per Second | 8,469.55 | 4,547.31 |
| LRANGE_600 (first 600 elements) per Second | 7,245.33 | 3,769.32 |
| MSET (10 keys) per Second | 32,819.17 | 29,481.13 |
Redis Average Latency (ms)
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| PING_INLINE | 0.99 | 0.91 |
| PING_MBULK | 0.91 | 0.87 |
| SET | 0.95 | 0.92 |
| GET | 0.88 | 0.93 |
| INCR | 0.93 | 0.91 |
| LPUSH | 0.93 | 0.92 |
| RPUSH | 0.93 | 0.99 |
| LPOP | 0.91 | 1.02 |
| RPOP | 0.94 | 0.95 |
| SADD | 0.90 | 0.91 |
| HSET | 0.91 | 0.92 |
| SPOP | 0.88 | 0.90 |
| ZADD | 0.93 | 0.91 |
| ZPOPMIN | 0.89 | 0.91 |
| LRANGE_100 (first 100 elements) | 1.39 | 2.31 |
| LRANGE_300 (first 300 elements) | 2.66 | 4.92 |
| LRANGE_500 (first 500 elements) | 4.01 | 7.35 |
| LRANGE_600 (first 600 elements) | 4.62 | 8.64 |
| MSET (10 keys) | 1.06 | 1.20 |
Conclusion
From the friendly robots:
Upon comparing the benchmarks of Vultr's Cloud Compute instances, the 1 GB variant demonstrates robust performance in simple Redis operations, achieving high request rates with low latency, particularly excelling in SET, GET, INCR, and LPUSH operations. However, its performance degrades significantly for complex operations such as LRANGE with larger datasets, where throughput drops dramatically and latency spikes. The 2 GB instance, while matching the 1 GB in straightforward Redis operations, notably outperforms in complex tasks involving larger datasets due to its higher RAM, resulting in better throughput and lower latency for LRANGE operations. The 2 GB instance also shows slightly superior CPU performance and better I/O operations, making it a better choice for CPU-intensive and I/O-heavy workloads, whereas the 1 GB instance remains well-suited for lighter, less data-intensive tasks.
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.