Vultr Cloud Compute (4 GB, 2 Cores) vs. Vultr High Performance Intel (4 GB, 2 Cores)
Same showdown, different day. Today I've spun up brand new instance from Vultr and ran my world famous suite of benchmarking scripts. Each instance was spun up with 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 (4 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Last Benchmarked | Thu, 11 Jun 2026 09:00:52 GMT | Wed, 10 Jun 2026 17: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 | $24.00 |
| RAM (GB) | 4 | 4 |
| CPU Cores | 2 | 2 |
| Storage (TB) | 80 | 100 |
| Storage Type | SSD | NVMe |
| Transfer (TB) | 3 | 5 |
CPU
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 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,170.45 |
| Minimum Latency (ms) | 0.88 | 0.83 |
| Average Latency (ms) | 0.98 | 0.85 |
| Maximum Latency (ms) | 1.77 | 2.19 |
| 95th Percentile Latency (ms) | 1.21 | 0.89 |
Memory
Memory Read
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 3,523,809.57 | 5,381,090.35 |
| Mebibytes per second | 3,441.22 | 5,254.97 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.22 | 0.66 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 3,568,203.77 | 5,340,100.00 |
| Mebibytes per second | 3,484.57 | 5,214.94 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 1.02 | 3.45 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Reads per Second | 2,972.63 | 8,758.71 |
| Writes per Second | 1,981.75 | 5,839.10 |
| Fsyncs per Second | 6,347.81 | 18,689.29 |
| Read Mebibytes per Second | 46.45 | 136.85 |
| Written Mebibytes per Second | 30.96 | 91.24 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.09 | 0.03 |
| Maximum Latency (ms) | 17.12 | 1.64 |
| 95th Percentile Latency (ms) | 0.33 | 0.09 |
Mutex
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 899.28 | 754.58 |
| Average Latency (ms) | 935.93 | 772.18 |
| Maximum Latency (ms) | 969.92 | 791.88 |
| 95th Percentile Latency (ms) | 977.74 | 787.74 |
MySQL
MySQL Read-only
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 3,779.00 | 8,009.00 |
| Queries per second | 37,790.00 | 80,090.00 |
| Minimum Latency (ms) | 1.84 | 1.09 |
| Average Latency (ms) | 2.64 | 1.25 |
| Maximum Latency (ms) | 24.55 | 7.52 |
| 95th Percentile Latency (ms) | 3.82 | 1.5 |
MySQL Write-only
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 4,044.00 | 10,028.00 |
| Queries per second | 40,440.00 | 100,280.00 |
| Minimum Latency (ms) | 1.4 | 0.72 |
| Average Latency (ms) | 2.47 | 1 |
| Maximum Latency (ms) | 13.46 | 2.99 |
| 95th Percentile Latency (ms) | 3.3 | 1.3 |
MySQL Read/Write
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 1,798.00 | 4,291.00 |
| Queries per second | 17,980.00 | 42,910.00 |
| Minimum Latency (ms) | 3.86 | 1.94 |
| Average Latency (ms) | 5.56 | 2.33 |
| Maximum Latency (ms) | 27.33 | 4.57 |
| 95th Percentile Latency (ms) | 6.91 | 2.81 |
MySQL INSERT
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 6,405.00 | 18,803.00 |
| Queries per second | 64,050.00 | 188,030.00 |
| Minimum Latency (ms) | 0.99 | 0.39 |
| Average Latency (ms) | 1.56 | 0.53 |
| Maximum Latency (ms) | 15.15 | 2.51 |
| 95th Percentile Latency (ms) | 2.03 | 0.65 |
MySQL Bulk INSERT
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 865,805.00 | 1,725,342.00 |
| Queries per second | 8,658,050.00 | 17,253,420.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0.01 |
| Maximum Latency (ms) | 538.25 | 270.86 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 126,618.00 | 207,252.00 |
| Queries per second | 1,266,180.00 | 2,072,520.00 |
| Minimum Latency (ms) | 0.05 | 0.03 |
| Average Latency (ms) | 0.08 | 0.05 |
| Maximum Latency (ms) | 2.46 | 0.83 |
| 95th Percentile Latency (ms) | 0.11 | 0.06 |
MySQL SELECT (Random Points)
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 3,674.00 | 8,237.00 |
| Queries per second | 36,740.00 | 82,370.00 |
| Minimum Latency (ms) | 1.07 | 0.49 |
| Average Latency (ms) | 2.72 | 1.21 |
| Maximum Latency (ms) | 6.45 | 3.12 |
| 95th Percentile Latency (ms) | 3.55 | 1.55 |
MySQL SELECT (Random Ranges)
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 2,728.00 | 7,858.00 |
| Queries per second | 27,280.00 | 78,580.00 |
| Minimum Latency (ms) | 1.3 | 0.48 |
| Average Latency (ms) | 3.66 | 1.27 |
| Maximum Latency (ms) | 11.85 | 3.3 |
| 95th Percentile Latency (ms) | 5 | 1.7 |
MySQL UPDATE (Indexed)
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 5,438.00 | 17,356.00 |
| Queries per second | 54,380.00 | 173,560.00 |
| Minimum Latency (ms) | 0.99 | 0.41 |
| Average Latency (ms) | 1.84 | 0.58 |
| Maximum Latency (ms) | 13.86 | 10.49 |
| 95th Percentile Latency (ms) | 2.71 | 0.77 |
MySQL UPDATE (Non-Indexed)
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 6,370.00 | 18,406.00 |
| Queries per second | 63,700.00 | 184,060.00 |
| Minimum Latency (ms) | 1.01 | 0.4 |
| Average Latency (ms) | 1.57 | 0.54 |
| Maximum Latency (ms) | 8.99 | 2.04 |
| 95th Percentile Latency (ms) | 2.07 | 0.69 |
MySQL DELETE
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 51,180.00 | 155,987.00 |
| Queries per second | 511,800.00 | 1,559,870.00 |
| Minimum Latency (ms) | 0.05 | 0.03 |
| Average Latency (ms) | 0.19 | 0.06 |
| Maximum Latency (ms) | 6.11 | 1.23 |
| 95th Percentile Latency (ms) | 1.39 | 0.08 |
Redis
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE per Second | 49,677.10 | 65,876.16 |
| PING_MBULK per Second | 45,372.05 | 64,557.78 |
| SET per Second | 45,392.64 | 62,266.50 |
| GET per Second | 53,163.21 | 50,075.11 |
| INCR per Second | 48,732.94 | 53,390.28 |
| LPUSH per Second | 50,327.12 | 62,344.14 |
| RPUSH per Second | 48,285.85 | 67,294.75 |
| LPOP per Second | 48,355.90 | 68,917.99 |
| RPOP per Second | 51,413.88 | 68,352.70 |
| SADD per Second | 48,332.53 | 67,385.45 |
| HSET per Second | 49,285.36 | 69,013.11 |
| SPOP per Second | 48,332.53 | 68,446.27 |
| ZADD per Second | 51,229.51 | 68,587.11 |
| ZPOPMIN per Second | 45,085.66 | 68,587.11 |
| LRANGE_100 (first 100 elements) per Second | 27,122.32 | 52,137.64 |
| LRANGE_300 (first 300 elements) per Second | 12,442.45 | 27,300.03 |
| LRANGE_500 (first 500 elements) per Second | 7,930.21 | 19,681.17 |
| LRANGE_600 (first 600 elements) per Second | 6,902.74 | 17,664.72 |
| MSET (10 keys) per Second | 45,146.73 | 68,681.32 |
Redis Average Latency (ms)
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE | 0.53 | 0.40 |
| PING_MBULK | 0.57 | 0.40 |
| SET | 0.57 | 0.41 |
| GET | 0.49 | 0.52 |
| INCR | 0.53 | 0.49 |
| LPUSH | 0.51 | 0.42 |
| RPUSH | 0.54 | 0.38 |
| LPOP | 0.54 | 0.37 |
| RPOP | 0.52 | 0.38 |
| SADD | 0.55 | 0.38 |
| HSET | 0.54 | 0.37 |
| SPOP | 0.54 | 0.38 |
| ZADD | 0.52 | 0.38 |
| ZPOPMIN | 0.57 | 0.38 |
| LRANGE_100 (first 100 elements) | 1.02 | 0.50 |
| LRANGE_300 (first 300 elements) | 2.29 | 0.94 |
| LRANGE_500 (first 500 elements) | 3.27 | 1.32 |
| LRANGE_600 (first 600 elements) | 3.91 | 1.48 |
| MSET (10 keys) | 0.78 | 0.38 |
Conclusion
From the friendly robots:
In comparing the benchmark performance of Vultr's two instances, the High Performance Intel (4 GB, 2 Cores) generally outperforms the Cloud Compute (4 GB, 2 Cores) in most metrics. The High Performance variant shows higher RPS rates in Redis operations, lower latencies across a wide range of tasks, and better throughput and read speeds in file IO. Both instances perform similarly in CPU-bound tasks and memory operations, but the High Performance instance has a slight edge in handling MySQL workloads. Given these results, the High Performance Intel variant is recommended for use cases that benefit from higher throughput, lower latencies, and better I/O performance, such as high-traffic web applications, databases, and other CPU-intensive and I/O-heavy workloads. The Cloud Compute instance, while still capable, might be more suitable for lighter workloads 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.