Vultr Cloud Compute (4 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 and ran my world famous suite of benchmarking scripts. All instances were running 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 Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Last Benchmarked | Tue, 02 Jun 2026 06:00:52 GMT | Sun, 31 May 2026 13:00:55 GMT |
| Linux Distro | Ubuntu 24.04 LTS x64 | Ubuntu 24.04 LTS x64 |
| Kernel Version | 6.8.0-117-generic | 6.8.0-117-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 | $20.00 | $18.00 |
| RAM (GB) | 4 | 2 |
| CPU Cores | 2 | 2 |
| Storage (TB) | 80 | 80 |
| Storage Type | SSD | NVMe |
| Transfer (TB) | 3 | 3 |
CPU
| Vultr – Cloud Compute (4 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.06 | 3,791.98 |
| CPU Cache Size (KB) | 16,384.00 | 16,384.00 |
| BogoMips | 7,584.11 | 7,583.95 |
| Events per Second | 1,576.98 | 1,552.05 |
| Minimum Latency (ms) | 0.61 | 0.62 |
| Average Latency (ms) | 0.63 | 0.64 |
| Maximum Latency (ms) | 1.97 | 4.61 |
| 95th Percentile Latency (ms) | 0.67 | 0.69 |
Memory
Memory Read
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 7,849,685.24 | 7,875,668.83 |
| Mebibytes per second | 7,665.71 | 7,691.08 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.06 | 0.12 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 7,856,320.45 | 7,729,812.11 |
| Mebibytes per second | 7,672.19 | 7,548.64 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.06 | 0.16 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Reads per Second | 8,095.12 | 4,671.85 |
| Writes per Second | 5,396.74 | 3,114.56 |
| Fsyncs per Second | 17,271.28 | 9,976.90 |
| Read Mebibytes per Second | 126.49 | 73.00 |
| Written Mebibytes per Second | 84.32 | 48.67 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.03 | 0.06 |
| Maximum Latency (ms) | 1.51 | 2.76 |
| 95th Percentile Latency (ms) | 0.11 | 0.17 |
Mutex
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 464.63 | 543.27 |
| Average Latency (ms) | 547.54 | 554.74 |
| Maximum Latency (ms) | 583.01 | 563.70 |
| 95th Percentile Latency (ms) | 580.02 | 559.50 |
MySQL
MySQL Read-only
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 10,127.00 | 10,621.00 |
| Queries per second | 101,270.00 | 106,210.00 |
| Minimum Latency (ms) | 0.89 | 0.86 |
| Average Latency (ms) | 0.99 | 0.94 |
| Maximum Latency (ms) | 2.49 | 2.5 |
| 95th Percentile Latency (ms) | 1.12 | 1.03 |
MySQL Write-only
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 9,521.00 | 10,229.00 |
| Queries per second | 95,210.00 | 102,290.00 |
| Minimum Latency (ms) | 0.64 | 0.64 |
| Average Latency (ms) | 1.05 | 0.98 |
| Maximum Latency (ms) | 54.22 | 2.08 |
| 95th Percentile Latency (ms) | 1.34 | 1.23 |
MySQL Read/Write
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 4,611.00 | 5,072.00 |
| Queries per second | 46,110.00 | 50,720.00 |
| Minimum Latency (ms) | 1.61 | 1.59 |
| Average Latency (ms) | 2.17 | 1.97 |
| Maximum Latency (ms) | 16.47 | 3.94 |
| 95th Percentile Latency (ms) | 2.71 | 2.39 |
MySQL INSERT
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 16,673.00 | 16,038.00 |
| Queries per second | 166,730.00 | 160,380.00 |
| Minimum Latency (ms) | 0.38 | 0.38 |
| Average Latency (ms) | 0.6 | 0.62 |
| Maximum Latency (ms) | 2.29 | 13.18 |
| 95th Percentile Latency (ms) | 0.84 | 0.8 |
MySQL Bulk INSERT
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 2,249,592.00 | 2,424,342.00 |
| Queries per second | 22,495,920.00 | 24,243,420.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 217.13 | 205.81 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 228,323.00 | 241,313.00 |
| Queries per second | 2,283,230.00 | 2,413,130.00 |
| Minimum Latency (ms) | 0.03 | 0.03 |
| Average Latency (ms) | 0.04 | 0.04 |
| Maximum Latency (ms) | 0.84 | 0.76 |
| 95th Percentile Latency (ms) | 0.06 | 0.05 |
MySQL SELECT (Random Points)
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 10,527.00 | 12,080.00 |
| Queries per second | 105,270.00 | 120,800.00 |
| Minimum Latency (ms) | 0.29 | 0.21 |
| Average Latency (ms) | 0.95 | 0.83 |
| Maximum Latency (ms) | 3.01 | 3.31 |
| 95th Percentile Latency (ms) | 1.37 | 1.04 |
MySQL SELECT (Random Ranges)
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,906.00 | 10,527.00 |
| Queries per second | 89,060.00 | 105,270.00 |
| Minimum Latency (ms) | 0.34 | 0.16 |
| Average Latency (ms) | 1.12 | 0.95 |
| Maximum Latency (ms) | 4.32 | 3.25 |
| 95th Percentile Latency (ms) | 2.52 | 1.23 |
MySQL UPDATE (Indexed)
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 16,008.00 | 17,123.00 |
| Queries per second | 160,080.00 | 171,230.00 |
| Minimum Latency (ms) | 0.38 | 0.38 |
| Average Latency (ms) | 0.62 | 0.58 |
| Maximum Latency (ms) | 2.17 | 2 |
| 95th Percentile Latency (ms) | 0.87 | 0.78 |
MySQL UPDATE (Non-Indexed)
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 16,237.00 | 16,979.00 |
| Queries per second | 162,370.00 | 169,790.00 |
| Minimum Latency (ms) | 0.38 | 0.38 |
| Average Latency (ms) | 0.62 | 0.59 |
| Maximum Latency (ms) | 10.07 | 4.13 |
| 95th Percentile Latency (ms) | 0.84 | 0.8 |
MySQL DELETE
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 149,460.00 | 156,424.00 |
| Queries per second | 1,494,600.00 | 1,564,240.00 |
| Minimum Latency (ms) | 0.03 | 0.03 |
| Average Latency (ms) | 0.07 | 0.06 |
| Maximum Latency (ms) | 6.92 | 4.87 |
| 95th Percentile Latency (ms) | 0.08 | 0.07 |
Redis
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE per Second | 79,617.83 | 88,652.48 |
| PING_MBULK per Second | 79,554.50 | 89,605.73 |
| SET per Second | 83,125.52 | 90,171.33 |
| GET per Second | 81,632.65 | 90,579.71 |
| INCR per Second | 81,366.97 | 90,744.10 |
| LPUSH per Second | 75,642.96 | 90,497.73 |
| RPUSH per Second | 80,321.28 | 90,415.91 |
| LPOP per Second | 85,251.49 | 90,909.09 |
| RPOP per Second | 86,355.79 | 90,661.83 |
| SADD per Second | 85,178.88 | 90,252.70 |
| HSET per Second | 84,245.99 | 90,415.91 |
| SPOP per Second | 85,470.09 | 89,928.05 |
| ZADD per Second | 86,730.27 | 90,415.91 |
| ZPOPMIN per Second | 85,689.80 | 90,009.01 |
| LRANGE_100 (first 100 elements) per Second | 63,051.70 | 66,533.60 |
| LRANGE_300 (first 300 elements) per Second | 29,940.12 | 36,179.45 |
| LRANGE_500 (first 500 elements) per Second | 24,390.24 | 26,239.83 |
| LRANGE_600 (first 600 elements) per Second | 21,353.83 | 22,547.91 |
| MSET (10 keys) per Second | 84,175.09 | 88,105.73 |
Redis Average Latency (ms)
| Vultr – Cloud Compute (4 GB, 2 Cores) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE | 0.33 | 0.30 |
| PING_MBULK | 0.32 | 0.29 |
| SET | 0.32 | 0.29 |
| GET | 0.32 | 0.29 |
| INCR | 0.32 | 0.28 |
| LPUSH | 0.34 | 0.29 |
| RPUSH | 0.32 | 0.29 |
| LPOP | 0.31 | 0.28 |
| RPOP | 0.30 | 0.28 |
| SADD | 0.30 | 0.29 |
| HSET | 0.31 | 0.29 |
| SPOP | 0.30 | 0.29 |
| ZADD | 0.30 | 0.29 |
| ZPOPMIN | 0.30 | 0.29 |
| LRANGE_100 (first 100 elements) | 0.43 | 0.39 |
| LRANGE_300 (first 300 elements) | 0.96 | 0.71 |
| LRANGE_500 (first 500 elements) | 1.11 | 0.97 |
| LRANGE_600 (first 600 elements) | 1.23 | 1.14 |
| MSET (10 keys) | 0.31 | 0.30 |
Conclusion
From the friendly robots:
Both Vultr instances show impressive performance with high request rates for Redis operations, though the 4 GB, 2 Cores instance from Provider 1 has slightly higher average RPS and lower latency for most benchmarks, especially in complex tasks like LRANGE, suggesting better performance under more demanding loads. The CPU benchmarks also favor the higher-memory instance, with slightly higher events per second and lower latencies. In terms of file I/O, both instances offer good throughput and low average latency, though the High Frequency Intel instance shows slightly higher read and write speeds. For MySQL operations, the difference is marginal, but the 4 GB instance again edges out the 2 GB variant in read-heavy tasks. Overall, the 4 GB, 2 Cores instance is better suited for CPU-intensive, memory-demanding workloads, while the 2 GB, 2 Cores variant offers a cost-effective option for less resource-intensive applications, especially those benefitting from NVMe storage.
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.