Vultr Cloud Compute (2 GB) vs. Vultr Cloud Compute (4 GB, 2 Cores)
Welcome to another round of the VPS Showdown. 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. Let's get into the numbers.
Overview
| Vultr – Cloud Compute (2 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Last Benchmarked | Thu, 11 Jun 2026 14:00:52 GMT | Thu, 11 Jun 2026 09: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 | $10.00 | $20.00 |
| RAM (GB) | 2 | 4 |
| CPU Cores | 1 | 2 |
| Storage (TB) | 50 | 80 |
| Storage Type | SSD | SSD |
| Transfer (TB) | 2 | 3 |
CPU
| Vultr – Cloud Compute (2 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Vendor | GenuineIntel | GenuineIntel |
| Model Name | Intel Xeon Processor (Skylake, IBRS) | Intel Xeon Processor (Skylake, IBRS) |
| Clock Speed (MHz) | 2,593.90 | 2,593.91 |
| CPU Cache Size (KB) | 16,384.00 | 16,384.00 |
| BogoMips | 5,187.80 | 5,187.81 |
| Events per Second | 1,102.14 | 1,022.39 |
| Minimum Latency (ms) | 0.88 | 0.88 |
| Average Latency (ms) | 0.91 | 0.98 |
| Maximum Latency (ms) | 2.28 | 1.77 |
| 95th Percentile Latency (ms) | 0.94 | 1.21 |
Memory
Memory Read
| Vultr – Cloud Compute (2 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 3,690,700.44 | 3,523,809.57 |
| Mebibytes per second | 3,604.20 | 3,441.22 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 1.07 | 0.22 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – Cloud Compute (2 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 3,696,317.88 | 3,568,203.77 |
| Mebibytes per second | 3,609.69 | 3,484.57 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.27 | 1.02 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – Cloud Compute (2 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Reads per Second | 2,596.60 | 2,972.63 |
| Writes per Second | 1,731.00 | 1,981.75 |
| Fsyncs per Second | 5,552.00 | 6,347.81 |
| Read Mebibytes per Second | 40.57 | 46.45 |
| Written Mebibytes per Second | 27.05 | 30.96 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.1 | 0.09 |
| Maximum Latency (ms) | 5.91 | 17.12 |
| 95th Percentile Latency (ms) | 0.34 | 0.33 |
Mutex
| Vultr – Cloud Compute (2 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 1,739.44 | 899.28 |
| Average Latency (ms) | 1,752.16 | 935.93 |
| Maximum Latency (ms) | 1,759.94 | 969.92 |
| 95th Percentile Latency (ms) | 1,771.29 | 977.74 |
MySQL
MySQL Read-only
| Vultr – Cloud Compute (2 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 5,635.00 | 3,779.00 |
| Queries per second | 56,350.00 | 37,790.00 |
| Minimum Latency (ms) | 1.67 | 1.84 |
| Average Latency (ms) | 1.77 | 2.64 |
| Maximum Latency (ms) | 5.49 | 24.55 |
| 95th Percentile Latency (ms) | 1.89 | 3.82 |
MySQL Write-only
| Vultr – Cloud Compute (2 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 5,082.00 | 4,044.00 |
| Queries per second | 50,820.00 | 40,440.00 |
| Minimum Latency (ms) | 1.27 | 1.4 |
| Average Latency (ms) | 1.97 | 2.47 |
| Maximum Latency (ms) | 7.83 | 13.46 |
| 95th Percentile Latency (ms) | 2.71 | 3.3 |
MySQL Read/Write
| Vultr – Cloud Compute (2 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 2,462.00 | 1,798.00 |
| Queries per second | 24,620.00 | 17,980.00 |
| Minimum Latency (ms) | 3.37 | 3.86 |
| Average Latency (ms) | 4.06 | 5.56 |
| Maximum Latency (ms) | 9.51 | 27.33 |
| 95th Percentile Latency (ms) | 4.91 | 6.91 |
MySQL INSERT
| Vultr – Cloud Compute (2 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,612.00 | 6,405.00 |
| Queries per second | 86,120.00 | 64,050.00 |
| Minimum Latency (ms) | 0.7 | 0.99 |
| Average Latency (ms) | 1.16 | 1.56 |
| Maximum Latency (ms) | 5.5 | 15.15 |
| 95th Percentile Latency (ms) | 1.5 | 2.03 |
MySQL Bulk INSERT
| Vultr – Cloud Compute (2 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 767,507.00 | 865,805.00 |
| Queries per second | 7,675,070.00 | 8,658,050.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0.01 |
| Maximum Latency (ms) | 608.85 | 538.25 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – Cloud Compute (2 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 168,599.00 | 126,618.00 |
| Queries per second | 1,685,990.00 | 1,266,180.00 |
| Minimum Latency (ms) | 0.05 | 0.05 |
| Average Latency (ms) | 0.06 | 0.08 |
| Maximum Latency (ms) | 1.54 | 2.46 |
| 95th Percentile Latency (ms) | 0.08 | 0.11 |
MySQL SELECT (Random Points)
| Vultr – Cloud Compute (2 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 4,151.00 | 3,674.00 |
| Queries per second | 41,510.00 | 36,740.00 |
| Minimum Latency (ms) | 0.82 | 1.07 |
| Average Latency (ms) | 2.41 | 2.72 |
| Maximum Latency (ms) | 6.25 | 6.45 |
| 95th Percentile Latency (ms) | 3.07 | 3.55 |
MySQL SELECT (Random Ranges)
| Vultr – Cloud Compute (2 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 2,614.00 | 2,728.00 |
| Queries per second | 26,140.00 | 27,280.00 |
| Minimum Latency (ms) | 1.09 | 1.3 |
| Average Latency (ms) | 3.82 | 3.66 |
| Maximum Latency (ms) | 7.53 | 11.85 |
| 95th Percentile Latency (ms) | 5 | 5 |
MySQL UPDATE (Indexed)
| Vultr – Cloud Compute (2 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,286.00 | 5,438.00 |
| Queries per second | 82,860.00 | 54,380.00 |
| Minimum Latency (ms) | 0.7 | 0.99 |
| Average Latency (ms) | 1.21 | 1.84 |
| Maximum Latency (ms) | 5.25 | 13.86 |
| 95th Percentile Latency (ms) | 1.73 | 2.71 |
MySQL UPDATE (Non-Indexed)
| Vultr – Cloud Compute (2 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,245.00 | 6,370.00 |
| Queries per second | 82,450.00 | 63,700.00 |
| Minimum Latency (ms) | 0.7 | 1.01 |
| Average Latency (ms) | 1.21 | 1.57 |
| Maximum Latency (ms) | 7.3 | 8.99 |
| 95th Percentile Latency (ms) | 1.64 | 2.07 |
MySQL DELETE
| Vultr – Cloud Compute (2 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 77,233.00 | 51,180.00 |
| Queries per second | 772,330.00 | 511,800.00 |
| Minimum Latency (ms) | 0.05 | 0.05 |
| Average Latency (ms) | 0.13 | 0.19 |
| Maximum Latency (ms) | 4.25 | 6.11 |
| 95th Percentile Latency (ms) | 0.65 | 1.39 |
Redis
| Vultr – Cloud Compute (2 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE per Second | 35,906.64 | 49,677.10 |
| PING_MBULK per Second | 36,968.58 | 45,372.05 |
| SET per Second | 36,101.08 | 45,392.64 |
| GET per Second | 36,968.58 | 53,163.21 |
| INCR per Second | 36,845.98 | 48,732.94 |
| LPUSH per Second | 36,337.21 | 50,327.12 |
| RPUSH per Second | 36,179.45 | 48,285.85 |
| LPOP per Second | 35,842.29 | 48,355.90 |
| RPOP per Second | 34,293.55 | 51,413.88 |
| SADD per Second | 33,046.93 | 48,332.53 |
| HSET per Second | 35,050.82 | 49,285.36 |
| SPOP per Second | 36,363.64 | 48,332.53 |
| ZADD per Second | 35,460.99 | 51,229.51 |
| ZPOPMIN per Second | 36,832.41 | 45,085.66 |
| LRANGE_100 (first 100 elements) per Second | 16,123.83 | 27,122.32 |
| LRANGE_300 (first 300 elements) per Second | 7,284.38 | 12,442.45 |
| LRANGE_500 (first 500 elements) per Second | 4,626.84 | 7,930.21 |
| LRANGE_600 (first 600 elements) per Second | 3,885.15 | 6,902.74 |
| MSET (10 keys) per Second | 26,274.30 | 45,146.73 |
Redis Average Latency (ms)
| Vultr – Cloud Compute (2 GB) | Vultr – Cloud Compute (4 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE | 0.90 | 0.53 |
| PING_MBULK | 0.88 | 0.57 |
| SET | 0.91 | 0.57 |
| GET | 0.89 | 0.49 |
| INCR | 0.89 | 0.53 |
| LPUSH | 0.91 | 0.51 |
| RPUSH | 0.91 | 0.54 |
| LPOP | 0.92 | 0.54 |
| RPOP | 0.96 | 0.52 |
| SADD | 0.98 | 0.55 |
| HSET | 0.94 | 0.54 |
| SPOP | 0.89 | 0.54 |
| ZADD | 0.93 | 0.52 |
| ZPOPMIN | 0.89 | 0.57 |
| LRANGE_100 (first 100 elements) | 2.16 | 1.02 |
| LRANGE_300 (first 300 elements) | 4.74 | 2.29 |
| LRANGE_500 (first 500 elements) | 7.32 | 3.27 |
| LRANGE_600 (first 600 elements) | 8.47 | 3.91 |
| MSET (10 keys) | 1.35 | 0.78 |
Conclusion
From the friendly robots:
Upon analyzing the benchmark results, the Vultr Cloud Compute instance with 2 GB RAM and 1 CPU core offers robust Redis performance with high request rates and relatively low latency, making it a strong choice for Redis workloads. However, the Vultr Cloud Compute instance with 4 GB RAM and 2 CPU cores excels in handling more demanding tasks due to its higher CPU count, improved Redis performance with even higher request rates and lower latencies, superior MySQL performance, and better overall file I/O operations, making it a better choice for CPU-intensive, multi-threaded, or memory-heavy workloads. The higher monthly cost of the 4 GB instance reflects its enhanced capabilities and makes it ideal for applications requiring greater computational and memory resources.
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.