Vultr Cloud Compute (1 GB) vs. Vultr Cloud Compute (2 GB)
My friend, I'm so glad you're here! Today I've spun up brand new instance from Vultr and ran my world famous suite of benchmarking scripts. Each instance was spun up with Ubuntu 24.04 LTS x64 and were created in the New York area (or close to it). Let's get into the numbers.
Overview
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Last Benchmarked | Mon, 09 Feb 2026 01:00:52 GMT | Mon, 09 Feb 2026 04:00:52 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.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.94 |
| CPU Cache Size (KB) | 16,384.00 | 16,384.00 |
| BogoMips | 4,799.99 | 5,187.88 |
| Events per Second | 815.39 | 1,074.97 |
| Minimum Latency (ms) | 1.05 | 0.88 |
| Average Latency (ms) | 1.23 | 0.93 |
| Maximum Latency (ms) | 6.35 | 3.44 |
| 95th Percentile Latency (ms) | 1.32 | 1.06 |
Memory
Memory Read
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Operations per second | 4,056,132.83 | 3,538,923.30 |
| Mebibytes per second | 3,961.07 | 3,455.98 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.93 | 0.31 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Operations per second | 4,076,721.57 | 3,652,500.05 |
| Mebibytes per second | 3,981.17 | 3,566.89 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.43 | 0.68 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Reads per Second | 2,257.57 | 3,018.07 |
| Writes per Second | 1,505.05 | 2,011.98 |
| Fsyncs per Second | 4,819.34 | 6,445.37 |
| Read Mebibytes per Second | 35.27 | 47.16 |
| Written Mebibytes per Second | 23.52 | 31.44 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.12 | 0.09 |
| Maximum Latency (ms) | 6.11 | 63.4 |
| 95th Percentile Latency (ms) | 0.29 | 0.23 |
Mutex
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Minimum Latency (ms) | 2,065.69 | 1,618.94 |
| Average Latency (ms) | 2,071.23 | 1,624.95 |
| Maximum Latency (ms) | 2,077.58 | 1,633.36 |
| 95th Percentile Latency (ms) | 2,082.91 | 1,618.78 |
MySQL
MySQL Read-only
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 4,753.00 | 5,645.00 |
| Queries per second | 47,530.00 | 56,450.00 |
| Minimum Latency (ms) | 1.8 | 1.63 |
| Average Latency (ms) | 2.1 | 1.77 |
| Maximum Latency (ms) | 8.07 | 3.8 |
| 95th Percentile Latency (ms) | 2.26 | 1.93 |
MySQL Write-only
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 3,987.00 | 4,767.00 |
| Queries per second | 39,870.00 | 47,670.00 |
| Minimum Latency (ms) | 1.81 | 1.25 |
| Average Latency (ms) | 2.51 | 2.09 |
| Maximum Latency (ms) | 26.15 | 63.65 |
| 95th Percentile Latency (ms) | 3.49 | 2.91 |
MySQL Read/Write
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 1,915.00 | 2,354.00 |
| Queries per second | 19,150.00 | 23,540.00 |
| Minimum Latency (ms) | 4.2 | 3.35 |
| Average Latency (ms) | 5.22 | 4.24 |
| Maximum Latency (ms) | 15.46 | 20.64 |
| 95th Percentile Latency (ms) | 6.79 | 5.37 |
MySQL INSERT
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 6,283.00 | 9,769.00 |
| Queries per second | 62,830.00 | 97,690.00 |
| Minimum Latency (ms) | 1.15 | 0.65 |
| Average Latency (ms) | 1.59 | 1.02 |
| Maximum Latency (ms) | 7.36 | 8.05 |
| 95th Percentile Latency (ms) | 2.14 | 1.23 |
MySQL Bulk INSERT
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 898,571.00 | 800,273.00 |
| Queries per second | 8,985,710.00 | 8,002,730.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0.01 |
| Maximum Latency (ms) | 643.07 | 569.83 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 102,823.00 | 161,980.00 |
| Queries per second | 1,028,230.00 | 1,619,800.00 |
| Minimum Latency (ms) | 0.07 | 0.05 |
| Average Latency (ms) | 0.1 | 0.06 |
| Maximum Latency (ms) | 8.25 | 7.95 |
| 95th Percentile Latency (ms) | 0.13 | 0.08 |
MySQL SELECT (Random Points)
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 4,999.00 | 3,645.00 |
| Queries per second | 49,990.00 | 36,450.00 |
| Minimum Latency (ms) | 0.65 | 0.96 |
| Average Latency (ms) | 2 | 2.74 |
| Maximum Latency (ms) | 7.7 | 7.03 |
| 95th Percentile Latency (ms) | 2.61 | 3.62 |
MySQL SELECT (Random Ranges)
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 6,142.00 | 2,596.00 |
| Queries per second | 61,420.00 | 25,960.00 |
| Minimum Latency (ms) | 0.5 | 1.04 |
| Average Latency (ms) | 1.63 | 3.85 |
| Maximum Latency (ms) | 4.51 | 8.08 |
| 95th Percentile Latency (ms) | 2.11 | 5.18 |
MySQL UPDATE (Indexed)
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 6,108.00 | 9,126.00 |
| Queries per second | 61,080.00 | 91,260.00 |
| Minimum Latency (ms) | 0.99 | 0.67 |
| Average Latency (ms) | 1.64 | 1.09 |
| Maximum Latency (ms) | 7.27 | 14.15 |
| 95th Percentile Latency (ms) | 2.3 | 1.47 |
MySQL UPDATE (Non-Indexed)
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 6,551.00 | 8,310.00 |
| Queries per second | 65,510.00 | 83,100.00 |
| Minimum Latency (ms) | 0.98 | 0.68 |
| Average Latency (ms) | 1.53 | 1.2 |
| Maximum Latency (ms) | 7.05 | 30.89 |
| 95th Percentile Latency (ms) | 1.96 | 1.42 |
MySQL DELETE
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 40,352.00 | 80,792.00 |
| Queries per second | 403,520.00 | 807,920.00 |
| Minimum Latency (ms) | 0.07 | 0.05 |
| Average Latency (ms) | 0.25 | 0.12 |
| Maximum Latency (ms) | 11.03 | 9.12 |
| 95th Percentile Latency (ms) | 1.5 | 0.32 |
Redis
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| PING_INLINE per Second | 37,622.27 | 37,608.12 |
| PING_MBULK per Second | 38,008.36 | 38,008.36 |
| SET per Second | 38,138.82 | 35,599.86 |
| GET per Second | 38,022.81 | 37,078.23 |
| INCR per Second | 37,864.45 | 37,313.43 |
| LPUSH per Second | 37,850.11 | 36,549.71 |
| RPUSH per Second | 36,724.20 | 37,299.52 |
| LPOP per Second | 37,064.49 | 35,855.14 |
| RPOP per Second | 37,133.31 | 36,886.76 |
| SADD per Second | 38,270.19 | 36,258.16 |
| HSET per Second | 38,153.38 | 36,101.08 |
| SPOP per Second | 38,343.56 | 37,636.43 |
| ZADD per Second | 37,383.18 | 34,965.04 |
| ZPOPMIN per Second | 36,656.89 | 36,416.61 |
| LRANGE_100 (first 100 elements) per Second | 22,660.32 | 15,880.58 |
| LRANGE_300 (first 300 elements) per Second | 12,860.08 | 7,292.88 |
| LRANGE_500 (first 500 elements) per Second | 8,591.07 | 4,703.67 |
| LRANGE_600 (first 600 elements) per Second | 7,468.82 | 3,975.04 |
| MSET (10 keys) per Second | 33,955.86 | 27,716.19 |
Redis Average Latency (ms)
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| PING_INLINE | 0.88 | 0.88 |
| PING_MBULK | 0.87 | 0.86 |
| SET | 0.88 | 0.93 |
| GET | 0.88 | 0.89 |
| INCR | 0.88 | 0.88 |
| LPUSH | 0.89 | 0.90 |
| RPUSH | 0.91 | 0.89 |
| LPOP | 0.91 | 0.93 |
| RPOP | 0.91 | 0.90 |
| SADD | 0.87 | 0.91 |
| HSET | 0.88 | 0.92 |
| SPOP | 0.87 | 0.87 |
| ZADD | 0.90 | 0.95 |
| ZPOPMIN | 0.90 | 0.90 |
| LRANGE_100 (first 100 elements) | 1.48 | 2.22 |
| LRANGE_300 (first 300 elements) | 2.64 | 4.74 |
| LRANGE_500 (first 500 elements) | 3.96 | 7.23 |
| LRANGE_600 (first 600 elements) | 4.53 | 8.25 |
| MSET (10 keys) | 1.04 | 1.29 |
Conclusion
From the friendly robots:
The Vultr Cloud Compute (1 GB) instance shows impressive performance for basic Redis operations, achieving up to 36,819 requests per second for PING_MBULK and maintaining relatively low latencies across various operations, despite its single CPU core and 1 GB of RAM. In contrast, the Cloud Compute (2 GB) instance, though also performing admirably, shows slightly lower Redis performance metrics but demonstrates better throughput in CPU operations, file I/O, and memory operations, likely due to its slightly more advanced CPU model and double the RAM. Ideal use cases for the 1 GB instance might include lightweight web applications or services requiring frequent Redis interactions, while the 2 GB instance would be better suited for more resource-intensive applications, including those needing higher CPU and memory capacity for complex computations or data processing 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.