Vultr Cloud Compute (1 GB) vs. Vultr Cloud Compute (2 GB)
New day, new benchmarks. Today I've spun up brand new instance from Vultr and ran my world famous suite of benchmarking scripts. Each instance was running Ubuntu 24.04 LTS x64 and all resided in or around the New York / New Jersey area. Without further ado, here's the results.
Overview
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Last Benchmarked | Tue, 28 Oct 2025 11:00:51 GMT | Tue, 28 Oct 2025 14:00:53 GMT |
| Linux Distro | Ubuntu 24.04 LTS x64 | Ubuntu 24.04 LTS x64 |
| Kernel Version | 6.8.0-79-generic | 6.8.0-79-generic |
| MySQL Version | 8.0.43-0ubuntu0.24.04.2 | 8.0.43-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,394.45 | 2,593.90 |
| CPU Cache Size (KB) | 16,384.00 | 16,384.00 |
| BogoMips | 4,788.90 | 5,187.80 |
| Events per Second | 615.53 | 1,106.75 |
| Minimum Latency (ms) | 0.88 | 0.88 |
| Average Latency (ms) | 1.62 | 0.9 |
| Maximum Latency (ms) | 5.49 | 4.04 |
| 95th Percentile Latency (ms) | 2.61 | 0.92 |
Memory
Memory Read
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Operations per second | 3,650,861.12 | 3,684,287.99 |
| Mebibytes per second | 3,565.29 | 3,597.94 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.86 | 0.21 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Operations per second | 3,964,071.36 | 3,705,042.78 |
| Mebibytes per second | 3,871.16 | 3,618.21 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.65 | 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,335.03 | 2,382.95 |
| Writes per Second | 890.02 | 1,588.63 |
| Fsyncs per Second | 2,849.25 | 5,090.01 |
| Read Mebibytes per Second | 20.86 | 37.23 |
| Written Mebibytes per Second | 13.91 | 24.82 |
| Minimum Latency (ms) | 0.01 | 0 |
| Average Latency (ms) | 0.2 | 0.11 |
| Maximum Latency (ms) | 12 | 7.37 |
| 95th Percentile Latency (ms) | 0.51 | 0.39 |
Mutex
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Minimum Latency (ms) | 2,016.43 | 1,602.96 |
| Average Latency (ms) | 2,026.59 | 1,608.90 |
| Maximum Latency (ms) | 2,036.58 | 1,616.06 |
| 95th Percentile Latency (ms) | 2,045.74 | 1,618.78 |
MySQL
MySQL Read-only
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 4,681.00 | 5,561.00 |
| Queries per second | 46,810.00 | 55,610.00 |
| Minimum Latency (ms) | 1.57 | 1.65 |
| Average Latency (ms) | 2.13 | 1.8 |
| Maximum Latency (ms) | 22.59 | 4.57 |
| 95th Percentile Latency (ms) | 3.75 | 2 |
MySQL Write-only
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 2,680.00 | 5,144.00 |
| Queries per second | 26,800.00 | 51,440.00 |
| Minimum Latency (ms) | 1.66 | 1.31 |
| Average Latency (ms) | 3.73 | 1.94 |
| Maximum Latency (ms) | 34.94 | 21.1 |
| 95th Percentile Latency (ms) | 6.67 | 2.76 |
MySQL Read/Write
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 1,752.00 | 2,409.00 |
| Queries per second | 17,520.00 | 24,090.00 |
| Minimum Latency (ms) | 4.22 | 3.3 |
| Average Latency (ms) | 5.71 | 4.15 |
| Maximum Latency (ms) | 16.45 | 8.93 |
| 95th Percentile Latency (ms) | 8.28 | 5.18 |
MySQL INSERT
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 4,351.00 | 8,491.00 |
| Queries per second | 43,510.00 | 84,910.00 |
| Minimum Latency (ms) | 1.34 | 0.74 |
| Average Latency (ms) | 2.29 | 1.17 |
| Maximum Latency (ms) | 26.21 | 5.61 |
| 95th Percentile Latency (ms) | 3.36 | 1.52 |
MySQL Bulk INSERT
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 865,805.00 | 800,273.00 |
| Queries per second | 8,658,050.00 | 8,002,730.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0.01 |
| Maximum Latency (ms) | 955.84 | 625.59 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 105,481.00 | 173,636.00 |
| Queries per second | 1,054,810.00 | 1,736,360.00 |
| Minimum Latency (ms) | 0.06 | 0.05 |
| Average Latency (ms) | 0.09 | 0.06 |
| Maximum Latency (ms) | 9.22 | 1.37 |
| 95th Percentile Latency (ms) | 0.16 | 0.08 |
MySQL SELECT (Random Points)
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 3,665.00 | 3,981.00 |
| Queries per second | 36,650.00 | 39,810.00 |
| Minimum Latency (ms) | 0.5 | 0.57 |
| Average Latency (ms) | 2.73 | 2.51 |
| Maximum Latency (ms) | 13.84 | 6.85 |
| 95th Percentile Latency (ms) | 5 | 3.25 |
MySQL SELECT (Random Ranges)
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 5,236.00 | 2,610.00 |
| Queries per second | 52,360.00 | 26,100.00 |
| Minimum Latency (ms) | 0.72 | 1.02 |
| Average Latency (ms) | 1.91 | 3.83 |
| Maximum Latency (ms) | 10.33 | 7.55 |
| 95th Percentile Latency (ms) | 2.76 | 5.09 |
MySQL UPDATE (Indexed)
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 4,511.00 | 8,203.00 |
| Queries per second | 45,110.00 | 82,030.00 |
| Minimum Latency (ms) | 1.26 | 0.73 |
| Average Latency (ms) | 2.21 | 1.22 |
| Maximum Latency (ms) | 14.93 | 5.65 |
| 95th Percentile Latency (ms) | 3.55 | 1.7 |
MySQL UPDATE (Non-Indexed)
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 5,148.00 | 8,491.00 |
| Queries per second | 51,480.00 | 84,910.00 |
| Minimum Latency (ms) | 1.25 | 0.73 |
| Average Latency (ms) | 1.94 | 1.18 |
| Maximum Latency (ms) | 19.95 | 5.79 |
| 95th Percentile Latency (ms) | 2.81 | 1.52 |
MySQL DELETE
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 19,636.00 | 70,550.00 |
| Queries per second | 196,360.00 | 705,500.00 |
| Minimum Latency (ms) | 0.08 | 0.05 |
| Average Latency (ms) | 0.51 | 0.14 |
| Maximum Latency (ms) | 33.94 | 5.94 |
| 95th Percentile Latency (ms) | 2.48 | 0.95 |
Redis
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| PING_INLINE per Second | 34,270.05 | 39,261.88 |
| PING_MBULK per Second | 34,638.03 | 39,603.96 |
| SET per Second | 35,211.27 | 38,654.81 |
| GET per Second | 34,977.27 | 39,323.63 |
| INCR per Second | 34,965.04 | 39,077.77 |
| LPUSH per Second | 36,443.15 | 37,174.72 |
| RPUSH per Second | 33,898.30 | 38,182.51 |
| LPOP per Second | 35,855.14 | 37,160.91 |
| RPOP per Second | 34,831.07 | 37,023.32 |
| SADD per Second | 35,829.45 | 38,595.14 |
| HSET per Second | 34,977.27 | 35,273.37 |
| SPOP per Second | 34,423.41 | 31,836.99 |
| ZADD per Second | 35,174.11 | 31,897.93 |
| ZPOPMIN per Second | 35,410.77 | 37,411.15 |
| LRANGE_100 (first 100 elements) per Second | 23,364.48 | 16,268.10 |
| LRANGE_300 (first 300 elements) per Second | 12,325.90 | 7,280.67 |
| LRANGE_500 (first 500 elements) per Second | 8,369.60 | 4,586.10 |
| LRANGE_600 (first 600 elements) per Second | 7,555.15 | 3,546.23 |
| MSET (10 keys) per Second | 33,123.55 | 25,641.03 |
Redis Average Latency (ms)
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| PING_INLINE | 0.96 | 0.84 |
| PING_MBULK | 0.92 | 0.83 |
| SET | 0.93 | 0.86 |
| GET | 0.94 | 0.84 |
| INCR | 0.92 | 0.85 |
| LPUSH | 0.92 | 0.89 |
| RPUSH | 0.95 | 0.87 |
| LPOP | 0.93 | 0.90 |
| RPOP | 0.93 | 0.90 |
| SADD | 0.92 | 0.86 |
| HSET | 0.93 | 0.93 |
| SPOP | 0.94 | 1.00 |
| ZADD | 0.93 | 1.03 |
| ZPOPMIN | 0.92 | 0.87 |
| LRANGE_100 (first 100 elements) | 1.43 | 2.16 |
| LRANGE_300 (first 300 elements) | 2.77 | 4.74 |
| LRANGE_500 (first 500 elements) | 4.07 | 7.37 |
| LRANGE_600 (first 600 elements) | 4.48 | 9.22 |
| MSET (10 keys) | 1.03 | 1.41 |
Conclusion
From the friendly robots:
The Vultr Cloud Compute (1 GB) instance shows strong performance in Redis operations, with high request rates and low latencies, making it suitable for applications requiring high throughput and low latency, such as caching services. However, it struggles with more complex Redis commands like LRANGE, which involve larger data sets, resulting in significantly higher latencies. The Vultr Cloud Compute (2 GB) instance, while also performing well in Redis operations, offers slightly better throughput and lower latencies overall, indicating it might be more suitable for applications that require a balance between memory capacity and performance, especially for workloads that involve more complex data handling like larger LRANGE operations. Both instances are suitable for general-purpose tasks with the 2 GB instance providing a slight edge in memory-intensive and complex data operations.
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.