Vultr Cloud Compute (2 GB, 2 Cores) vs. Vultr High Frequency Intel (8 GB, 3 Cores)
My friend, I'm so glad you're here! 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 all resided in or around the New York / New Jersey area. Enough talk. Here's the data.
Overview
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Last Benchmarked | Mon, 11 May 2026 04:00:52 GMT | Wed, 13 May 2026 12:00:56 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 | $48.00 |
| RAM (GB) | 2 | 8 |
| CPU Cores | 2 | 3 |
| Storage (TB) | 65 | 256 |
| Storage Type | SSD | NVMe |
| Transfer (TB) | 3 | 4 |
CPU
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (8 GB, 3 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,588.61 |
| Minimum Latency (ms) | 0.63 | 0.6 |
| Average Latency (ms) | 0.67 | 0.63 |
| Maximum Latency (ms) | 1.95 | 1.06 |
| 95th Percentile Latency (ms) | 0.77 | 0.67 |
Memory
Memory Read
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Operations per second | 6,401,389.08 | 7,884,082.37 |
| Mebibytes per second | 6,251.36 | 7,699.30 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.23 | 0.22 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Operations per second | 6,411,085.35 | 7,885,513.57 |
| Mebibytes per second | 6,260.83 | 7,700.70 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.18 | 0.22 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Reads per Second | 4,345.71 | 8,376.82 |
| Writes per Second | 2,897.07 | 5,584.54 |
| Fsyncs per Second | 9,273.19 | 17,873.04 |
| Read Mebibytes per Second | 67.90 | 130.89 |
| Written Mebibytes per Second | 45.27 | 87.26 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.06 | 0.03 |
| Maximum Latency (ms) | 2.92 | 7.2 |
| 95th Percentile Latency (ms) | 0.17 | 0.11 |
Mutex
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 214.63 | 313.28 |
| Average Latency (ms) | 569.72 | 357.73 |
| Maximum Latency (ms) | 636.55 | 383.79 |
| 95th Percentile Latency (ms) | 634.66 | 383.33 |
MySQL
MySQL Read-only
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 8,015.00 | 10,451.00 |
| Queries per second | 80,150.00 | 104,510.00 |
| Minimum Latency (ms) | 0.92 | 0.88 |
| Average Latency (ms) | 1.25 | 0.96 |
| Maximum Latency (ms) | 5.5 | 2.21 |
| 95th Percentile Latency (ms) | 1.86 | 1.06 |
MySQL Write-only
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 8,497.00 | 9,424.00 |
| Queries per second | 84,970.00 | 94,240.00 |
| Minimum Latency (ms) | 0.76 | 0.66 |
| Average Latency (ms) | 1.17 | 1.06 |
| Maximum Latency (ms) | 3.04 | 2.59 |
| 95th Percentile Latency (ms) | 1.55 | 1.34 |
MySQL Read/Write
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 3,726.00 | 4,489.00 |
| Queries per second | 37,260.00 | 44,890.00 |
| Minimum Latency (ms) | 1.78 | 1.66 |
| Average Latency (ms) | 2.68 | 2.23 |
| Maximum Latency (ms) | 5.82 | 3.58 |
| 95th Percentile Latency (ms) | 3.43 | 2.66 |
MySQL INSERT
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 15,028.00 | 14,748.00 |
| Queries per second | 150,280.00 | 147,480.00 |
| Minimum Latency (ms) | 0.41 | 0.39 |
| Average Latency (ms) | 0.66 | 0.68 |
| Maximum Latency (ms) | 2.42 | 8.13 |
| 95th Percentile Latency (ms) | 0.86 | 0.89 |
MySQL Bulk INSERT
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 1,696,217.00 | 2,395,217.00 |
| Queries per second | 16,962,170.00 | 23,952,170.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0 |
| Maximum Latency (ms) | 283.37 | 208.41 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 201,989.00 | 234,211.00 |
| Queries per second | 2,019,890.00 | 2,342,110.00 |
| Minimum Latency (ms) | 0.03 | 0.03 |
| Average Latency (ms) | 0.05 | 0.04 |
| Maximum Latency (ms) | 0.51 | 0.3 |
| 95th Percentile Latency (ms) | 0.07 | 0.05 |
MySQL SELECT (Random Points)
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 8,025.00 | 12,201.00 |
| Queries per second | 80,250.00 | 122,010.00 |
| Minimum Latency (ms) | 0.35 | 0.22 |
| Average Latency (ms) | 1.24 | 0.82 |
| Maximum Latency (ms) | 3.55 | 2.86 |
| 95th Percentile Latency (ms) | 2.07 | 1.04 |
MySQL SELECT (Random Ranges)
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 8,336.00 | 10,460.00 |
| Queries per second | 83,360.00 | 104,600.00 |
| Minimum Latency (ms) | 0.4 | 0.32 |
| Average Latency (ms) | 1.2 | 0.96 |
| Maximum Latency (ms) | 4.25 | 2.97 |
| 95th Percentile Latency (ms) | 2.22 | 1.23 |
MySQL UPDATE (Indexed)
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 13,858.00 | 15,980.00 |
| Queries per second | 138,580.00 | 159,800.00 |
| Minimum Latency (ms) | 0.42 | 0.39 |
| Average Latency (ms) | 0.72 | 0.63 |
| Maximum Latency (ms) | 6.33 | 12.56 |
| 95th Percentile Latency (ms) | 0.95 | 0.87 |
MySQL UPDATE (Non-Indexed)
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 14,587.00 | 15,997.00 |
| Queries per second | 145,870.00 | 159,970.00 |
| Minimum Latency (ms) | 0.4 | 0.38 |
| Average Latency (ms) | 0.68 | 0.62 |
| Maximum Latency (ms) | 11.69 | 6.69 |
| 95th Percentile Latency (ms) | 0.9 | 0.87 |
MySQL DELETE
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 129,013.00 | 140,187.00 |
| Queries per second | 1,290,130.00 | 1,401,870.00 |
| Minimum Latency (ms) | 0.03 | 0.03 |
| Average Latency (ms) | 0.08 | 0.07 |
| Maximum Latency (ms) | 2.61 | 7.56 |
| 95th Percentile Latency (ms) | 0.09 | 0.08 |
Redis
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| PING_INLINE per Second | 78,247.26 | 89,126.56 |
| PING_MBULK per Second | 74,738.41 | 88,028.16 |
| SET per Second | 77,041.60 | 89,047.20 |
| GET per Second | 83,333.33 | 87,032.20 |
| INCR per Second | 80,971.66 | 87,950.75 |
| LPUSH per Second | 79,113.92 | 88,731.15 |
| RPUSH per Second | 77,160.49 | 88,652.48 |
| LPOP per Second | 81,499.59 | 88,417.33 |
| RPOP per Second | 82,440.23 | 88,809.95 |
| SADD per Second | 80,192.46 | 87,565.68 |
| HSET per Second | 83,612.04 | 86,805.56 |
| SPOP per Second | 85,034.02 | 87,565.68 |
| ZADD per Second | 83,263.95 | 88,967.98 |
| ZPOPMIN per Second | 82,987.55 | 88,417.33 |
| LRANGE_100 (first 100 elements) per Second | 55,555.56 | 63,775.51 |
| LRANGE_300 (first 300 elements) per Second | 28,851.70 | 37,453.18 |
| LRANGE_500 (first 500 elements) per Second | 19,391.12 | 26,441.04 |
| LRANGE_600 (first 600 elements) per Second | 17,211.71 | 23,601.61 |
| MSET (10 keys) per Second | 80,256.82 | 91,324.20 |
Redis Average Latency (ms)
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| PING_INLINE | 0.34 | 0.29 |
| PING_MBULK | 0.35 | 0.29 |
| SET | 0.34 | 0.29 |
| GET | 0.32 | 0.30 |
| 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.30 |
| 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.08 |
| MSET (10 keys) | 0.38 | 0.29 |
Conclusion
From the friendly robots:
The Vultr Cloud Compute instance with 2 GB RAM and 2 cores performs admirably for basic tasks, showing strong Redis command response rates and low latencies for most operations, although it struggles slightly with larger LRANGE operations. In contrast, the High Frequency Intel instance with 8 GB RAM and 3 cores provides significantly better performance across the board, handling Redis commands at an extremely high rate with low latencies, superior CPU event processing, and excellent file I/O throughput. While the Cloud Compute instance offers a good balance for modest workloads and development environments, the High Frequency Intel instance is ideal for more demanding applications requiring high concurrency, large data set handling, and intensive compute tasks.
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.