Vultr Cloud Compute (1 GB) vs. Vultr Cloud Compute (2 GB, 2 Cores)
Fresh benchmarks coming at ya. Today I've spun up some brand new instance from Vultr and ran some benchmarks. Each instance was running Ubuntu 24.04 LTS x64 and were created 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, 2 Cores) | |
|---|---|---|
| Last Benchmarked | Tue, 12 May 2026 18:00:51 GMT | Mon, 11 May 2026 04:00:52 GMT |
| Linux Distro | Ubuntu 24.04 LTS x64 | Ubuntu 24.04 LTS x64 |
| Kernel Version | 6.8.0-111-generic | 6.8.0-111-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 | $15.00 |
| RAM (GB) | 1 | 2 |
| CPU Cores | 1 | 2 |
| Storage (TB) | 25 | 65 |
| Storage Type | SSD | SSD |
| Transfer (TB) | 1 | 3 |
CPU
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Vendor | GenuineIntel | GenuineIntel |
| Model Name | Intel Core Processor (Broadwell, no TSX, IBRS) | Intel Core Processor (Skylake, IBRS, no TSX) |
| Clock Speed (MHz) | 2,394.45 | 3,792.00 |
| CPU Cache Size (KB) | 16,384.00 | 16,384.00 |
| BogoMips | 4,788.90 | 7,583.99 |
| Events per Second | 795.66 | 1,481.60 |
| Minimum Latency (ms) | 1.14 | 0.63 |
| Average Latency (ms) | 1.26 | 0.67 |
| Maximum Latency (ms) | 3.9 | 1.95 |
| 95th Percentile Latency (ms) | 1.47 | 0.77 |
Memory
Memory Read
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 3,786,617.05 | 6,401,389.08 |
| Mebibytes per second | 3,697.87 | 6,251.36 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.43 | 0.23 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 3,766,621.58 | 6,411,085.35 |
| Mebibytes per second | 3,678.34 | 6,260.83 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.78 | 0.18 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Reads per Second | 1,908.38 | 4,345.71 |
| Writes per Second | 1,272.25 | 2,897.07 |
| Fsyncs per Second | 4,078.88 | 9,273.19 |
| Read Mebibytes per Second | 29.82 | 67.90 |
| Written Mebibytes per Second | 19.88 | 45.27 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.14 | 0.06 |
| Maximum Latency (ms) | 16.36 | 2.92 |
| 95th Percentile Latency (ms) | 0.39 | 0.17 |
Mutex
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 2,335.65 | 214.63 |
| Average Latency (ms) | 2,349.86 | 569.72 |
| Maximum Latency (ms) | 2,365.31 | 636.55 |
| 95th Percentile Latency (ms) | 2,362.72 | 634.66 |
MySQL
MySQL Read-only
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 4,483.00 | 8,015.00 |
| Queries per second | 44,830.00 | 80,150.00 |
| Minimum Latency (ms) | 1.78 | 0.92 |
| Average Latency (ms) | 2.23 | 1.25 |
| Maximum Latency (ms) | 49.32 | 5.5 |
| 95th Percentile Latency (ms) | 2.71 | 1.86 |
MySQL Write-only
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 3,919.00 | 8,497.00 |
| Queries per second | 39,190.00 | 84,970.00 |
| Minimum Latency (ms) | 1.68 | 0.76 |
| Average Latency (ms) | 2.55 | 1.17 |
| Maximum Latency (ms) | 27.43 | 3.04 |
| 95th Percentile Latency (ms) | 3.62 | 1.55 |
MySQL Read/Write
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 1,790.00 | 3,726.00 |
| Queries per second | 17,900.00 | 37,260.00 |
| Minimum Latency (ms) | 4.06 | 1.78 |
| Average Latency (ms) | 5.58 | 2.68 |
| Maximum Latency (ms) | 44.16 | 5.82 |
| 95th Percentile Latency (ms) | 7.98 | 3.43 |
MySQL INSERT
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 6,614.00 | 15,028.00 |
| Queries per second | 66,140.00 | 150,280.00 |
| Minimum Latency (ms) | 0.91 | 0.41 |
| Average Latency (ms) | 1.51 | 0.66 |
| Maximum Latency (ms) | 14.16 | 2.42 |
| 95th Percentile Latency (ms) | 2.07 | 0.86 |
MySQL Bulk INSERT
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 865,805.00 | 1,696,217.00 |
| Queries per second | 8,658,050.00 | 16,962,170.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0.01 |
| Maximum Latency (ms) | 627.7 | 283.37 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 102,465.00 | 201,989.00 |
| Queries per second | 1,024,650.00 | 2,019,890.00 |
| Minimum Latency (ms) | 0.07 | 0.03 |
| Average Latency (ms) | 0.1 | 0.05 |
| Maximum Latency (ms) | 9.98 | 0.51 |
| 95th Percentile Latency (ms) | 0.14 | 0.07 |
MySQL SELECT (Random Points)
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 4,521.00 | 8,025.00 |
| Queries per second | 45,210.00 | 80,250.00 |
| Minimum Latency (ms) | 0.73 | 0.35 |
| Average Latency (ms) | 2.21 | 1.24 |
| Maximum Latency (ms) | 6.91 | 3.55 |
| 95th Percentile Latency (ms) | 3.07 | 2.07 |
MySQL SELECT (Random Ranges)
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 5,358.00 | 8,336.00 |
| Queries per second | 53,580.00 | 83,360.00 |
| Minimum Latency (ms) | 0.66 | 0.4 |
| Average Latency (ms) | 1.86 | 1.2 |
| Maximum Latency (ms) | 8.79 | 4.25 |
| 95th Percentile Latency (ms) | 2.57 | 2.22 |
MySQL UPDATE (Indexed)
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 6,182.00 | 13,858.00 |
| Queries per second | 61,820.00 | 138,580.00 |
| Minimum Latency (ms) | 0.94 | 0.42 |
| Average Latency (ms) | 1.62 | 0.72 |
| Maximum Latency (ms) | 35.17 | 6.33 |
| 95th Percentile Latency (ms) | 2.35 | 0.95 |
MySQL UPDATE (Non-Indexed)
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 6,753.00 | 14,587.00 |
| Queries per second | 67,530.00 | 145,870.00 |
| Minimum Latency (ms) | 0.93 | 0.4 |
| Average Latency (ms) | 1.48 | 0.68 |
| Maximum Latency (ms) | 10.15 | 11.69 |
| 95th Percentile Latency (ms) | 1.93 | 0.9 |
MySQL DELETE
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 35,322.00 | 129,013.00 |
| Queries per second | 353,220.00 | 1,290,130.00 |
| Minimum Latency (ms) | 0.07 | 0.03 |
| Average Latency (ms) | 0.28 | 0.08 |
| Maximum Latency (ms) | 21.31 | 2.61 |
| 95th Percentile Latency (ms) | 1.55 | 0.09 |
Redis
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE per Second | 27,925.16 | 78,247.26 |
| PING_MBULK per Second | 30,590.39 | 74,738.41 |
| SET per Second | 24,740.23 | 77,041.60 |
| GET per Second | 29,095.14 | 83,333.33 |
| INCR per Second | 31,645.57 | 80,971.66 |
| LPUSH per Second | 31,685.68 | 79,113.92 |
| RPUSH per Second | 31,505.99 | 77,160.49 |
| LPOP per Second | 30,609.12 | 81,499.59 |
| RPOP per Second | 29,394.47 | 82,440.23 |
| SADD per Second | 31,357.79 | 80,192.46 |
| HSET per Second | 29,489.83 | 83,612.04 |
| SPOP per Second | 29,027.58 | 85,034.02 |
| ZADD per Second | 29,010.73 | 83,263.95 |
| ZPOPMIN per Second | 28,968.71 | 82,987.55 |
| LRANGE_100 (first 100 elements) per Second | 19,040.37 | 55,555.56 |
| LRANGE_300 (first 300 elements) per Second | 10,432.97 | 28,851.70 |
| LRANGE_500 (first 500 elements) per Second | 7,370.83 | 19,391.12 |
| LRANGE_600 (first 600 elements) per Second | 6,899.41 | 17,211.71 |
| MSET (10 keys) per Second | 31,705.77 | 80,256.82 |
Redis Average Latency (ms)
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE | 1.14 | 0.34 |
| PING_MBULK | 1.04 | 0.35 |
| SET | 1.31 | 0.34 |
| GET | 1.14 | 0.32 |
| INCR | 1.03 | 0.32 |
| LPUSH | 1.02 | 0.34 |
| RPUSH | 1.02 | 0.34 |
| LPOP | 1.06 | 0.32 |
| RPOP | 1.09 | 0.32 |
| SADD | 1.03 | 0.32 |
| HSET | 1.09 | 0.31 |
| SPOP | 1.09 | 0.30 |
| ZADD | 1.11 | 0.31 |
| ZPOPMIN | 1.10 | 0.31 |
| LRANGE_100 (first 100 elements) | 1.76 | 0.54 |
| LRANGE_300 (first 300 elements) | 3.27 | 1.11 |
| LRANGE_500 (first 500 elements) | 4.54 | 1.62 |
| LRANGE_600 (first 600 elements) | 4.86 | 1.84 |
| MSET (10 keys) | 1.09 | 0.38 |
Conclusion
From the friendly robots:
Analyzing the benchmark performance of both Vultr instances, it's evident that the Cloud Compute (2 GB, 2 Cores) instance significantly outperforms the Cloud Compute (1 GB) in terms of multi-core processing, memory operations, and overall throughput. The 2 GB instance demonstrates superior Redis performance with higher requests per second and lower latencies across a variety of operations, along with substantially better CPU, file I/O, and MySQL performance metrics. While the 1 GB instance shows decent performance for lower-resource applications, the 2 GB instance is ideal for CPU-intensive, I/O-heavy, and multi-threaded workloads due to its enhanced processing power and memory capabilities. Thus, for applications requiring high concurrency and throughput, the 2 GB instance is the better choice.
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.