Vultr Cloud Compute (2 GB, 2 Cores) vs. Vultr High Frequency Intel (2 GB, 2 Cores)
My friend, I'm so glad you're here! Today I've spun up brand new instance from Vultr to run some benchmarks on. Each instance was running 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 (2 GB, 2 Cores) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Last Benchmarked | Mon, 11 May 2026 04:00:52 GMT | Tue, 12 May 2026 22:00:52 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 | $18.00 |
| RAM (GB) | 2 | 2 |
| CPU Cores | 2 | 2 |
| Storage (TB) | 65 | 80 |
| Storage Type | SSD | NVMe |
| Transfer (TB) | 3 | 3 |
CPU
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Vendor | GenuineIntel | GenuineIntel |
| Model Name | Intel Core Processor (Skylake, IBRS, no TSX) | Intel Core Processor (Skylake, IBRS, no TSX) |
| Clock Speed (MHz) | 3,792.00 | 3,792.00 |
| CPU Cache Size (KB) | 16,384.00 | 16,384.00 |
| BogoMips | 7,583.99 | 7,584.00 |
| Events per Second | 1,481.60 | 1,595.33 |
| Minimum Latency (ms) | 0.63 | 0.61 |
| Average Latency (ms) | 0.67 | 0.63 |
| Maximum Latency (ms) | 1.95 | 3.82 |
| 95th Percentile Latency (ms) | 0.77 | 0.67 |
Memory
Memory Read
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 6,401,389.08 | 8,018,179.72 |
| Mebibytes per second | 6,251.36 | 7,830.25 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.23 | 0.23 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 6,411,085.35 | 8,026,354.64 |
| Mebibytes per second | 6,260.83 | 7,838.24 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.18 | 0.23 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Reads per Second | 4,345.71 | 4,761.31 |
| Writes per Second | 2,897.07 | 3,174.20 |
| Fsyncs per Second | 9,273.19 | 10,161.05 |
| Read Mebibytes per Second | 67.90 | 74.40 |
| Written Mebibytes per Second | 45.27 | 49.60 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.06 | 0.05 |
| Maximum Latency (ms) | 2.92 | 2.86 |
| 95th Percentile Latency (ms) | 0.17 | 0.17 |
Mutex
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 214.63 | 315.69 |
| Average Latency (ms) | 569.72 | 517.12 |
| Maximum Latency (ms) | 636.55 | 555.49 |
| 95th Percentile Latency (ms) | 634.66 | 559.50 |
MySQL
MySQL Read-only
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,015.00 | 10,846.00 |
| Queries per second | 80,150.00 | 108,460.00 |
| Minimum Latency (ms) | 0.92 | 0.85 |
| Average Latency (ms) | 1.25 | 0.92 |
| Maximum Latency (ms) | 5.5 | 2.7 |
| 95th Percentile Latency (ms) | 1.86 | 0.97 |
MySQL Write-only
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,497.00 | 9,835.00 |
| Queries per second | 84,970.00 | 98,350.00 |
| Minimum Latency (ms) | 0.76 | 0.66 |
| Average Latency (ms) | 1.17 | 1.02 |
| Maximum Latency (ms) | 3.04 | 2.23 |
| 95th Percentile Latency (ms) | 1.55 | 1.3 |
MySQL Read/Write
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 3,726.00 | 5,208.00 |
| Queries per second | 37,260.00 | 52,080.00 |
| Minimum Latency (ms) | 1.78 | 1.59 |
| Average Latency (ms) | 2.68 | 1.92 |
| Maximum Latency (ms) | 5.82 | 3.66 |
| 95th Percentile Latency (ms) | 3.43 | 2.18 |
MySQL INSERT
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 15,028.00 | 18,348.00 |
| Queries per second | 150,280.00 | 183,480.00 |
| Minimum Latency (ms) | 0.41 | 0.37 |
| Average Latency (ms) | 0.66 | 0.54 |
| Maximum Latency (ms) | 2.42 | 2.54 |
| 95th Percentile Latency (ms) | 0.86 | 0.68 |
MySQL Bulk INSERT
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 1,696,217.00 | 2,540,842.00 |
| Queries per second | 16,962,170.00 | 25,408,420.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0 |
| Maximum Latency (ms) | 283.37 | 200.43 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 201,989.00 | 245,434.00 |
| Queries per second | 2,019,890.00 | 2,454,340.00 |
| Minimum Latency (ms) | 0.03 | 0.03 |
| Average Latency (ms) | 0.05 | 0.04 |
| Maximum Latency (ms) | 0.51 | 1.11 |
| 95th Percentile Latency (ms) | 0.07 | 0.05 |
MySQL SELECT (Random Points)
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,025.00 | 12,340.00 |
| Queries per second | 80,250.00 | 123,400.00 |
| Minimum Latency (ms) | 0.35 | 0.22 |
| Average Latency (ms) | 1.24 | 0.81 |
| Maximum Latency (ms) | 3.55 | 2.5 |
| 95th Percentile Latency (ms) | 2.07 | 1.03 |
MySQL SELECT (Random Ranges)
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,336.00 | 10,685.00 |
| Queries per second | 83,360.00 | 106,850.00 |
| Minimum Latency (ms) | 0.4 | 0.39 |
| Average Latency (ms) | 1.2 | 0.94 |
| Maximum Latency (ms) | 4.25 | 2.9 |
| 95th Percentile Latency (ms) | 2.22 | 1.21 |
MySQL UPDATE (Indexed)
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 13,858.00 | 17,447.00 |
| Queries per second | 138,580.00 | 174,470.00 |
| Minimum Latency (ms) | 0.42 | 0.38 |
| Average Latency (ms) | 0.72 | 0.57 |
| Maximum Latency (ms) | 6.33 | 1.78 |
| 95th Percentile Latency (ms) | 0.95 | 0.75 |
MySQL UPDATE (Non-Indexed)
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 14,587.00 | 16,733.00 |
| Queries per second | 145,870.00 | 167,330.00 |
| Minimum Latency (ms) | 0.4 | 0.37 |
| Average Latency (ms) | 0.68 | 0.6 |
| Maximum Latency (ms) | 11.69 | 1.55 |
| 95th Percentile Latency (ms) | 0.9 | 0.77 |
MySQL DELETE
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 129,013.00 | 158,104.00 |
| Queries per second | 1,290,130.00 | 1,581,040.00 |
| Minimum Latency (ms) | 0.03 | 0.03 |
| Average Latency (ms) | 0.08 | 0.06 |
| Maximum Latency (ms) | 2.61 | 3.94 |
| 95th Percentile Latency (ms) | 0.09 | 0.07 |
Redis
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE per Second | 78,247.26 | 85,397.09 |
| PING_MBULK per Second | 74,738.41 | 86,355.79 |
| SET per Second | 77,041.60 | 86,430.43 |
| GET per Second | 83,333.33 | 86,355.79 |
| INCR per Second | 80,971.66 | 86,058.52 |
| LPUSH per Second | 79,113.92 | 87,336.24 |
| RPUSH per Second | 77,160.49 | 87,642.41 |
| LPOP per Second | 81,499.59 | 87,336.24 |
| RPOP per Second | 82,440.23 | 87,032.20 |
| SADD per Second | 80,192.46 | 85,763.29 |
| HSET per Second | 83,612.04 | 87,260.03 |
| SPOP per Second | 85,034.02 | 87,489.06 |
| ZADD per Second | 83,263.95 | 87,336.24 |
| ZPOPMIN per Second | 82,987.55 | 86,355.79 |
| LRANGE_100 (first 100 elements) per Second | 55,555.56 | 65,061.81 |
| LRANGE_300 (first 300 elements) per Second | 28,851.70 | 36,832.41 |
| LRANGE_500 (first 500 elements) per Second | 19,391.12 | 26,171.16 |
| LRANGE_600 (first 600 elements) per Second | 17,211.71 | 23,337.22 |
| MSET (10 keys) per Second | 80,256.82 | 89,525.52 |
Redis Average Latency (ms)
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE | 0.34 | 0.31 |
| PING_MBULK | 0.35 | 0.30 |
| SET | 0.34 | 0.30 |
| GET | 0.32 | 0.30 |
| INCR | 0.32 | 0.30 |
| LPUSH | 0.34 | 0.29 |
| RPUSH | 0.34 | 0.29 |
| LPOP | 0.32 | 0.29 |
| RPOP | 0.32 | 0.30 |
| SADD | 0.32 | 0.30 |
| HSET | 0.31 | 0.30 |
| SPOP | 0.30 | 0.29 |
| ZADD | 0.31 | 0.29 |
| ZPOPMIN | 0.31 | 0.30 |
| LRANGE_100 (first 100 elements) | 0.54 | 0.39 |
| LRANGE_300 (first 300 elements) | 1.11 | 0.69 |
| LRANGE_500 (first 500 elements) | 1.62 | 0.97 |
| LRANGE_600 (first 600 elements) | 1.84 | 1.09 |
| MSET (10 keys) | 0.38 | 0.29 |
Conclusion
From the friendly robots:
After analyzing the benchmark results for both Vultr instances, it's clear that the High Frequency Intel (2 GB, 2 Cores) variant outperforms the standard Cloud Compute (2 GB, 2 Cores) in most metrics, particularly in Redis operations, CPU performance, and MySQL operations. The High Frequency variant provides higher RPS rates for most Redis commands and slightly lower latencies, suggesting better efficiency. CPU and MySQL benchmarks also show superior performance in terms of throughput and lower average latencies. While both instances deliver solid I/O performance, the High Frequency variant's higher read and write operations per second indicate a slight edge. Therefore, the High Frequency Intel variant would be better suited for CPU-intensive and I/O-heavy workloads, whereas the Cloud Compute instance might be more economical for simpler tasks requiring lower computational power and I/O operations.
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.