Vultr Cloud Compute (2 GB, 2 Cores) vs. Vultr High Frequency Intel (4 GB, 2 Cores)
Welcome to another round of the VPS Showdown. Today I've spun up brand new instance from Vultr and ran some benchmarks. Each instance was spun up with Ubuntu 24.04 LTS x64 and were created in the New York area (or close to it). Enough talk. Here's the data.
Overview
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (4 GB, 2 Cores) | |
|---|---|---|
| Last Benchmarked | Mon, 11 May 2026 04:00:52 GMT | Wed, 13 May 2026 08: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 | $15.00 | $24.00 |
| RAM (GB) | 2 | 4 |
| CPU Cores | 2 | 2 |
| Storage (TB) | 65 | 128 |
| Storage Type | SSD | NVMe |
| Transfer (TB) | 3 | 3 |
CPU
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (4 GB, 2 Cores) | |
|---|---|---|
| Vendor | GenuineIntel | GenuineIntel |
| Model Name | Intel Core Processor (Skylake, IBRS, no TSX) | Intel Core Processor (Skylake, IBRS, no TSX) |
| Clock Speed (MHz) | 3,792.00 | 3,791.94 |
| CPU Cache Size (KB) | 16,384.00 | 16,384.00 |
| BogoMips | 7,583.99 | 7,583.88 |
| Events per Second | 1,481.60 | 1,590.31 |
| Minimum Latency (ms) | 0.63 | 0.6 |
| Average Latency (ms) | 0.67 | 0.63 |
| Maximum Latency (ms) | 1.95 | 1.79 |
| 95th Percentile Latency (ms) | 0.77 | 0.67 |
Memory
Memory Read
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (4 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 6,401,389.08 | 7,807,742.85 |
| Mebibytes per second | 6,251.36 | 7,624.75 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.23 | 0.06 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (4 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 6,411,085.35 | 7,906,141.09 |
| Mebibytes per second | 6,260.83 | 7,720.84 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.18 | 0.04 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (4 GB, 2 Cores) | |
|---|---|---|
| Reads per Second | 4,345.71 | 8,035.78 |
| Writes per Second | 2,897.07 | 5,357.19 |
| Fsyncs per Second | 9,273.19 | 17,149.39 |
| Read Mebibytes per Second | 67.90 | 125.56 |
| Written Mebibytes per Second | 45.27 | 83.71 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.06 | 0.03 |
| Maximum Latency (ms) | 2.92 | 2.91 |
| 95th Percentile Latency (ms) | 0.17 | 0.12 |
Mutex
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (4 GB, 2 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 214.63 | 530.07 |
| Average Latency (ms) | 569.72 | 548.97 |
| Maximum Latency (ms) | 636.55 | 564.28 |
| 95th Percentile Latency (ms) | 634.66 | 559.50 |
MySQL
MySQL Read-only
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,015.00 | 10,624.00 |
| Queries per second | 80,150.00 | 106,240.00 |
| Minimum Latency (ms) | 0.92 | 0.87 |
| Average Latency (ms) | 1.25 | 0.94 |
| Maximum Latency (ms) | 5.5 | 2.48 |
| 95th Percentile Latency (ms) | 1.86 | 1.03 |
MySQL Write-only
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,497.00 | 10,496.00 |
| Queries per second | 84,970.00 | 104,960.00 |
| Minimum Latency (ms) | 0.76 | 0.62 |
| Average Latency (ms) | 1.17 | 0.95 |
| Maximum Latency (ms) | 3.04 | 2.57 |
| 95th Percentile Latency (ms) | 1.55 | 1.21 |
MySQL Read/Write
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 3,726.00 | 4,967.00 |
| Queries per second | 37,260.00 | 49,670.00 |
| Minimum Latency (ms) | 1.78 | 1.59 |
| Average Latency (ms) | 2.68 | 2.01 |
| Maximum Latency (ms) | 5.82 | 3.47 |
| 95th Percentile Latency (ms) | 3.43 | 2.39 |
MySQL INSERT
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 15,028.00 | 17,471.00 |
| Queries per second | 150,280.00 | 174,710.00 |
| Minimum Latency (ms) | 0.41 | 0.38 |
| Average Latency (ms) | 0.66 | 0.57 |
| Maximum Latency (ms) | 2.42 | 2.14 |
| 95th Percentile Latency (ms) | 0.86 | 0.8 |
MySQL Bulk INSERT
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 1,696,217.00 | 2,424,342.00 |
| Queries per second | 16,962,170.00 | 24,243,420.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0 |
| Maximum Latency (ms) | 283.37 | 208.42 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 201,989.00 | 243,477.00 |
| Queries per second | 2,019,890.00 | 2,434,770.00 |
| Minimum Latency (ms) | 0.03 | 0.03 |
| Average Latency (ms) | 0.05 | 0.04 |
| Maximum Latency (ms) | 0.51 | 0.75 |
| 95th Percentile Latency (ms) | 0.07 | 0.05 |
MySQL SELECT (Random Points)
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,025.00 | 11,659.00 |
| Queries per second | 80,250.00 | 116,590.00 |
| Minimum Latency (ms) | 0.35 | 0.22 |
| Average Latency (ms) | 1.24 | 0.86 |
| Maximum Latency (ms) | 3.55 | 3.08 |
| 95th Percentile Latency (ms) | 2.07 | 1.1 |
MySQL SELECT (Random Ranges)
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,336.00 | 10,594.00 |
| Queries per second | 83,360.00 | 105,940.00 |
| Minimum Latency (ms) | 0.4 | 0.36 |
| Average Latency (ms) | 1.2 | 0.94 |
| Maximum Latency (ms) | 4.25 | 3.17 |
| 95th Percentile Latency (ms) | 2.22 | 1.21 |
MySQL UPDATE (Indexed)
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 13,858.00 | 16,016.00 |
| Queries per second | 138,580.00 | 160,160.00 |
| Minimum Latency (ms) | 0.42 | 0.39 |
| Average Latency (ms) | 0.72 | 0.62 |
| Maximum Latency (ms) | 6.33 | 1.92 |
| 95th Percentile Latency (ms) | 0.95 | 0.86 |
MySQL UPDATE (Non-Indexed)
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 14,587.00 | 17,709.00 |
| Queries per second | 145,870.00 | 177,090.00 |
| Minimum Latency (ms) | 0.4 | 0.37 |
| Average Latency (ms) | 0.68 | 0.56 |
| Maximum Latency (ms) | 11.69 | 1.8 |
| 95th Percentile Latency (ms) | 0.9 | 0.74 |
MySQL DELETE
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 129,013.00 | 157,492.00 |
| Queries per second | 1,290,130.00 | 1,574,920.00 |
| Minimum Latency (ms) | 0.03 | 0.03 |
| Average Latency (ms) | 0.08 | 0.06 |
| Maximum Latency (ms) | 2.61 | 4.53 |
| 95th Percentile Latency (ms) | 0.09 | 0.07 |
Redis
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (4 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE per Second | 78,247.26 | 87,260.03 |
| PING_MBULK per Second | 74,738.41 | 87,950.75 |
| SET per Second | 77,041.60 | 88,731.15 |
| GET per Second | 83,333.33 | 89,365.51 |
| INCR per Second | 80,971.66 | 88,809.95 |
| LPUSH per Second | 79,113.92 | 89,126.56 |
| RPUSH per Second | 77,160.49 | 89,365.51 |
| LPOP per Second | 81,499.59 | 90,334.23 |
| RPOP per Second | 82,440.23 | 90,579.71 |
| SADD per Second | 80,192.46 | 90,171.33 |
| HSET per Second | 83,612.04 | 89,686.10 |
| SPOP per Second | 85,034.02 | 89,365.51 |
| ZADD per Second | 83,263.95 | 90,415.91 |
| ZPOPMIN per Second | 82,987.55 | 90,090.09 |
| LRANGE_100 (first 100 elements) per Second | 55,555.56 | 67,114.09 |
| LRANGE_300 (first 300 elements) per Second | 28,851.70 | 37,821.48 |
| LRANGE_500 (first 500 elements) per Second | 19,391.12 | 26,595.74 |
| LRANGE_600 (first 600 elements) per Second | 17,211.71 | 23,009.66 |
| MSET (10 keys) per Second | 80,256.82 | 90,826.52 |
Redis Average Latency (ms)
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (4 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE | 0.34 | 0.30 |
| PING_MBULK | 0.35 | 0.29 |
| SET | 0.34 | 0.29 |
| GET | 0.32 | 0.29 |
| INCR | 0.32 | 0.29 |
| LPUSH | 0.34 | 0.29 |
| RPUSH | 0.34 | 0.29 |
| LPOP | 0.32 | 0.29 |
| RPOP | 0.32 | 0.29 |
| SADD | 0.32 | 0.29 |
| HSET | 0.31 | 0.29 |
| SPOP | 0.30 | 0.29 |
| ZADD | 0.31 | 0.29 |
| ZPOPMIN | 0.31 | 0.29 |
| LRANGE_100 (first 100 elements) | 0.54 | 0.40 |
| LRANGE_300 (first 300 elements) | 1.11 | 0.68 |
| LRANGE_500 (first 500 elements) | 1.62 | 0.96 |
| LRANGE_600 (first 600 elements) | 1.84 | 1.20 |
| MSET (10 keys) | 0.38 | 0.29 |
Conclusion
From the friendly robots:
Comparing the Vultr Cloud Compute (2 GB, 2 Cores) and High Frequency Intel (4 GB, 2 Cores) instances, the latter demonstrates significantly better performance across most benchmarks, especially in CPU-intensive tasks and memory operations, likely due to the additional 2 GB of RAM and the same processor architecture. The High Frequency Intel instance shows higher requests per second and lower latencies for Redis operations, CPU events per second, file I/O throughput, and MySQL operations, indicating it handles high-performance tasks more efficiently. However, the Cloud Compute instance, while more cost-effective at $15 per month compared to $24 per month, still performs admirably for less demanding applications and shows competitive results in some specific benchmarks. For users needing more CPU power, memory, and who can afford a slightly higher cost, the High Frequency Intel instance is the better choice, whereas the Cloud Compute instance would serve well for smaller applications or when budget is a primary concern.
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.