Vultr Cloud Compute (2 GB, 2 Cores) vs. Vultr High Performance Intel (2 GB)
Fresh benchmarks coming at ya. Today I've spun up brand new instance from Vultr and ran some benchmarks. Each instance was spun up with 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 (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Last Benchmarked | Mon, 11 May 2026 04:00:52 GMT | Tue, 12 May 2026 19:00:53 GMT |
| Linux Distro | Ubuntu 24.04 LTS x64 | Ubuntu 24.04 LTS x64 |
| Kernel Version | 6.8.0-111-generic | 6.8.0-111-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 | $15.00 | $12.00 |
| RAM (GB) | 2 | 2 |
| CPU Cores | 2 | 1 |
| Storage (TB) | 65 | 50 |
| Storage Type | SSD | NVMe |
| Transfer (TB) | 3 | 3 |
CPU
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Vendor | GenuineIntel | GenuineIntel |
| Model Name | Intel Core Processor (Skylake, IBRS, no TSX) | Intel Xeon Processor (Cascadelake) |
| Clock Speed (MHz) | 3,792.00 | 2,893.17 |
| CPU Cache Size (KB) | 16,384.00 | 16,384.00 |
| BogoMips | 7,583.99 | 5,786.33 |
| Events per Second | 1,481.60 | 1,113.54 |
| Minimum Latency (ms) | 0.63 | 0.83 |
| Average Latency (ms) | 0.67 | 0.9 |
| Maximum Latency (ms) | 1.95 | 2.82 |
| 95th Percentile Latency (ms) | 0.77 | 1.03 |
Memory
Memory Read
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Operations per second | 6,401,389.08 | 5,137,826.95 |
| Mebibytes per second | 6,251.36 | 5,017.41 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.23 | 2.23 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Operations per second | 6,411,085.35 | 5,077,308.02 |
| Mebibytes per second | 6,260.83 | 4,958.31 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.18 | 0.68 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Reads per Second | 4,345.71 | 4,329.69 |
| Writes per Second | 2,897.07 | 2,886.46 |
| Fsyncs per Second | 9,273.19 | 9,246.36 |
| Read Mebibytes per Second | 67.90 | 67.65 |
| Written Mebibytes per Second | 45.27 | 45.10 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.06 | 0.06 |
| Maximum Latency (ms) | 2.92 | 4.84 |
| 95th Percentile Latency (ms) | 0.17 | 0.18 |
Mutex
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Minimum Latency (ms) | 214.63 | 1,646.72 |
| Average Latency (ms) | 569.72 | 1,659.26 |
| Maximum Latency (ms) | 636.55 | 1,671.13 |
| 95th Percentile Latency (ms) | 634.66 | 1,678.14 |
MySQL
MySQL Read-only
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 8,015.00 | 8,418.00 |
| Queries per second | 80,150.00 | 84,180.00 |
| Minimum Latency (ms) | 0.92 | 1.08 |
| Average Latency (ms) | 1.25 | 1.19 |
| Maximum Latency (ms) | 5.5 | 4.43 |
| 95th Percentile Latency (ms) | 1.86 | 1.47 |
MySQL Write-only
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 8,497.00 | 7,510.00 |
| Queries per second | 84,970.00 | 75,100.00 |
| Minimum Latency (ms) | 0.76 | 0.79 |
| Average Latency (ms) | 1.17 | 1.33 |
| Maximum Latency (ms) | 3.04 | 6.46 |
| 95th Percentile Latency (ms) | 1.55 | 2 |
MySQL Read/Write
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 3,726.00 | 3,001.00 |
| Queries per second | 37,260.00 | 30,010.00 |
| Minimum Latency (ms) | 1.78 | 2.36 |
| Average Latency (ms) | 2.68 | 3.33 |
| Maximum Latency (ms) | 5.82 | 19.36 |
| 95th Percentile Latency (ms) | 3.43 | 4.74 |
MySQL INSERT
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 15,028.00 | 14,317.00 |
| Queries per second | 150,280.00 | 143,170.00 |
| Minimum Latency (ms) | 0.41 | 0.43 |
| Average Latency (ms) | 0.66 | 0.69 |
| Maximum Latency (ms) | 2.42 | 4.44 |
| 95th Percentile Latency (ms) | 0.86 | 0.9 |
MySQL Bulk INSERT
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 1,696,217.00 | 1,171,967.00 |
| Queries per second | 16,962,170.00 | 11,719,670.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0.01 |
| Maximum Latency (ms) | 283.37 | 386.31 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 201,989.00 | 211,601.00 |
| Queries per second | 2,019,890.00 | 2,116,010.00 |
| Minimum Latency (ms) | 0.03 | 0.04 |
| Average Latency (ms) | 0.05 | 0.05 |
| Maximum Latency (ms) | 0.51 | 1.44 |
| 95th Percentile Latency (ms) | 0.07 | 0.07 |
MySQL SELECT (Random Points)
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 8,025.00 | 5,968.00 |
| Queries per second | 80,250.00 | 59,680.00 |
| Minimum Latency (ms) | 0.35 | 0.58 |
| Average Latency (ms) | 1.24 | 1.67 |
| Maximum Latency (ms) | 3.55 | 4.57 |
| 95th Percentile Latency (ms) | 2.07 | 2.43 |
MySQL SELECT (Random Ranges)
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 8,336.00 | 7,670.00 |
| Queries per second | 83,360.00 | 76,700.00 |
| Minimum Latency (ms) | 0.4 | 0.39 |
| Average Latency (ms) | 1.2 | 1.3 |
| Maximum Latency (ms) | 4.25 | 3.13 |
| 95th Percentile Latency (ms) | 2.22 | 1.76 |
MySQL UPDATE (Indexed)
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 13,858.00 | 14,254.00 |
| Queries per second | 138,580.00 | 142,540.00 |
| Minimum Latency (ms) | 0.42 | 0.42 |
| Average Latency (ms) | 0.72 | 0.7 |
| Maximum Latency (ms) | 6.33 | 3.63 |
| 95th Percentile Latency (ms) | 0.95 | 1.03 |
MySQL UPDATE (Non-Indexed)
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 14,587.00 | 13,755.00 |
| Queries per second | 145,870.00 | 137,550.00 |
| Minimum Latency (ms) | 0.4 | 0.42 |
| Average Latency (ms) | 0.68 | 0.73 |
| Maximum Latency (ms) | 11.69 | 7.01 |
| 95th Percentile Latency (ms) | 0.9 | 1.01 |
MySQL DELETE
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 129,013.00 | 117,129.00 |
| Queries per second | 1,290,130.00 | 1,171,290.00 |
| Minimum Latency (ms) | 0.03 | 0.04 |
| Average Latency (ms) | 0.08 | 0.08 |
| Maximum Latency (ms) | 2.61 | 4.27 |
| 95th Percentile Latency (ms) | 0.09 | 0.16 |
Redis
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| PING_INLINE per Second | 78,247.26 | 44,033.47 |
| PING_MBULK per Second | 74,738.41 | 41,203.13 |
| SET per Second | 77,041.60 | 41,597.34 |
| GET per Second | 83,333.33 | 41,771.09 |
| INCR per Second | 80,971.66 | 39,354.59 |
| LPUSH per Second | 79,113.92 | 45,871.56 |
| RPUSH per Second | 77,160.49 | 43,802.02 |
| LPOP per Second | 81,499.59 | 45,228.40 |
| RPOP per Second | 82,440.23 | 44,286.98 |
| SADD per Second | 80,192.46 | 42,992.26 |
| HSET per Second | 83,612.04 | 42,052.14 |
| SPOP per Second | 85,034.02 | 43,084.88 |
| ZADD per Second | 83,263.95 | 46,425.25 |
| ZPOPMIN per Second | 82,987.55 | 44,306.60 |
| LRANGE_100 (first 100 elements) per Second | 55,555.56 | 27,816.41 |
| LRANGE_300 (first 300 elements) per Second | 28,851.70 | 14,634.86 |
| LRANGE_500 (first 500 elements) per Second | 19,391.12 | 9,436.63 |
| LRANGE_600 (first 600 elements) per Second | 17,211.71 | 8,049.59 |
| MSET (10 keys) per Second | 80,256.82 | 42,771.60 |
Redis Average Latency (ms)
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| PING_INLINE | 0.34 | 0.74 |
| PING_MBULK | 0.35 | 0.78 |
| SET | 0.34 | 0.79 |
| GET | 0.32 | 0.78 |
| INCR | 0.32 | 0.84 |
| LPUSH | 0.34 | 0.71 |
| RPUSH | 0.34 | 0.74 |
| LPOP | 0.32 | 0.72 |
| RPOP | 0.32 | 0.74 |
| SADD | 0.32 | 0.75 |
| HSET | 0.31 | 0.77 |
| SPOP | 0.30 | 0.75 |
| ZADD | 0.31 | 0.70 |
| ZPOPMIN | 0.31 | 0.73 |
| LRANGE_100 (first 100 elements) | 0.54 | 1.23 |
| LRANGE_300 (first 300 elements) | 1.11 | 2.42 |
| LRANGE_500 (first 500 elements) | 1.62 | 3.76 |
| LRANGE_600 (first 600 elements) | 1.84 | 4.43 |
| MSET (10 keys) | 0.38 | 0.79 |
Conclusion
From the friendly robots:
Upon comparing the benchmark performance of Vultr's Cloud Compute (2 GB, 2 Cores) and High Performance Intel (2 GB) instances, it's clear that the Cloud Compute offers slightly higher Redis performance metrics with significantly more requests per second for most operations, albeit with slightly higher latencies. The High Performance Intel instance, however, showcases superior CPU performance and lower latencies in its benchmarks, indicating it may handle CPU-intensive tasks more efficiently. Given their similar configurations, the Cloud Compute instance is better suited for workloads that benefit from more CPU cores and slightly better I/O performance, while the High Performance Intel instance excels in CPU-bound tasks with lower latency, making it ideal for high-performance computing scenarios.
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.