Vultr Cloud Compute (1 GB) vs. Vultr Cloud Compute (2 GB)
Same showdown, different day. Today I've spun up some brand new instance from Vultr and ran some benchmarks. All instances were running 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 (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Last Benchmarked | Mon, 12 Jan 2026 01:00:52 GMT | Mon, 12 Jan 2026 05:00:51 GMT |
| Linux Distro | Ubuntu 24.04 LTS x64 | Ubuntu 24.04 LTS x64 |
| Kernel Version | 6.8.0-90-generic | 6.8.0-90-generic |
| MySQL Version | 8.0.44-0ubuntu0.24.04.2 | 8.0.44-0ubuntu0.24.04.2 |
| 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.79 |
| Events per Second | 805.88 | 918.93 |
| Minimum Latency (ms) | 1.02 | 0.89 |
| Average Latency (ms) | 1.24 | 1.09 |
| Maximum Latency (ms) | 6.6 | 4.31 |
| 95th Percentile Latency (ms) | 1.37 | 1.39 |
Memory
Memory Read
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Operations per second | 4,121,312.27 | 3,131,236.30 |
| Mebibytes per second | 4,024.72 | 3,057.85 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.95 | 1.16 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Operations per second | 4,116,548.02 | 3,233,842.60 |
| Mebibytes per second | 4,020.07 | 3,158.05 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.71 | 0.82 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Reads per Second | 2,171.48 | 2,170.20 |
| Writes per Second | 1,447.66 | 1,446.80 |
| Fsyncs per Second | 4,641.45 | 4,639.94 |
| Read Mebibytes per Second | 33.93 | 33.91 |
| Written Mebibytes per Second | 22.62 | 22.61 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.12 | 0.12 |
| Maximum Latency (ms) | 14.98 | 10.23 |
| 95th Percentile Latency (ms) | 0.31 | 0.39 |
Mutex
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Minimum Latency (ms) | 1,925.48 | 2,247.43 |
| Average Latency (ms) | 1,936.26 | 2,315.45 |
| Maximum Latency (ms) | 1,944.23 | 2,351.95 |
| 95th Percentile Latency (ms) | 1,938.16 | 2,362.72 |
MySQL
MySQL Read-only
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 4,956.00 | 4,168.00 |
| Queries per second | 49,560.00 | 41,680.00 |
| Minimum Latency (ms) | 1.69 | 1.64 |
| Average Latency (ms) | 2.02 | 2.39 |
| Maximum Latency (ms) | 9.9 | 6.75 |
| 95th Percentile Latency (ms) | 2.22 | 3.07 |
MySQL Write-only
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 3,781.00 | 3,934.00 |
| Queries per second | 37,810.00 | 39,340.00 |
| Minimum Latency (ms) | 1.88 | 1.36 |
| Average Latency (ms) | 2.64 | 2.54 |
| Maximum Latency (ms) | 13.55 | 11.55 |
| 95th Percentile Latency (ms) | 3.55 | 3.62 |
MySQL Read/Write
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 1,808.00 | 1,636.00 |
| Queries per second | 18,080.00 | 16,360.00 |
| Minimum Latency (ms) | 4.32 | 3.75 |
| Average Latency (ms) | 5.53 | 6.11 |
| Maximum Latency (ms) | 105.61 | 17.57 |
| 95th Percentile Latency (ms) | 6.67 | 8.13 |
MySQL INSERT
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 5,179.00 | 6,379.00 |
| Queries per second | 51,790.00 | 63,790.00 |
| Minimum Latency (ms) | 1.23 | 0.97 |
| Average Latency (ms) | 1.93 | 1.56 |
| Maximum Latency (ms) | 76.05 | 6.98 |
| 95th Percentile Latency (ms) | 2.91 | 2.22 |
MySQL Bulk INSERT
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 931,337.00 | 603,677.00 |
| Queries per second | 9,313,370.00 | 6,036,770.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0.02 |
| Maximum Latency (ms) | 684.82 | 737.04 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 101,002.00 | 141,357.00 |
| Queries per second | 1,010,020.00 | 1,413,570.00 |
| Minimum Latency (ms) | 0.07 | 0.05 |
| Average Latency (ms) | 0.1 | 0.07 |
| Maximum Latency (ms) | 6.9 | 1.92 |
| 95th Percentile Latency (ms) | 0.14 | 0.11 |
MySQL SELECT (Random Points)
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 5,061.00 | 3,305.00 |
| Queries per second | 50,610.00 | 33,050.00 |
| Minimum Latency (ms) | 0.21 | 1.16 |
| Average Latency (ms) | 1.97 | 3.02 |
| Maximum Latency (ms) | 7.53 | 12.95 |
| 95th Percentile Latency (ms) | 2.61 | 4.25 |
MySQL SELECT (Random Ranges)
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 6,208.00 | 2,530.00 |
| Queries per second | 62,080.00 | 25,300.00 |
| Minimum Latency (ms) | 0.58 | 1.04 |
| Average Latency (ms) | 1.61 | 3.95 |
| Maximum Latency (ms) | 4.89 | 7.33 |
| 95th Percentile Latency (ms) | 2.07 | 5.47 |
MySQL UPDATE (Indexed)
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 5,746.00 | 5,724.00 |
| Queries per second | 57,460.00 | 57,240.00 |
| Minimum Latency (ms) | 1.14 | 0.91 |
| Average Latency (ms) | 1.74 | 1.74 |
| Maximum Latency (ms) | 108.49 | 6.21 |
| 95th Percentile Latency (ms) | 2.35 | 2.57 |
MySQL UPDATE (Non-Indexed)
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 5,723.00 | 6,368.00 |
| Queries per second | 57,230.00 | 63,680.00 |
| Minimum Latency (ms) | 1.2 | 0.86 |
| Average Latency (ms) | 1.75 | 1.57 |
| Maximum Latency (ms) | 52.39 | 13.64 |
| 95th Percentile Latency (ms) | 2.35 | 2.18 |
MySQL DELETE
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 34,076.00 | 45,880.00 |
| Queries per second | 340,760.00 | 458,800.00 |
| Minimum Latency (ms) | 0.07 | 0.05 |
| Average Latency (ms) | 0.29 | 0.22 |
| Maximum Latency (ms) | 44.14 | 6.41 |
| 95th Percentile Latency (ms) | 1.7 | 1.44 |
Redis
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| PING_INLINE per Second | 36,873.16 | 31,347.96 |
| PING_MBULK per Second | 39,062.50 | 31,084.86 |
| SET per Second | 37,650.61 | 27,739.25 |
| GET per Second | 37,327.36 | 27,548.21 |
| INCR per Second | 37,693.18 | 29,779.63 |
| LPUSH per Second | 36,153.29 | 27,693.16 |
| RPUSH per Second | 33,990.48 | 30,816.64 |
| LPOP per Second | 36,523.01 | 28,885.04 |
| RPOP per Second | 36,496.35 | 28,368.79 |
| SADD per Second | 36,913.99 | 31,756.11 |
| HSET per Second | 36,968.58 | 31,123.56 |
| SPOP per Second | 37,678.97 | 31,715.82 |
| ZADD per Second | 35,561.88 | 29,437.74 |
| ZPOPMIN per Second | 33,288.95 | 28,951.94 |
| LRANGE_100 (first 100 elements) per Second | 25,081.52 | 13,024.23 |
| LRANGE_300 (first 300 elements) per Second | 13,152.70 | 5,921.36 |
| LRANGE_500 (first 500 elements) per Second | 9,051.41 | 3,883.34 |
| LRANGE_600 (first 600 elements) per Second | 7,717.24 | 3,313.12 |
| MSET (10 keys) per Second | 34,867.50 | 25,000.00 |
Redis Average Latency (ms)
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| PING_INLINE | 0.92 | 1.02 |
| PING_MBULK | 0.87 | 1.02 |
| SET | 0.90 | 1.15 |
| GET | 0.91 | 1.14 |
| INCR | 0.90 | 1.07 |
| LPUSH | 0.94 | 1.15 |
| RPUSH | 1.02 | 1.04 |
| LPOP | 0.94 | 1.11 |
| RPOP | 0.94 | 1.13 |
| SADD | 0.93 | 1.01 |
| HSET | 0.93 | 1.03 |
| SPOP | 0.91 | 1.01 |
| ZADD | 0.96 | 1.09 |
| ZPOPMIN | 0.99 | 1.09 |
| LRANGE_100 (first 100 elements) | 1.36 | 2.66 |
| LRANGE_300 (first 300 elements) | 2.59 | 5.76 |
| LRANGE_500 (first 500 elements) | 3.79 | 8.42 |
| LRANGE_600 (first 600 elements) | 4.41 | 9.76 |
| MSET (10 keys) | 1.02 | 1.42 |
Conclusion
From the friendly robots:
In comparing the two Vultr instances, the Cloud Compute (1 GB) shows higher raw performance in most benchmarks, particularly in Redis operations, achieving up to 39,062.5 requests per second for inline pings and handling around 37,650.61 SET operations per second. The Cloud Compute (2 GB), however, features a more substantial RAM capacity and a slightly more advanced CPU model, resulting in more stable latency and better throughput in file I/O and memory operations. Given these metrics, the 1 GB instance excels in CPU-intensive, memory-bound workloads that can utilize a single core efficiently, whereas the 2 GB instance is more suited for tasks requiring higher RAM capacity and better file I/O performance, making it ideal for database-heavy and I/O-intensive 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.