Vultr Cloud Compute (1 GB) vs. Vultr Cloud Compute (2 GB)
New day, new benchmarks. Today I've spun up some brand new instance from Vultr and ran my world famous suite of benchmarking scripts. 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, 09 Jun 2026 16:00:52 GMT | Mon, 08 Jun 2026 13:00:52 GMT |
| Linux Distro | Ubuntu 24.04 LTS x64 | Ubuntu 24.04 LTS x64 |
| Kernel Version | 6.8.0-124-generic | 6.8.0-124-generic |
| MySQL Version | 8.0.46-0ubuntu0.24.04.2 | 8.0.46-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 | 818.79 | 865.41 |
| Minimum Latency (ms) | 1.02 | 0.89 |
| Average Latency (ms) | 1.22 | 1.15 |
| Maximum Latency (ms) | 4.29 | 4.98 |
| 95th Percentile Latency (ms) | 1.37 | 1.37 |
Memory
Memory Read
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Operations per second | 4,016,644.99 | 3,459,843.17 |
| Mebibytes per second | 3,922.50 | 3,378.75 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.24 | 2.32 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Operations per second | 3,983,147.38 | 3,496,594.92 |
| Mebibytes per second | 3,889.79 | 3,414.64 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.35 | 1.05 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Reads per Second | 2,012.81 | 2,228.25 |
| Writes per Second | 1,341.84 | 1,485.43 |
| Fsyncs per Second | 4,294.21 | 4,754.03 |
| Read Mebibytes per Second | 31.45 | 34.82 |
| Written Mebibytes per Second | 20.97 | 23.21 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.13 | 0.12 |
| Maximum Latency (ms) | 5.76 | 13.44 |
| 95th Percentile Latency (ms) | 0.35 | 0.32 |
Mutex
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Minimum Latency (ms) | 2,100.95 | 2,228.36 |
| Average Latency (ms) | 2,112.04 | 2,256.09 |
| Maximum Latency (ms) | 2,121.79 | 2,280.06 |
| 95th Percentile Latency (ms) | 2,120.76 | 2,279.14 |
MySQL
MySQL Read-only
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 5,273.00 | 3,894.00 |
| Queries per second | 52,730.00 | 38,940.00 |
| Minimum Latency (ms) | 1.65 | 1.34 |
| Average Latency (ms) | 1.89 | 2.56 |
| Maximum Latency (ms) | 13.42 | 6.72 |
| 95th Percentile Latency (ms) | 2.07 | 3.25 |
MySQL Write-only
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 3,981.00 | 3,338.00 |
| Queries per second | 39,810.00 | 33,380.00 |
| Minimum Latency (ms) | 1.77 | 1.5 |
| Average Latency (ms) | 2.51 | 2.99 |
| Maximum Latency (ms) | 128.86 | 16.01 |
| 95th Percentile Latency (ms) | 3.3 | 4.91 |
MySQL Read/Write
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 2,042.00 | 1,305.00 |
| Queries per second | 20,420.00 | 13,050.00 |
| Minimum Latency (ms) | 3.94 | 4.22 |
| Average Latency (ms) | 4.89 | 7.65 |
| Maximum Latency (ms) | 58.24 | 28.08 |
| 95th Percentile Latency (ms) | 5.88 | 12.08 |
MySQL INSERT
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 5,470.00 | 3,834.00 |
| Queries per second | 54,700.00 | 38,340.00 |
| Minimum Latency (ms) | 1.13 | 0.99 |
| Average Latency (ms) | 1.83 | 2.6 |
| Maximum Latency (ms) | 111.33 | 18.67 |
| 95th Percentile Latency (ms) | 3.13 | 5.67 |
MySQL Bulk INSERT
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 996,869.00 | 701,975.00 |
| Queries per second | 9,968,690.00 | 7,019,750.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0.01 |
| Maximum Latency (ms) | 648.81 | 723.82 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 112,678.00 | 117,473.00 |
| Queries per second | 1,126,780.00 | 1,174,730.00 |
| Minimum Latency (ms) | 0.06 | 0.04 |
| Average Latency (ms) | 0.09 | 0.08 |
| Maximum Latency (ms) | 8.37 | 2.35 |
| 95th Percentile Latency (ms) | 0.13 | 0.13 |
MySQL SELECT (Random Points)
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 4,976.00 | 2,870.00 |
| Queries per second | 49,760.00 | 28,700.00 |
| Minimum Latency (ms) | 0.83 | 1.02 |
| Average Latency (ms) | 2.01 | 3.48 |
| Maximum Latency (ms) | 8.19 | 13.7 |
| 95th Percentile Latency (ms) | 3.02 | 4.91 |
MySQL SELECT (Random Ranges)
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 5,987.00 | 3,021.00 |
| Queries per second | 59,870.00 | 30,210.00 |
| Minimum Latency (ms) | 0.54 | 0.91 |
| Average Latency (ms) | 1.67 | 3.3 |
| Maximum Latency (ms) | 10.51 | 6.84 |
| 95th Percentile Latency (ms) | 2.18 | 4.82 |
MySQL UPDATE (Indexed)
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 5,883.00 | 3,707.00 |
| Queries per second | 58,830.00 | 37,070.00 |
| Minimum Latency (ms) | 0.98 | 1.03 |
| Average Latency (ms) | 1.7 | 2.69 |
| Maximum Latency (ms) | 4.44 | 24.2 |
| 95th Percentile Latency (ms) | 2.26 | 5.67 |
MySQL UPDATE (Non-Indexed)
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 6,195.00 | 4,481.00 |
| Queries per second | 61,950.00 | 44,810.00 |
| Minimum Latency (ms) | 1.18 | 0.96 |
| Average Latency (ms) | 1.61 | 2.23 |
| Maximum Latency (ms) | 30.16 | 80.39 |
| 95th Percentile Latency (ms) | 2.11 | 4.41 |
MySQL DELETE
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| Transactions per second | 23,800.00 | 20,095.00 |
| Queries per second | 238,000.00 | 200,950.00 |
| Minimum Latency (ms) | 0.06 | 0.04 |
| Average Latency (ms) | 0.42 | 0.5 |
| Maximum Latency (ms) | 2553.92 | 19.36 |
| 95th Percentile Latency (ms) | 1.7 | 2.43 |
Redis
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| PING_INLINE per Second | 34,129.69 | 23,180.34 |
| PING_MBULK per Second | 35,248.50 | 24,783.15 |
| SET per Second | 34,352.46 | 23,004.37 |
| GET per Second | 34,806.82 | 25,866.53 |
| INCR per Second | 34,199.73 | 24,125.45 |
| LPUSH per Second | 33,840.95 | 25,050.10 |
| RPUSH per Second | 34,698.12 | 23,250.41 |
| LPOP per Second | 32,041.01 | 22,650.06 |
| RPOP per Second | 33,400.13 | 23,730.42 |
| SADD per Second | 33,568.31 | 24,038.46 |
| HSET per Second | 33,489.62 | 24,691.36 |
| SPOP per Second | 34,855.35 | 24,461.84 |
| ZADD per Second | 32,658.39 | 22,276.68 |
| ZPOPMIN per Second | 33,134.53 | 22,361.36 |
| LRANGE_100 (first 100 elements) per Second | 22,158.21 | 13,349.35 |
| LRANGE_300 (first 300 elements) per Second | 12,084.59 | 5,978.00 |
| LRANGE_500 (first 500 elements) per Second | 8,313.93 | 4,053.34 |
| LRANGE_600 (first 600 elements) per Second | 7,367.57 | 3,627.66 |
| MSET (10 keys) per Second | 30,807.15 | 20,424.84 |
Redis Average Latency (ms)
| Vultr – Cloud Compute (1 GB) | Vultr – Cloud Compute (2 GB) | |
|---|---|---|
| PING_INLINE | 0.96 | 1.35 |
| PING_MBULK | 0.93 | 1.25 |
| SET | 0.96 | 1.36 |
| GET | 0.94 | 1.21 |
| INCR | 0.97 | 1.29 |
| LPUSH | 0.98 | 1.26 |
| RPUSH | 0.95 | 1.35 |
| LPOP | 1.03 | 1.40 |
| RPOP | 0.99 | 1.33 |
| SADD | 0.97 | 1.31 |
| HSET | 0.98 | 1.28 |
| SPOP | 0.94 | 1.27 |
| ZADD | 1.01 | 1.41 |
| ZPOPMIN | 0.99 | 1.38 |
| LRANGE_100 (first 100 elements) | 1.50 | 2.58 |
| LRANGE_300 (first 300 elements) | 2.81 | 5.57 |
| LRANGE_500 (first 500 elements) | 4.10 | 8.09 |
| LRANGE_600 (first 600 elements) | 4.58 | 9.04 |
| MSET (10 keys) | 1.10 | 1.77 |
Conclusion
From the friendly robots:
The Vultr Cloud Compute (1 GB) instance shows strong performance in single-threaded tasks with a good number of requests per second for Redis operations and MySQL OLTP workloads, though it struggles with larger list ranges and I/O intensive tasks. The Vultr Cloud Compute (2 GB) instance, despite having identical CPU architecture, performs better across the board with higher RPS for Redis operations, better file I/O throughput, and slightly lower latencies across most benchmarks, suggesting it is more suitable for I/O heavy and multi-threaded tasks. The 2 GB instance is more cost-effective for users needing higher RAM, better performance for larger datasets, or who anticipate higher workloads, while the 1 GB instance might suffice for lighter workloads and budget-conscious users.
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.