Vultr Cloud Compute (8 GB, 4 Cores) vs. Vultr High Performance Intel (1 GB)
Welcome to another round of the VPS Showdown. Today I've spun up some brand new instance from Vultr to run some benchmarks on. All instances were 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 (8 GB, 4 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Last Benchmarked | Sat, 23 May 2026 11:00:52 GMT | Sun, 24 May 2026 08: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 | $6.00 |
| RAM (GB) | 8 | 1 |
| CPU Cores | 4 | 1 |
| Storage (TB) | 160 | 25 |
| Storage Type | SSD | NVMe |
| Transfer (TB) | 4 | 2 |
CPU
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Vendor | GenuineIntel | GenuineIntel |
| Model Name | Intel Xeon Processor (Skylake, IBRS) | Intel Xeon Processor (Cascadelake) |
| Clock Speed (MHz) | 2,593.90 | 2,992.91 |
| CPU Cache Size (KB) | 16,384.00 | 16,384.00 |
| BogoMips | 5,187.80 | 5,985.82 |
| Events per Second | 1,100.82 | 1,183.29 |
| Minimum Latency (ms) | 0.88 | 0.81 |
| Average Latency (ms) | 0.91 | 0.84 |
| Maximum Latency (ms) | 1.56 | 2.96 |
| 95th Percentile Latency (ms) | 0.97 | 0.9 |
Memory
Memory Read
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Operations per second | 3,685,781.23 | 5,550,903.11 |
| Mebibytes per second | 3,599.40 | 5,420.80 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 1.03 | 0.53 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Operations per second | 3,590,629.63 | 5,562,286.73 |
| Mebibytes per second | 3,506.47 | 5,431.92 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 1.16 | 0.69 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Reads per Second | 4,999.39 | 4,485.73 |
| Writes per Second | 3,332.93 | 2,990.49 |
| Fsyncs per Second | 10,670.47 | 9,581.36 |
| Read Mebibytes per Second | 78.12 | 70.09 |
| Written Mebibytes per Second | 52.08 | 46.73 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.05 | 0.06 |
| Maximum Latency (ms) | 37.52 | 2.01 |
| 95th Percentile Latency (ms) | 0.18 | 0.16 |
Mutex
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Minimum Latency (ms) | 369.37 | 1,462.47 |
| Average Latency (ms) | 416.22 | 1,470.85 |
| Maximum Latency (ms) | 441.77 | 1,477.99 |
| 95th Percentile Latency (ms) | 442.73 | 1,479.41 |
MySQL
MySQL Read-only
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 5,144.00 | 8,773.00 |
| Queries per second | 51,440.00 | 87,730.00 |
| Minimum Latency (ms) | 1.72 | 1.04 |
| Average Latency (ms) | 1.94 | 1.14 |
| Maximum Latency (ms) | 7.67 | 5.61 |
| 95th Percentile Latency (ms) | 2.35 | 1.3 |
MySQL Write-only
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 5,108.00 | 8,769.00 |
| Queries per second | 51,080.00 | 87,690.00 |
| Minimum Latency (ms) | 1.15 | 0.76 |
| Average Latency (ms) | 1.96 | 1.14 |
| Maximum Latency (ms) | 12.52 | 6.14 |
| 95th Percentile Latency (ms) | 2.71 | 1.58 |
MySQL Read/Write
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 2,247.00 | 3,792.00 |
| Queries per second | 22,470.00 | 37,920.00 |
| Minimum Latency (ms) | 3.08 | 2.12 |
| Average Latency (ms) | 4.45 | 2.64 |
| Maximum Latency (ms) | 29.7 | 6.11 |
| 95th Percentile Latency (ms) | 5.28 | 3.19 |
MySQL INSERT
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 7,630.00 | 15,597.00 |
| Queries per second | 76,300.00 | 155,970.00 |
| Minimum Latency (ms) | 0.71 | 0.44 |
| Average Latency (ms) | 1.31 | 0.64 |
| Maximum Latency (ms) | 29.81 | 12.55 |
| 95th Percentile Latency (ms) | 1.55 | 0.84 |
MySQL Bulk INSERT
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 898,571.00 | 1,463,217.00 |
| Queries per second | 8,985,710.00 | 14,632,170.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0.01 |
| Maximum Latency (ms) | 505.86 | 343.43 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 149,465.00 | 233,708.00 |
| Queries per second | 1,494,650.00 | 2,337,080.00 |
| Minimum Latency (ms) | 0.05 | 0.04 |
| Average Latency (ms) | 0.07 | 0.04 |
| Maximum Latency (ms) | 1.22 | 3.94 |
| 95th Percentile Latency (ms) | 0.09 | 0.06 |
MySQL SELECT (Random Points)
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 4,249.00 | 7,685.00 |
| Queries per second | 42,490.00 | 76,850.00 |
| Minimum Latency (ms) | 0.83 | 0.46 |
| Average Latency (ms) | 2.35 | 1.3 |
| Maximum Latency (ms) | 6.6 | 5.35 |
| 95th Percentile Latency (ms) | 3.02 | 1.7 |
MySQL SELECT (Random Ranges)
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 2,637.00 | 8,363.00 |
| Queries per second | 26,370.00 | 83,630.00 |
| Minimum Latency (ms) | 0.94 | 0.47 |
| Average Latency (ms) | 3.79 | 1.19 |
| Maximum Latency (ms) | 6.3 | 3.3 |
| 95th Percentile Latency (ms) | 5.09 | 1.55 |
MySQL UPDATE (Indexed)
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 7,166.00 | 14,752.00 |
| Queries per second | 71,660.00 | 147,520.00 |
| Minimum Latency (ms) | 0.7 | 0.45 |
| Average Latency (ms) | 1.39 | 0.68 |
| Maximum Latency (ms) | 28.84 | 4.04 |
| 95th Percentile Latency (ms) | 1.79 | 1.03 |
MySQL UPDATE (Non-Indexed)
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 7,661.00 | 15,655.00 |
| Queries per second | 76,610.00 | 156,550.00 |
| Minimum Latency (ms) | 0.7 | 0.44 |
| Average Latency (ms) | 1.3 | 0.64 |
| Maximum Latency (ms) | 33.97 | 4.17 |
| 95th Percentile Latency (ms) | 1.58 | 0.84 |
MySQL DELETE
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 69,690.00 | 134,815.00 |
| Queries per second | 696,900.00 | 1,348,150.00 |
| Minimum Latency (ms) | 0.05 | 0.04 |
| Average Latency (ms) | 0.14 | 0.07 |
| Maximum Latency (ms) | 27.73 | 12.02 |
| 95th Percentile Latency (ms) | 0.87 | 0.13 |
Redis
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| PING_INLINE per Second | 54,436.58 | 48,875.86 |
| PING_MBULK per Second | 48,828.12 | 50,530.57 |
| SET per Second | 51,572.98 | 49,285.36 |
| GET per Second | 48,239.27 | 49,950.05 |
| INCR per Second | 52,328.62 | 50,530.57 |
| LPUSH per Second | 45,454.54 | 47,573.74 |
| RPUSH per Second | 49,751.24 | 47,846.89 |
| LPOP per Second | 53,390.28 | 47,147.57 |
| RPOP per Second | 53,648.07 | 46,082.95 |
| SADD per Second | 48,285.85 | 46,641.79 |
| HSET per Second | 51,493.30 | 46,382.19 |
| SPOP per Second | 52,910.05 | 48,995.59 |
| ZADD per Second | 53,504.55 | 48,732.94 |
| ZPOPMIN per Second | 53,590.57 | 49,800.80 |
| LRANGE_100 (first 100 elements) per Second | 28,645.09 | 31,269.54 |
| LRANGE_300 (first 300 elements) per Second | 13,131.98 | 16,488.05 |
| LRANGE_500 (first 500 elements) per Second | 8,529.51 | 11,064.39 |
| LRANGE_600 (first 600 elements) per Second | 7,479.99 | 9,430.40 |
| MSET (10 keys) per Second | 49,212.60 | 43,898.15 |
Redis Average Latency (ms)
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| PING_INLINE | 0.47 | 0.67 |
| PING_MBULK | 0.53 | 0.65 |
| SET | 0.50 | 0.67 |
| GET | 0.54 | 0.66 |
| INCR | 0.49 | 0.66 |
| LPUSH | 0.58 | 0.70 |
| RPUSH | 0.52 | 0.69 |
| LPOP | 0.49 | 0.71 |
| RPOP | 0.48 | 0.72 |
| SADD | 0.54 | 0.70 |
| HSET | 0.53 | 0.72 |
| SPOP | 0.49 | 0.67 |
| ZADD | 0.48 | 0.68 |
| ZPOPMIN | 0.48 | 0.66 |
| LRANGE_100 (first 100 elements) | 0.91 | 1.09 |
| LRANGE_300 (first 300 elements) | 1.94 | 2.16 |
| LRANGE_500 (first 500 elements) | 3.00 | 3.20 |
| LRANGE_600 (first 600 elements) | 3.43 | 3.76 |
| MSET (10 keys) | 0.77 | 0.77 |
Conclusion
From the friendly robots:
Upon comparison of Vultr's Cloud Compute (8 GB, 4 Cores) and High Performance Intel (1 GB) instances, the former shows stronger performance across a broad range of metrics, especially in CPU-intensive tasks, memory operations, and I/O throughput, likely due to its higher core count and more substantial memory allocation. The 8 GB, 4 Cores instance demonstrates superior results in Redis benchmarks, CPU processing, and file I/O operations, making it a more suitable choice for demanding workloads requiring substantial computational and memory resources. In contrast, the High Performance Intel (1 GB) instance, while still competent, excels in scenarios where lower resource consumption is acceptable, such as lightweight tasks, small databases, or less memory-intensive operations, due to its lower cost and adequate but not exceptional performance metrics.
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.