Vultr Cloud Compute (4 GB, 2 Cores) vs. Vultr High Frequency Intel (8 GB, 3 Cores)
New day, new benchmarks. Today I've spun up some brand new instance from Vultr to run some benchmarks on. 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 (4 GB, 2 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Last Benchmarked | Thu, 11 Jun 2026 09:00:52 GMT | Wed, 10 Jun 2026 14: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 | $20.00 | $48.00 |
| RAM (GB) | 4 | 8 |
| CPU Cores | 2 | 3 |
| Storage (TB) | 80 | 256 |
| Storage Type | SSD | NVMe |
| Transfer (TB) | 3 | 4 |
CPU
| Vultr – Cloud Compute (4 GB, 2 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.91 | 3,792.00 |
| CPU Cache Size (KB) | 16,384.00 | 16,384.00 |
| BogoMips | 5,187.81 | 7,584.00 |
| Events per Second | 1,022.39 | 1,587.96 |
| Minimum Latency (ms) | 0.88 | 0.6 |
| Average Latency (ms) | 0.98 | 0.63 |
| Maximum Latency (ms) | 1.77 | 2.79 |
| 95th Percentile Latency (ms) | 1.21 | 0.67 |
Memory
Memory Read
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Operations per second | 3,523,809.57 | 7,883,811.41 |
| Mebibytes per second | 3,441.22 | 7,699.03 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.22 | 0.08 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Operations per second | 3,568,203.77 | 7,818,447.41 |
| Mebibytes per second | 3,484.57 | 7,635.20 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 1.02 | 0.07 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Reads per Second | 2,972.63 | 8,232.75 |
| Writes per Second | 1,981.75 | 5,488.50 |
| Fsyncs per Second | 6,347.81 | 17,567.69 |
| Read Mebibytes per Second | 46.45 | 128.64 |
| Written Mebibytes per Second | 30.96 | 85.76 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.09 | 0.03 |
| Maximum Latency (ms) | 17.12 | 6.44 |
| 95th Percentile Latency (ms) | 0.33 | 0.11 |
Mutex
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 899.28 | 318.10 |
| Average Latency (ms) | 935.93 | 361.83 |
| Maximum Latency (ms) | 969.92 | 375.78 |
| 95th Percentile Latency (ms) | 977.74 | 376.49 |
MySQL
MySQL Read-only
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 3,779.00 | 10,386.00 |
| Queries per second | 37,790.00 | 103,860.00 |
| Minimum Latency (ms) | 1.84 | 0.87 |
| Average Latency (ms) | 2.64 | 0.96 |
| Maximum Latency (ms) | 24.55 | 1.94 |
| 95th Percentile Latency (ms) | 3.82 | 1.08 |
MySQL Write-only
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 4,044.00 | 9,441.00 |
| Queries per second | 40,440.00 | 94,410.00 |
| Minimum Latency (ms) | 1.4 | 0.65 |
| Average Latency (ms) | 2.47 | 1.06 |
| Maximum Latency (ms) | 13.46 | 3.98 |
| 95th Percentile Latency (ms) | 3.3 | 1.34 |
MySQL Read/Write
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 1,798.00 | 4,387.00 |
| Queries per second | 17,980.00 | 43,870.00 |
| Minimum Latency (ms) | 3.86 | 1.64 |
| Average Latency (ms) | 5.56 | 2.28 |
| Maximum Latency (ms) | 27.33 | 3.88 |
| 95th Percentile Latency (ms) | 6.91 | 2.81 |
MySQL INSERT
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 6,405.00 | 15,792.00 |
| Queries per second | 64,050.00 | 157,920.00 |
| Minimum Latency (ms) | 0.99 | 0.38 |
| Average Latency (ms) | 1.56 | 0.63 |
| Maximum Latency (ms) | 15.15 | 2.1 |
| 95th Percentile Latency (ms) | 2.03 | 0.87 |
MySQL Bulk INSERT
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 865,805.00 | 2,259,059.00 |
| Queries per second | 8,658,050.00 | 22,590,590.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0 |
| Maximum Latency (ms) | 538.25 | 200.1 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 126,618.00 | 236,719.00 |
| Queries per second | 1,266,180.00 | 2,367,190.00 |
| Minimum Latency (ms) | 0.05 | 0.03 |
| Average Latency (ms) | 0.08 | 0.04 |
| Maximum Latency (ms) | 2.46 | 1.14 |
| 95th Percentile Latency (ms) | 0.11 | 0.05 |
MySQL SELECT (Random Points)
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 3,674.00 | 12,222.00 |
| Queries per second | 36,740.00 | 122,220.00 |
| Minimum Latency (ms) | 1.07 | 0.28 |
| Average Latency (ms) | 2.72 | 0.82 |
| Maximum Latency (ms) | 6.45 | 2.66 |
| 95th Percentile Latency (ms) | 3.55 | 1.04 |
MySQL SELECT (Random Ranges)
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 2,728.00 | 10,623.00 |
| Queries per second | 27,280.00 | 106,230.00 |
| Minimum Latency (ms) | 1.3 | 0.29 |
| Average Latency (ms) | 3.66 | 0.94 |
| Maximum Latency (ms) | 11.85 | 4.04 |
| 95th Percentile Latency (ms) | 5 | 1.23 |
MySQL UPDATE (Indexed)
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 5,438.00 | 15,315.00 |
| Queries per second | 54,380.00 | 153,150.00 |
| Minimum Latency (ms) | 0.99 | 0.39 |
| Average Latency (ms) | 1.84 | 0.65 |
| Maximum Latency (ms) | 13.86 | 2.08 |
| 95th Percentile Latency (ms) | 2.71 | 0.92 |
MySQL UPDATE (Non-Indexed)
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 6,370.00 | 16,290.00 |
| Queries per second | 63,700.00 | 162,900.00 |
| Minimum Latency (ms) | 1.01 | 0.38 |
| Average Latency (ms) | 1.57 | 0.61 |
| Maximum Latency (ms) | 8.99 | 1.81 |
| 95th Percentile Latency (ms) | 2.07 | 0.83 |
MySQL DELETE
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| Transactions per second | 51,180.00 | 144,202.00 |
| Queries per second | 511,800.00 | 1,442,020.00 |
| Minimum Latency (ms) | 0.05 | 0.03 |
| Average Latency (ms) | 0.19 | 0.07 |
| Maximum Latency (ms) | 6.11 | 3.26 |
| 95th Percentile Latency (ms) | 1.39 | 0.09 |
Redis
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| PING_INLINE per Second | 49,677.10 | 88,809.95 |
| PING_MBULK per Second | 45,372.05 | 87,873.46 |
| SET per Second | 45,392.64 | 87,336.24 |
| GET per Second | 53,163.21 | 86,430.43 |
| INCR per Second | 48,732.94 | 88,339.23 |
| LPUSH per Second | 50,327.12 | 90,090.09 |
| RPUSH per Second | 48,285.85 | 88,261.25 |
| LPOP per Second | 48,355.90 | 90,334.23 |
| RPOP per Second | 51,413.88 | 90,744.10 |
| SADD per Second | 48,332.53 | 90,991.81 |
| HSET per Second | 49,285.36 | 90,415.91 |
| SPOP per Second | 48,332.53 | 89,285.71 |
| ZADD per Second | 51,229.51 | 89,206.06 |
| ZPOPMIN per Second | 45,085.66 | 89,847.26 |
| LRANGE_100 (first 100 elements) per Second | 27,122.32 | 66,711.14 |
| LRANGE_300 (first 300 elements) per Second | 12,442.45 | 37,216.23 |
| LRANGE_500 (first 500 elements) per Second | 7,930.21 | 25,893.32 |
| LRANGE_600 (first 600 elements) per Second | 6,902.74 | 23,359.03 |
| MSET (10 keys) per Second | 45,146.73 | 88,731.15 |
Redis Average Latency (ms)
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Frequency Intel (8 GB, 3 Cores) | |
|---|---|---|
| PING_INLINE | 0.53 | 0.29 |
| PING_MBULK | 0.57 | 0.29 |
| SET | 0.57 | 0.30 |
| GET | 0.49 | 0.30 |
| INCR | 0.53 | 0.29 |
| LPUSH | 0.51 | 0.29 |
| RPUSH | 0.54 | 0.29 |
| LPOP | 0.54 | 0.29 |
| RPOP | 0.52 | 0.28 |
| SADD | 0.55 | 0.28 |
| HSET | 0.54 | 0.29 |
| SPOP | 0.54 | 0.29 |
| ZADD | 0.52 | 0.29 |
| ZPOPMIN | 0.57 | 0.29 |
| LRANGE_100 (first 100 elements) | 1.02 | 0.39 |
| LRANGE_300 (first 300 elements) | 2.29 | 0.69 |
| LRANGE_500 (first 500 elements) | 3.27 | 1.00 |
| LRANGE_600 (first 600 elements) | 3.91 | 1.09 |
| MSET (10 keys) | 0.78 | 0.30 |
Conclusion
From the friendly robots:
When comparing the Vultr Cloud Compute (4 GB, 2 Cores) instance against the High Frequency Intel (8 GB, 3 Cores) instance, it's evident that the latter offers significantly superior performance across the board. The high-frequency instance excels in handling Redis commands, delivering higher requests per second and lower latency for most operations. It also performs better in CPU and memory benchmarks, showcasing lower latencies and higher throughput rates in file I/O operations and MySQL benchmarks. The High Frequency Intel instance is ideal for applications requiring higher computational power, better memory management, and lower latency for database operations, making it particularly suitable for CPU-intensive workloads and high-demand data processing tasks. Meanwhile, the Cloud Compute instance, despite its lower cost, is more suited for basic tasks, lower traffic websites, or applications that do not demand high concurrency or extensive data processing capabilities.
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.