Vultr Cloud Compute (8 GB, 4 Cores) vs. Vultr High Frequency Intel (8 GB, 3 Cores)
Same showdown, different day. Today I've spun up brand new instance from Vultr to run some benchmarks on. All instances were running Ubuntu 24.04 LTS x64 and were created in the New York area (or close to it). Without further ado, here's the results.
Overview
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Last Benchmarked | Sat, 23 May 2026 11:00:52 GMT | Fri, 22 May 2026 23:00:52 GMT |
| Linux Distro | Ubuntu 24.04 LTS x64 | Ubuntu 24.04 LTS x64 |
| Kernel Version | 6.8.0-117-generic | 6.8.0-117-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 | $40.00 | $48.00 |
| RAM (GB) | 8 | 8 |
| CPU Cores | 4 | 3 |
| Storage (TB) | 160 | 256 |
| Storage Type | SSD | NVMe |
| Transfer (TB) | 4 | 4 |
CPU
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Vendor | GenuineIntel | GenuineIntel |
| Model Name | Intel Xeon Processor (Skylake, IBRS) | Intel Core Processor (Skylake, IBRS, no TSX) |
| Clock Speed (MHz) | 2,593.90 | 3,792.05 |
| CPU Cache Size (KB) | 16,384.00 | 16,384.00 |
| BogoMips | 5,187.80 | 7,584.10 |
| Events per Second | 1,100.82 | 1,611.54 |
| Minimum Latency (ms) | 0.88 | 0.6 |
| Average Latency (ms) | 0.91 | 0.62 |
| Maximum Latency (ms) | 1.56 | 1.37 |
| 95th Percentile Latency (ms) | 0.97 | 0.65 |
Memory
Memory Read
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Operations per second | 3,685,781.23 | 7,987,810.00 |
| Mebibytes per second | 3,599.40 | 7,800.60 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 1.03 | 0.09 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Operations per second | 3,590,629.63 | 7,968,326.02 |
| Mebibytes per second | 3,506.47 | 7,781.57 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 1.16 | 0.04 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Reads per Second | 4,999.39 | 8,251.54 |
| Writes per Second | 3,332.93 | 5,501.03 |
| Fsyncs per Second | 10,670.47 | 17,610.48 |
| Read Mebibytes per Second | 78.12 | 128.93 |
| Written Mebibytes per Second | 52.08 | 85.95 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.05 | 0.03 |
| Maximum Latency (ms) | 37.52 | 6.57 |
| 95th Percentile Latency (ms) | 0.18 | 0.11 |
Mutex
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 369.37 | 161.36 |
| Average Latency (ms) | 416.22 | 329.22 |
| Maximum Latency (ms) | 441.77 | 380.33 |
| 95th Percentile Latency (ms) | 442.73 | 383.33 |
MySQL
MySQL Read-only
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 5,144.00 | 10,637.00 |
| Queries per second | 51,440.00 | 106,370.00 |
| Minimum Latency (ms) | 1.72 | 0.85 |
| Average Latency (ms) | 1.94 | 0.94 |
| Maximum Latency (ms) | 7.67 | 1.8 |
| 95th Percentile Latency (ms) | 2.35 | 1.03 |
MySQL Write-only
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 5,108.00 | 9,705.00 |
| Queries per second | 51,080.00 | 97,050.00 |
| Minimum Latency (ms) | 1.15 | 0.66 |
| Average Latency (ms) | 1.96 | 1.03 |
| Maximum Latency (ms) | 12.52 | 3.97 |
| 95th Percentile Latency (ms) | 2.71 | 1.27 |
MySQL Read/Write
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 2,247.00 | 4,692.00 |
| Queries per second | 22,470.00 | 46,920.00 |
| Minimum Latency (ms) | 3.08 | 1.65 |
| Average Latency (ms) | 4.45 | 2.13 |
| Maximum Latency (ms) | 29.7 | 3.41 |
| 95th Percentile Latency (ms) | 5.28 | 2.48 |
MySQL INSERT
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 7,630.00 | 15,216.00 |
| Queries per second | 76,300.00 | 152,160.00 |
| Minimum Latency (ms) | 0.71 | 0.38 |
| Average Latency (ms) | 1.31 | 0.66 |
| Maximum Latency (ms) | 29.81 | 12.51 |
| 95th Percentile Latency (ms) | 1.55 | 0.84 |
MySQL Bulk INSERT
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 898,571.00 | 2,457,847.00 |
| Queries per second | 8,985,710.00 | 24,578,470.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0 |
| Maximum Latency (ms) | 505.86 | 201.89 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 149,465.00 | 242,349.00 |
| Queries per second | 1,494,650.00 | 2,423,490.00 |
| Minimum Latency (ms) | 0.05 | 0.03 |
| Average Latency (ms) | 0.07 | 0.04 |
| Maximum Latency (ms) | 1.22 | 0.25 |
| 95th Percentile Latency (ms) | 0.09 | 0.05 |
MySQL SELECT (Random Points)
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 4,249.00 | 12,149.00 |
| Queries per second | 42,490.00 | 121,490.00 |
| Minimum Latency (ms) | 0.83 | 0.2 |
| Average Latency (ms) | 2.35 | 0.82 |
| Maximum Latency (ms) | 6.6 | 2.49 |
| 95th Percentile Latency (ms) | 3.02 | 1.04 |
MySQL SELECT (Random Ranges)
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 2,637.00 | 10,597.00 |
| Queries per second | 26,370.00 | 105,970.00 |
| Minimum Latency (ms) | 0.94 | 0.26 |
| Average Latency (ms) | 3.79 | 0.94 |
| Maximum Latency (ms) | 6.3 | 3.71 |
| 95th Percentile Latency (ms) | 5.09 | 1.21 |
MySQL UPDATE (Indexed)
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 7,166.00 | 14,930.00 |
| Queries per second | 71,660.00 | 149,300.00 |
| Minimum Latency (ms) | 0.7 | 0.38 |
| Average Latency (ms) | 1.39 | 0.67 |
| Maximum Latency (ms) | 28.84 | 13.18 |
| 95th Percentile Latency (ms) | 1.79 | 0.92 |
MySQL UPDATE (Non-Indexed)
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 7,661.00 | 16,526.00 |
| Queries per second | 76,610.00 | 165,260.00 |
| Minimum Latency (ms) | 0.7 | 0.38 |
| Average Latency (ms) | 1.3 | 0.6 |
| Maximum Latency (ms) | 33.97 | 2.79 |
| 95th Percentile Latency (ms) | 1.58 | 0.81 |
MySQL DELETE
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 69,690.00 | 141,899.00 |
| Queries per second | 696,900.00 | 1,418,990.00 |
| Minimum Latency (ms) | 0.05 | 0.03 |
| Average Latency (ms) | 0.14 | 0.07 |
| Maximum Latency (ms) | 27.73 | 7.25 |
| 95th Percentile Latency (ms) | 0.87 | 0.08 |
Redis
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| PING_INLINE per Second | 54,436.58 | 89,847.26 |
| PING_MBULK per Second | 48,828.12 | 90,497.73 |
| SET per Second | 51,572.98 | 90,991.81 |
| GET per Second | 48,239.27 | 89,445.44 |
| INCR per Second | 52,328.62 | 90,415.91 |
| LPUSH per Second | 45,454.54 | 90,991.81 |
| RPUSH per Second | 49,751.24 | 90,826.52 |
| LPOP per Second | 53,390.28 | 91,240.88 |
| RPOP per Second | 53,648.07 | 90,909.09 |
| SADD per Second | 48,285.85 | 90,415.91 |
| HSET per Second | 51,493.30 | 90,909.09 |
| SPOP per Second | 52,910.05 | 90,826.52 |
| ZADD per Second | 53,504.55 | 89,525.52 |
| ZPOPMIN per Second | 53,590.57 | 89,445.44 |
| LRANGE_100 (first 100 elements) per Second | 28,645.09 | 65,919.58 |
| LRANGE_300 (first 300 elements) per Second | 13,131.98 | 36,616.62 |
| LRANGE_500 (first 500 elements) per Second | 8,529.51 | 26,281.21 |
| LRANGE_600 (first 600 elements) per Second | 7,479.99 | 23,435.67 |
| MSET (10 keys) per Second | 49,212.60 | 92,936.80 |
Redis Average Latency (ms)
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| PING_INLINE | 0.47 | 0.29 |
| PING_MBULK | 0.53 | 0.28 |
| SET | 0.50 | 0.28 |
| GET | 0.54 | 0.29 |
| INCR | 0.49 | 0.28 |
| LPUSH | 0.58 | 0.28 |
| RPUSH | 0.52 | 0.28 |
| LPOP | 0.49 | 0.28 |
| RPOP | 0.48 | 0.28 |
| SADD | 0.54 | 0.28 |
| HSET | 0.53 | 0.28 |
| SPOP | 0.49 | 0.28 |
| ZADD | 0.48 | 0.29 |
| ZPOPMIN | 0.48 | 0.29 |
| LRANGE_100 (first 100 elements) | 0.91 | 0.39 |
| LRANGE_300 (first 300 elements) | 1.94 | 0.70 |
| LRANGE_500 (first 500 elements) | 3.00 | 0.97 |
| LRANGE_600 (first 600 elements) | 3.43 | 1.09 |
| MSET (10 keys) | 0.77 | 0.28 |
Conclusion
From the friendly robots:
After analyzing the benchmark results from both Vultr instances, it's clear that the High Frequency Intel (8 GB, 3 Cores) generally outperforms the Cloud Compute (8 GB, 4 Cores) in terms of raw performance, especially in Redis operations where it achieves significantly higher request rates per second with lower latencies. The High Frequency instance also shows superior performance in CPU benchmarks, file I/O operations, and MySQL database tasks, indicating a slight edge in processing power and I/O efficiency likely due to its higher clock speed and NVMe storage. The Cloud Compute instance, while still competent, lags behind in these metrics, particularly in I/O operations and MySQL bulk insert tasks. Given these results, the High Frequency Intel instance is ideal for use cases requiring high throughput and low latency, such as caching services, high-frequency trading platforms, or databases demanding rapid response times and heavy I/O operations, whereas the Cloud Compute instance might be more suitable for general-purpose workloads or scenarios where cost-efficiency and a slightly larger number of CPU cores are priorities.
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.