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 to run some benchmarks on. Each instance was running Ubuntu 24.04 LTS x64 and were created 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 | Tue, 23 Dec 2025 19:00:51 GMT | Wed, 24 Dec 2025 12: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.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 (Broadwell, 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 | 774.49 | 1,050.43 |
| Minimum Latency (ms) | 1.13 | 0.88 |
| Average Latency (ms) | 1.29 | 0.95 |
| Maximum Latency (ms) | 3.64 | 3.72 |
| 95th Percentile Latency (ms) | 1.55 | 1.12 |
Memory
Memory Read
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Operations per second | 3,563,144.39 | 3,627,786.39 |
| Mebibytes per second | 3,479.63 | 3,542.76 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 2.33 | 0.9 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Operations per second | 3,578,279.14 | 3,646,841.25 |
| Mebibytes per second | 3,494.41 | 3,561.37 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 1.36 | 0.68 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Reads per Second | 1,893.29 | 2,098.11 |
| Writes per Second | 1,262.20 | 1,398.74 |
| Fsyncs per Second | 4,041.52 | 4,481.35 |
| Read Mebibytes per Second | 29.58 | 32.78 |
| Written Mebibytes per Second | 19.72 | 21.86 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.14 | 0.12 |
| Maximum Latency (ms) | 7.93 | 6.23 |
| 95th Percentile Latency (ms) | 0.35 | 0.46 |
Mutex
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Minimum Latency (ms) | 2,405.08 | 1,865.77 |
| Average Latency (ms) | 2,423.84 | 1,883.50 |
| Maximum Latency (ms) | 2,436.20 | 1,894.82 |
| 95th Percentile Latency (ms) | 2,449.36 | 1,903.57 |
MySQL
MySQL Read-only
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 4,627.00 | 5,460.00 |
| Queries per second | 46,270.00 | 54,600.00 |
| Minimum Latency (ms) | 1.69 | 1.62 |
| Average Latency (ms) | 2.16 | 1.83 |
| Maximum Latency (ms) | 14.35 | 3.96 |
| 95th Percentile Latency (ms) | 3.13 | 2.11 |
MySQL Write-only
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 3,192.00 | 4,669.00 |
| Queries per second | 31,920.00 | 46,690.00 |
| Minimum Latency (ms) | 1.88 | 1.31 |
| Average Latency (ms) | 3.13 | 2.14 |
| Maximum Latency (ms) | 32.5 | 17.73 |
| 95th Percentile Latency (ms) | 4.57 | 3.07 |
MySQL Read/Write
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 1,733.00 | 2,204.00 |
| Queries per second | 17,330.00 | 22,040.00 |
| Minimum Latency (ms) | 3.98 | 3.41 |
| Average Latency (ms) | 5.77 | 4.53 |
| Maximum Latency (ms) | 15.77 | 27.49 |
| 95th Percentile Latency (ms) | 8.28 | 5.77 |
MySQL INSERT
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 5,038.00 | 7,861.00 |
| Queries per second | 50,380.00 | 78,610.00 |
| Minimum Latency (ms) | 1.29 | 0.73 |
| Average Latency (ms) | 1.98 | 1.27 |
| Maximum Latency (ms) | 20.82 | 19.26 |
| 95th Percentile Latency (ms) | 2.76 | 1.64 |
MySQL Bulk INSERT
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 800,273.00 | 767,507.00 |
| Queries per second | 8,002,730.00 | 7,675,070.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0.01 |
| Maximum Latency (ms) | 783.86 | 616.91 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 100,060.00 | 158,145.00 |
| Queries per second | 1,000,600.00 | 1,581,450.00 |
| Minimum Latency (ms) | 0.07 | 0.05 |
| Average Latency (ms) | 0.1 | 0.06 |
| Maximum Latency (ms) | 9.15 | 2.17 |
| 95th Percentile Latency (ms) | 0.15 | 0.09 |
MySQL SELECT (Random Points)
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 4,470.00 | 3,906.00 |
| Queries per second | 44,700.00 | 39,060.00 |
| Minimum Latency (ms) | 0.68 | 0.91 |
| Average Latency (ms) | 2.23 | 2.56 |
| Maximum Latency (ms) | 9.2 | 5.84 |
| 95th Percentile Latency (ms) | 3.55 | 3.3 |
MySQL SELECT (Random Ranges)
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 4,738.00 | 2,569.00 |
| Queries per second | 47,380.00 | 25,690.00 |
| Minimum Latency (ms) | 0.65 | 1.14 |
| Average Latency (ms) | 2.11 | 3.89 |
| Maximum Latency (ms) | 8.72 | 10.84 |
| 95th Percentile Latency (ms) | 3.68 | 5.28 |
MySQL UPDATE (Indexed)
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 4,344.00 | 7,455.00 |
| Queries per second | 43,440.00 | 74,550.00 |
| Minimum Latency (ms) | 1.12 | 0.73 |
| Average Latency (ms) | 2.3 | 1.34 |
| Maximum Latency (ms) | 37 | 14.86 |
| 95th Percentile Latency (ms) | 3.96 | 1.96 |
MySQL UPDATE (Non-Indexed)
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 5,409.00 | 7,916.00 |
| Queries per second | 54,090.00 | 79,160.00 |
| Minimum Latency (ms) | 1.08 | 0.73 |
| Average Latency (ms) | 1.85 | 1.26 |
| Maximum Latency (ms) | 13.01 | 7.69 |
| 95th Percentile Latency (ms) | 2.52 | 1.67 |
MySQL DELETE
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 34,310.00 | 65,321.00 |
| Queries per second | 343,100.00 | 653,210.00 |
| Minimum Latency (ms) | 0.07 | 0.05 |
| Average Latency (ms) | 0.29 | 0.15 |
| Maximum Latency (ms) | 6.95 | 19.46 |
| 95th Percentile Latency (ms) | 1.82 | 1.04 |
Redis
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| PING_INLINE per Second | 33,670.04 | 36,616.62 |
| PING_MBULK per Second | 32,948.93 | 35,161.74 |
| SET per Second | 32,829.94 | 34,770.52 |
| GET per Second | 34,411.56 | 36,140.22 |
| INCR per Second | 36,258.16 | 37,257.82 |
| LPUSH per Second | 32,435.94 | 35,063.11 |
| RPUSH per Second | 34,891.84 | 35,186.49 |
| LPOP per Second | 31,938.68 | 35,423.31 |
| RPOP per Second | 31,605.56 | 35,174.11 |
| SADD per Second | 32,679.74 | 36,231.88 |
| HSET per Second | 33,840.95 | 34,843.21 |
| SPOP per Second | 34,411.56 | 37,119.52 |
| ZADD per Second | 34,542.32 | 35,688.79 |
| ZPOPMIN per Second | 34,176.35 | 37,864.45 |
| LRANGE_100 (first 100 elements) per Second | 22,084.81 | 15,936.25 |
| LRANGE_300 (first 300 elements) per Second | 10,593.22 | 7,041.76 |
| LRANGE_500 (first 500 elements) per Second | 7,519.93 | 4,604.05 |
| LRANGE_600 (first 600 elements) per Second | 5,956.28 | 3,975.19 |
| MSET (10 keys) per Second | 29,594.55 | 28,694.41 |
Redis Average Latency (ms)
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| PING_INLINE | 0.97 | 0.89 |
| PING_MBULK | 0.98 | 0.91 |
| SET | 0.99 | 0.93 |
| GET | 0.95 | 0.90 |
| INCR | 0.91 | 0.87 |
| LPUSH | 1.01 | 0.93 |
| RPUSH | 0.95 | 0.92 |
| LPOP | 1.04 | 0.92 |
| RPOP | 1.04 | 0.93 |
| SADD | 1.00 | 0.90 |
| HSET | 0.98 | 0.94 |
| SPOP | 0.95 | 0.88 |
| ZADD | 0.96 | 0.93 |
| ZPOPMIN | 0.96 | 0.87 |
| LRANGE_100 (first 100 elements) | 1.53 | 2.19 |
| LRANGE_300 (first 300 elements) | 3.20 | 4.85 |
| LRANGE_500 (first 500 elements) | 4.53 | 7.34 |
| LRANGE_600 (first 600 elements) | 5.63 | 8.26 |
| MSET (10 keys) | 1.17 | 1.24 |
Conclusion
From the friendly robots:
Comparing the Vultr Cloud Compute instances, the 1 GB model shows decent performance with high Redis request rates up to 36,258 requests per second and efficient CPU operations, but struggles with larger Redis data sets, experiencing significant latency spikes for commands like LRANGE. It also shows reasonable file I/O and memory handling speeds, though it lags slightly behind the 2 GB model in these metrics. The 2 GB instance outperforms the 1 GB model across all benchmarks with notably higher Redis request rates, better CPU event processing, and improved file I/O and memory handling, although it still shows some latency in handling large data sets and more substantial variance in thread latencies. Ideal use cases for the 1 GB model include lightweight web applications or low-traffic services, while the 2 GB instance is suited for more demanding workloads such as high-traffic web applications or database-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.