Vultr Cloud Compute (8 GB, 4 Cores) vs. Vultr High Performance Intel (2 GB)
New day, new benchmarks. Today I've spun up brand new instance from Vultr and did some benchmarking. All instances were spun up with Ubuntu 24.04 LTS x64 and all resided in or around the New York / New Jersey area. Without further ado, here's the results.
Overview
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Last Benchmarked | Sat, 23 May 2026 11:00:52 GMT | Sat, 23 May 2026 01: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 | $12.00 |
| RAM (GB) | 8 | 2 |
| CPU Cores | 4 | 1 |
| Storage (TB) | 160 | 50 |
| Storage Type | SSD | NVMe |
| Transfer (TB) | 4 | 3 |
CPU
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Vendor | GenuineIntel | GenuineIntel |
| Model Name | Intel Xeon Processor (Skylake, IBRS) | Intel Xeon Processor (Cascadelake) |
| Clock Speed (MHz) | 2,593.90 | 2,992.93 |
| CPU Cache Size (KB) | 16,384.00 | 16,384.00 |
| BogoMips | 5,187.80 | 5,985.85 |
| Events per Second | 1,100.82 | 1,186.78 |
| Minimum Latency (ms) | 0.88 | 0.81 |
| Average Latency (ms) | 0.91 | 0.84 |
| Maximum Latency (ms) | 1.56 | 2.59 |
| 95th Percentile Latency (ms) | 0.97 | 0.92 |
Memory
Memory Read
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Operations per second | 3,685,781.23 | 5,529,814.46 |
| Mebibytes per second | 3,599.40 | 5,400.21 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 1.03 | 1.19 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Operations per second | 3,590,629.63 | 5,462,628.68 |
| Mebibytes per second | 3,506.47 | 5,334.60 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 1.16 | 0.31 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Reads per Second | 4,999.39 | 4,806.76 |
| Writes per Second | 3,332.93 | 3,204.44 |
| Fsyncs per Second | 10,670.47 | 10,258.69 |
| Read Mebibytes per Second | 78.12 | 75.11 |
| Written Mebibytes per Second | 52.08 | 50.07 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.05 | 0.05 |
| Maximum Latency (ms) | 37.52 | 2.63 |
| 95th Percentile Latency (ms) | 0.18 | 0.16 |
Mutex
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Minimum Latency (ms) | 369.37 | 1,492.82 |
| Average Latency (ms) | 416.22 | 1,499.43 |
| Maximum Latency (ms) | 441.77 | 1,510.35 |
| 95th Percentile Latency (ms) | 442.73 | 1,506.29 |
MySQL
MySQL Read-only
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 5,144.00 | 8,607.00 |
| Queries per second | 51,440.00 | 86,070.00 |
| Minimum Latency (ms) | 1.72 | 1.04 |
| Average Latency (ms) | 1.94 | 1.16 |
| Maximum Latency (ms) | 7.67 | 3.64 |
| 95th Percentile Latency (ms) | 2.35 | 1.47 |
MySQL Write-only
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 5,108.00 | 8,446.00 |
| Queries per second | 51,080.00 | 84,460.00 |
| Minimum Latency (ms) | 1.15 | 0.79 |
| Average Latency (ms) | 1.96 | 1.18 |
| Maximum Latency (ms) | 12.52 | 5.36 |
| 95th Percentile Latency (ms) | 2.71 | 1.67 |
MySQL Read/Write
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 2,247.00 | 3,136.00 |
| Queries per second | 22,470.00 | 31,360.00 |
| Minimum Latency (ms) | 3.08 | 2.12 |
| Average Latency (ms) | 4.45 | 3.19 |
| Maximum Latency (ms) | 29.7 | 236.46 |
| 95th Percentile Latency (ms) | 5.28 | 3.68 |
MySQL INSERT
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 7,630.00 | 16,238.00 |
| Queries per second | 76,300.00 | 162,380.00 |
| Minimum Latency (ms) | 0.71 | 0.44 |
| Average Latency (ms) | 1.31 | 0.61 |
| Maximum Latency (ms) | 29.81 | 10.48 |
| 95th Percentile Latency (ms) | 1.55 | 0.77 |
MySQL Bulk INSERT
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 898,571.00 | 1,434,092.00 |
| Queries per second | 8,985,710.00 | 14,340,920.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0.01 |
| Maximum Latency (ms) | 505.86 | 312.94 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 149,465.00 | 234,474.00 |
| Queries per second | 1,494,650.00 | 2,344,740.00 |
| Minimum Latency (ms) | 0.05 | 0.04 |
| Average Latency (ms) | 0.07 | 0.04 |
| Maximum Latency (ms) | 1.22 | 1.61 |
| 95th Percentile Latency (ms) | 0.09 | 0.06 |
MySQL SELECT (Random Points)
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 4,249.00 | 7,270.00 |
| Queries per second | 42,490.00 | 72,700.00 |
| Minimum Latency (ms) | 0.83 | 0.49 |
| Average Latency (ms) | 2.35 | 1.37 |
| Maximum Latency (ms) | 6.6 | 3.96 |
| 95th Percentile Latency (ms) | 3.02 | 1.82 |
MySQL SELECT (Random Ranges)
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 2,637.00 | 7,760.00 |
| Queries per second | 26,370.00 | 77,600.00 |
| Minimum Latency (ms) | 0.94 | 0.38 |
| Average Latency (ms) | 3.79 | 1.29 |
| Maximum Latency (ms) | 6.3 | 5.21 |
| 95th Percentile Latency (ms) | 5.09 | 1.76 |
MySQL UPDATE (Indexed)
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 7,166.00 | 15,196.00 |
| Queries per second | 71,660.00 | 151,960.00 |
| Minimum Latency (ms) | 0.7 | 0.42 |
| Average Latency (ms) | 1.39 | 0.66 |
| Maximum Latency (ms) | 28.84 | 3.55 |
| 95th Percentile Latency (ms) | 1.79 | 0.9 |
MySQL UPDATE (Non-Indexed)
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 7,661.00 | 15,874.00 |
| Queries per second | 76,610.00 | 158,740.00 |
| Minimum Latency (ms) | 0.7 | 0.41 |
| Average Latency (ms) | 1.3 | 0.63 |
| Maximum Latency (ms) | 33.97 | 2.86 |
| 95th Percentile Latency (ms) | 1.58 | 0.81 |
MySQL DELETE
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 69,690.00 | 145,934.00 |
| Queries per second | 696,900.00 | 1,459,340.00 |
| Minimum Latency (ms) | 0.05 | 0.04 |
| Average Latency (ms) | 0.14 | 0.07 |
| Maximum Latency (ms) | 27.73 | 2.52 |
| 95th Percentile Latency (ms) | 0.87 | 0.12 |
Redis
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| PING_INLINE per Second | 54,436.58 | 48,732.94 |
| PING_MBULK per Second | 48,828.12 | 46,992.48 |
| SET per Second | 51,572.98 | 47,755.49 |
| GET per Second | 48,239.27 | 48,030.74 |
| INCR per Second | 52,328.62 | 47,938.64 |
| LPUSH per Second | 45,454.54 | 47,483.38 |
| RPUSH per Second | 49,751.24 | 47,460.84 |
| LPOP per Second | 53,390.28 | 46,253.47 |
| RPOP per Second | 53,648.07 | 46,641.79 |
| SADD per Second | 48,285.85 | 48,216.01 |
| HSET per Second | 51,493.30 | 48,192.77 |
| SPOP per Second | 52,910.05 | 49,140.05 |
| ZADD per Second | 53,504.55 | 49,067.71 |
| ZPOPMIN per Second | 53,590.57 | 50,025.02 |
| LRANGE_100 (first 100 elements) per Second | 28,645.09 | 30,826.14 |
| LRANGE_300 (first 300 elements) per Second | 13,131.98 | 16,716.82 |
| LRANGE_500 (first 500 elements) per Second | 8,529.51 | 11,281.59 |
| LRANGE_600 (first 600 elements) per Second | 7,479.99 | 9,350.16 |
| MSET (10 keys) per Second | 49,212.60 | 44,247.79 |
Redis Average Latency (ms)
| Vultr – Cloud Compute (8 GB, 4 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| PING_INLINE | 0.47 | 0.68 |
| PING_MBULK | 0.53 | 0.70 |
| SET | 0.50 | 0.70 |
| GET | 0.54 | 0.69 |
| INCR | 0.49 | 0.69 |
| LPUSH | 0.58 | 0.70 |
| RPUSH | 0.52 | 0.70 |
| LPOP | 0.49 | 0.72 |
| RPOP | 0.48 | 0.71 |
| SADD | 0.54 | 0.69 |
| HSET | 0.53 | 0.69 |
| SPOP | 0.49 | 0.67 |
| ZADD | 0.48 | 0.69 |
| ZPOPMIN | 0.48 | 0.66 |
| LRANGE_100 (first 100 elements) | 0.91 | 1.12 |
| LRANGE_300 (first 300 elements) | 1.94 | 2.17 |
| LRANGE_500 (first 500 elements) | 3.00 | 3.19 |
| LRANGE_600 (first 600 elements) | 3.43 | 3.82 |
| MSET (10 keys) | 0.77 | 0.78 |
Conclusion
From the friendly robots:
Comparing the Vultr Cloud Compute (8 GB, 4 Cores) and the Vultr High Performance Intel (2 GB) instances, the former excels in high concurrency Redis operations, showing strong performance in commands like GET, SET, and LPUSH with high requests per second and low latency, ideal for memory-intensive applications and services requiring substantial RAM and CPU cores. The High Performance Intel instance, though with lower RAM and a single core, still performs admirably in Redis operations and provides notable throughput in file I/O tasks, making it a cost-effective choice for applications that do not require extensive memory or multi-core processing but benefit from faster NVMe storage and lower latency in single-threaded workloads. The best choice depends on the specific needs of your application, whether it's CPU and memory-intensive operations or optimized file handling with single-threaded efficiency.
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.