Vultr Cloud Compute (4 GB, 2 Cores) vs. Vultr High Performance Intel (8 GB, 4 Cores)
New day, new benchmarks. Today I've spun up some brand new instance from Vultr and did some benchmarking. Each instance was spun up with Ubuntu 24.04 LTS x64 and all resided in or around the New York / New Jersey area. Let's get into the numbers.
Overview
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Last Benchmarked | Thu, 11 Jun 2026 09:00:52 GMT | Fri, 12 Jun 2026 23: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 | 4 |
| Storage (TB) | 80 | 180 |
| Storage Type | SSD | NVMe |
| Transfer (TB) | 3 | 6 |
CPU
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Vendor | GenuineIntel | GenuineIntel |
| Model Name | Intel Xeon Processor (Skylake, IBRS) | Intel Xeon Processor (Cascadelake) |
| Clock Speed (MHz) | 2,593.91 | 2,893.20 |
| CPU Cache Size (KB) | 16,384.00 | 16,384.00 |
| BogoMips | 5,187.81 | 5,786.40 |
| Events per Second | 1,022.39 | 1,168.11 |
| Minimum Latency (ms) | 0.88 | 0.83 |
| Average Latency (ms) | 0.98 | 0.86 |
| Maximum Latency (ms) | 1.77 | 1.23 |
| 95th Percentile Latency (ms) | 1.21 | 0.9 |
Memory
Memory Read
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Operations per second | 3,523,809.57 | 5,319,337.14 |
| Mebibytes per second | 3,441.22 | 5,194.67 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.22 | 0.65 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Operations per second | 3,568,203.77 | 5,408,977.53 |
| Mebibytes per second | 3,484.57 | 5,282.20 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 1.02 | 0.2 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Reads per Second | 2,972.63 | 9,215.72 |
| Writes per Second | 1,981.75 | 6,143.81 |
| Fsyncs per Second | 6,347.81 | 19,665.40 |
| Read Mebibytes per Second | 46.45 | 144.00 |
| Written Mebibytes per Second | 30.96 | 96.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.09 | 0.03 |
| Maximum Latency (ms) | 17.12 | 2.79 |
| 95th Percentile Latency (ms) | 0.33 | 0.09 |
Mutex
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 899.28 | 348.34 |
| Average Latency (ms) | 935.93 | 380.98 |
| Maximum Latency (ms) | 969.92 | 399.75 |
| 95th Percentile Latency (ms) | 977.74 | 397.39 |
MySQL
MySQL Read-only
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 3,779.00 | 7,886.00 |
| Queries per second | 37,790.00 | 78,860.00 |
| Minimum Latency (ms) | 1.84 | 1.11 |
| Average Latency (ms) | 2.64 | 1.27 |
| Maximum Latency (ms) | 24.55 | 3.02 |
| 95th Percentile Latency (ms) | 3.82 | 1.5 |
MySQL Write-only
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 4,044.00 | 8,912.00 |
| Queries per second | 40,440.00 | 89,120.00 |
| Minimum Latency (ms) | 1.4 | 0.78 |
| Average Latency (ms) | 2.47 | 1.12 |
| Maximum Latency (ms) | 13.46 | 3.45 |
| 95th Percentile Latency (ms) | 3.3 | 1.37 |
MySQL Read/Write
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 1,798.00 | 4,044.00 |
| Queries per second | 17,980.00 | 40,440.00 |
| Minimum Latency (ms) | 3.86 | 1.99 |
| Average Latency (ms) | 5.56 | 2.47 |
| Maximum Latency (ms) | 27.33 | 5.78 |
| 95th Percentile Latency (ms) | 6.91 | 3.13 |
MySQL INSERT
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 6,405.00 | 17,011.00 |
| Queries per second | 64,050.00 | 170,110.00 |
| Minimum Latency (ms) | 0.99 | 0.41 |
| Average Latency (ms) | 1.56 | 0.59 |
| Maximum Latency (ms) | 15.15 | 3.53 |
| 95th Percentile Latency (ms) | 2.03 | 0.74 |
MySQL Bulk INSERT
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 865,805.00 | 1,783,592.00 |
| Queries per second | 8,658,050.00 | 17,835,920.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0.01 |
| Maximum Latency (ms) | 538.25 | 264.69 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 126,618.00 | 200,062.00 |
| Queries per second | 1,266,180.00 | 2,000,620.00 |
| Minimum Latency (ms) | 0.05 | 0.03 |
| Average Latency (ms) | 0.08 | 0.05 |
| Maximum Latency (ms) | 2.46 | 0.66 |
| 95th Percentile Latency (ms) | 0.11 | 0.07 |
MySQL SELECT (Random Points)
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 3,674.00 | 7,946.00 |
| Queries per second | 36,740.00 | 79,460.00 |
| Minimum Latency (ms) | 1.07 | 0.44 |
| Average Latency (ms) | 2.72 | 1.26 |
| Maximum Latency (ms) | 6.45 | 3.84 |
| 95th Percentile Latency (ms) | 3.55 | 1.67 |
MySQL SELECT (Random Ranges)
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 2,728.00 | 7,912.00 |
| Queries per second | 27,280.00 | 79,120.00 |
| Minimum Latency (ms) | 1.3 | 0.29 |
| Average Latency (ms) | 3.66 | 1.26 |
| Maximum Latency (ms) | 11.85 | 3.71 |
| 95th Percentile Latency (ms) | 5 | 1.7 |
MySQL UPDATE (Indexed)
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 5,438.00 | 16,005.00 |
| Queries per second | 54,380.00 | 160,050.00 |
| Minimum Latency (ms) | 0.99 | 0.41 |
| Average Latency (ms) | 1.84 | 0.62 |
| Maximum Latency (ms) | 13.86 | 9.15 |
| 95th Percentile Latency (ms) | 2.71 | 0.81 |
MySQL UPDATE (Non-Indexed)
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 6,370.00 | 16,608.00 |
| Queries per second | 63,700.00 | 166,080.00 |
| Minimum Latency (ms) | 1.01 | 0.4 |
| Average Latency (ms) | 1.57 | 0.6 |
| Maximum Latency (ms) | 8.99 | 2.36 |
| 95th Percentile Latency (ms) | 2.07 | 0.77 |
MySQL DELETE
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 51,180.00 | 145,717.00 |
| Queries per second | 511,800.00 | 1,457,170.00 |
| Minimum Latency (ms) | 0.05 | 0.03 |
| Average Latency (ms) | 0.19 | 0.07 |
| Maximum Latency (ms) | 6.11 | 3.66 |
| 95th Percentile Latency (ms) | 1.39 | 0.09 |
Redis
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| PING_INLINE per Second | 49,677.10 | 65,876.16 |
| PING_MBULK per Second | 45,372.05 | 64,432.99 |
| SET per Second | 45,392.64 | 67,385.45 |
| GET per Second | 53,163.21 | 66,181.34 |
| INCR per Second | 48,732.94 | 66,401.06 |
| LPUSH per Second | 50,327.12 | 65,231.57 |
| RPUSH per Second | 48,285.85 | 65,402.22 |
| LPOP per Second | 48,355.90 | 65,876.16 |
| RPOP per Second | 51,413.88 | 66,181.34 |
| SADD per Second | 48,332.53 | 65,274.15 |
| HSET per Second | 49,285.36 | 64,850.84 |
| SPOP per Second | 48,332.53 | 65,530.80 |
| ZADD per Second | 51,229.51 | 62,972.29 |
| ZPOPMIN per Second | 45,085.66 | 62,695.92 |
| LRANGE_100 (first 100 elements) per Second | 27,122.32 | 48,995.59 |
| LRANGE_300 (first 300 elements) per Second | 12,442.45 | 28,801.84 |
| LRANGE_500 (first 500 elements) per Second | 7,930.21 | 19,845.21 |
| LRANGE_600 (first 600 elements) per Second | 6,902.74 | 17,568.52 |
| MSET (10 keys) per Second | 45,146.73 | 64,641.24 |
Redis Average Latency (ms)
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| PING_INLINE | 0.53 | 0.40 |
| PING_MBULK | 0.57 | 0.40 |
| SET | 0.57 | 0.41 |
| GET | 0.49 | 0.39 |
| INCR | 0.53 | 0.39 |
| LPUSH | 0.51 | 0.40 |
| RPUSH | 0.54 | 0.39 |
| LPOP | 0.54 | 0.39 |
| RPOP | 0.52 | 0.39 |
| SADD | 0.55 | 0.39 |
| HSET | 0.54 | 0.41 |
| SPOP | 0.54 | 0.40 |
| ZADD | 0.52 | 0.42 |
| ZPOPMIN | 0.57 | 0.41 |
| LRANGE_100 (first 100 elements) | 1.02 | 0.56 |
| LRANGE_300 (first 300 elements) | 2.29 | 0.93 |
| LRANGE_500 (first 500 elements) | 3.27 | 1.35 |
| LRANGE_600 (first 600 elements) | 3.91 | 1.54 |
| MSET (10 keys) | 0.78 | 0.41 |
Conclusion
From the friendly robots:
Based on the benchmark results, the Vultr High Performance Intel (8 GB, 4 Cores) instance clearly outperforms the Cloud Compute (4 GB, 2 Cores) in most metrics. The High Performance instance shows significantly higher RPS and throughput values for Redis operations, CPU events, file I/O, and MySQL performance. This makes it ideal for CPU-intensive and I/O-heavy workloads, providing much better scalability and performance for applications requiring more resources. The Cloud Compute instance, while competent for lighter tasks, falls short in multi-core processing and large memory operations, making it more suitable for smaller, less demanding applications where cost is a primary concern.
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.