Vultr Cloud Compute (4 GB, 2 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 and ran some benchmarks. Each instance was running Ubuntu 24.04 LTS x64 and were created in or around the New York / New Jersey area. Enough talk. Here's the data.
Overview
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Last Benchmarked | Thu, 11 Jun 2026 09:00:52 GMT | Fri, 12 Jun 2026 05: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 | $6.00 |
| RAM (GB) | 4 | 1 |
| CPU Cores | 2 | 1 |
| Storage (TB) | 80 | 25 |
| Storage Type | SSD | NVMe |
| Transfer (TB) | 3 | 2 |
CPU
| Vultr – Cloud Compute (4 GB, 2 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.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,174.56 |
| Minimum Latency (ms) | 0.88 | 0.83 |
| Average Latency (ms) | 0.98 | 0.85 |
| Maximum Latency (ms) | 1.77 | 2.85 |
| 95th Percentile Latency (ms) | 1.21 | 0.87 |
Memory
Memory Read
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Operations per second | 3,523,809.57 | 5,460,667.93 |
| Mebibytes per second | 3,441.22 | 5,332.68 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.22 | 0.21 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Operations per second | 3,568,203.77 | 5,475,003.36 |
| Mebibytes per second | 3,484.57 | 5,346.68 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 1.02 | 0.83 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Reads per Second | 2,972.63 | 4,863.26 |
| Writes per Second | 1,981.75 | 3,242.17 |
| Fsyncs per Second | 6,347.81 | 10,379.56 |
| Read Mebibytes per Second | 46.45 | 75.99 |
| Written Mebibytes per Second | 30.96 | 50.66 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.09 | 0.05 |
| Maximum Latency (ms) | 17.12 | 2.02 |
| 95th Percentile Latency (ms) | 0.33 | 0.15 |
Mutex
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Minimum Latency (ms) | 899.28 | 1,468.68 |
| Average Latency (ms) | 935.93 | 1,481.17 |
| Maximum Latency (ms) | 969.92 | 1,487.15 |
| 95th Percentile Latency (ms) | 977.74 | 1,479.41 |
MySQL
MySQL Read-only
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 3,779.00 | 8,891.00 |
| Queries per second | 37,790.00 | 88,910.00 |
| Minimum Latency (ms) | 1.84 | 1.06 |
| Average Latency (ms) | 2.64 | 1.12 |
| Maximum Latency (ms) | 24.55 | 4.46 |
| 95th Percentile Latency (ms) | 3.82 | 1.21 |
MySQL Write-only
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 4,044.00 | 9,408.00 |
| Queries per second | 40,440.00 | 94,080.00 |
| Minimum Latency (ms) | 1.4 | 0.74 |
| Average Latency (ms) | 2.47 | 1.06 |
| Maximum Latency (ms) | 13.46 | 12.96 |
| 95th Percentile Latency (ms) | 3.3 | 1.44 |
MySQL Read/Write
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 1,798.00 | 3,886.00 |
| Queries per second | 17,980.00 | 38,860.00 |
| Minimum Latency (ms) | 3.86 | 2.13 |
| Average Latency (ms) | 5.56 | 2.57 |
| Maximum Latency (ms) | 27.33 | 7.51 |
| 95th Percentile Latency (ms) | 6.91 | 3.02 |
MySQL INSERT
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 6,405.00 | 18,427.00 |
| Queries per second | 64,050.00 | 184,270.00 |
| Minimum Latency (ms) | 0.99 | 0.4 |
| Average Latency (ms) | 1.56 | 0.54 |
| Maximum Latency (ms) | 15.15 | 9.42 |
| 95th Percentile Latency (ms) | 2.03 | 0.68 |
MySQL Bulk INSERT
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 865,805.00 | 1,492,342.00 |
| Queries per second | 8,658,050.00 | 14,923,420.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0.01 |
| Maximum Latency (ms) | 538.25 | 333.65 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 126,618.00 | 234,303.00 |
| Queries per second | 1,266,180.00 | 2,343,030.00 |
| Minimum Latency (ms) | 0.05 | 0.04 |
| Average Latency (ms) | 0.08 | 0.04 |
| Maximum Latency (ms) | 2.46 | 1.19 |
| 95th Percentile Latency (ms) | 0.11 | 0.05 |
MySQL SELECT (Random Points)
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 3,674.00 | 7,673.00 |
| Queries per second | 36,740.00 | 76,730.00 |
| Minimum Latency (ms) | 1.07 | 0.44 |
| Average Latency (ms) | 2.72 | 1.3 |
| Maximum Latency (ms) | 6.45 | 5.53 |
| 95th Percentile Latency (ms) | 3.55 | 1.67 |
MySQL SELECT (Random Ranges)
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 2,728.00 | 8,400.00 |
| Queries per second | 27,280.00 | 84,000.00 |
| Minimum Latency (ms) | 1.3 | 0.42 |
| Average Latency (ms) | 3.66 | 1.19 |
| Maximum Latency (ms) | 11.85 | 2.72 |
| 95th Percentile Latency (ms) | 5 | 1.55 |
MySQL UPDATE (Indexed)
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 5,438.00 | 17,655.00 |
| Queries per second | 54,380.00 | 176,550.00 |
| Minimum Latency (ms) | 0.99 | 0.4 |
| Average Latency (ms) | 1.84 | 0.57 |
| Maximum Latency (ms) | 13.86 | 8.78 |
| 95th Percentile Latency (ms) | 2.71 | 0.78 |
MySQL UPDATE (Non-Indexed)
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 6,370.00 | 18,233.00 |
| Queries per second | 63,700.00 | 182,330.00 |
| Minimum Latency (ms) | 1.01 | 0.4 |
| Average Latency (ms) | 1.57 | 0.55 |
| Maximum Latency (ms) | 8.99 | 5.12 |
| 95th Percentile Latency (ms) | 2.07 | 0.69 |
MySQL DELETE
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 51,180.00 | 147,244.00 |
| Queries per second | 511,800.00 | 1,472,440.00 |
| Minimum Latency (ms) | 0.05 | 0.04 |
| Average Latency (ms) | 0.19 | 0.07 |
| Maximum Latency (ms) | 6.11 | 3.53 |
| 95th Percentile Latency (ms) | 1.39 | 0.12 |
Redis
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| PING_INLINE per Second | 49,677.10 | 47,915.67 |
| PING_MBULK per Second | 45,372.05 | 48,638.13 |
| SET per Second | 45,392.64 | 36,832.41 |
| GET per Second | 53,163.21 | 44,326.24 |
| INCR per Second | 48,732.94 | 49,358.34 |
| LPUSH per Second | 50,327.12 | 49,236.83 |
| RPUSH per Second | 48,285.85 | 49,261.09 |
| LPOP per Second | 48,355.90 | 48,709.21 |
| RPOP per Second | 51,413.88 | 49,382.71 |
| SADD per Second | 48,332.53 | 49,900.20 |
| HSET per Second | 49,285.36 | 48,828.12 |
| SPOP per Second | 48,332.53 | 49,850.45 |
| ZADD per Second | 51,229.51 | 48,709.21 |
| ZPOPMIN per Second | 45,085.66 | 50,075.11 |
| LRANGE_100 (first 100 elements) per Second | 27,122.32 | 31,133.25 |
| LRANGE_300 (first 300 elements) per Second | 12,442.45 | 16,321.20 |
| LRANGE_500 (first 500 elements) per Second | 7,930.21 | 11,234.69 |
| LRANGE_600 (first 600 elements) per Second | 6,902.74 | 9,695.56 |
| MSET (10 keys) per Second | 45,146.73 | 43,994.72 |
Redis Average Latency (ms)
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| PING_INLINE | 0.53 | 0.69 |
| PING_MBULK | 0.57 | 0.69 |
| SET | 0.57 | 0.89 |
| GET | 0.49 | 0.75 |
| INCR | 0.53 | 0.68 |
| LPUSH | 0.51 | 0.69 |
| RPUSH | 0.54 | 0.68 |
| LPOP | 0.54 | 0.70 |
| RPOP | 0.52 | 0.69 |
| SADD | 0.55 | 0.68 |
| HSET | 0.54 | 0.69 |
| SPOP | 0.54 | 0.67 |
| ZADD | 0.52 | 0.69 |
| ZPOPMIN | 0.57 | 0.67 |
| LRANGE_100 (first 100 elements) | 1.02 | 1.11 |
| LRANGE_300 (first 300 elements) | 2.29 | 2.17 |
| LRANGE_500 (first 500 elements) | 3.27 | 3.16 |
| LRANGE_600 (first 600 elements) | 3.91 | 3.62 |
| MSET (10 keys) | 0.78 | 0.78 |
Conclusion
From the friendly robots:
Comparing the benchmarks of Vultr's Cloud Compute (4 GB, 2 Cores) and High Performance Intel (1 GB) instances, the former shows superior performance in most metrics with higher RPS rates and lower latencies for Redis operations, CPU events, file IO, and memory operations, although it does come with a higher cost. The High Performance Intel instance, while having a single more powerful CPU core (Xeon vs. Skylake), lags behind in multi-core tasks and memory throughput, but excels slightly in CPU latency and certain database operations. Therefore, the Cloud Compute instance is ideal for CPU-intensive and I/O-heavy workloads requiring higher RAM and multi-core processing, while the High Performance Intel instance would better serve applications that benefit from a powerful single core without requiring extensive multi-core or memory 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.