Vultr High Frequency Intel (2 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 my world famous suite of benchmarking scripts. All instances were spun up with Ubuntu 24.04 LTS x64 and all resided in or around the New York / New Jersey area. Enough talk. Here's the data.
Overview
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Last Benchmarked | Sun, 31 May 2026 13:00:55 GMT | Sat, 30 May 2026 16:00:52 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 | $18.00 | $6.00 |
| RAM (GB) | 2 | 1 |
| CPU Cores | 2 | 1 |
| Storage (TB) | 80 | 25 |
| Storage Type | NVMe | NVMe |
| Transfer (TB) | 3 | 2 |
CPU
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Vendor | GenuineIntel | GenuineIntel |
| Model Name | Intel Core Processor (Skylake, IBRS, no TSX) | Intel Xeon Processor (Cascadelake) |
| Clock Speed (MHz) | 3,791.98 | 2,893.17 |
| CPU Cache Size (KB) | 16,384.00 | 16,384.00 |
| BogoMips | 7,583.95 | 5,786.33 |
| Events per Second | 1,552.05 | 1,117.86 |
| Minimum Latency (ms) | 0.62 | 0.83 |
| Average Latency (ms) | 0.64 | 0.89 |
| Maximum Latency (ms) | 4.61 | 3.92 |
| 95th Percentile Latency (ms) | 0.69 | 1.04 |
Memory
Memory Read
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Operations per second | 7,875,668.83 | 4,957,996.46 |
| Mebibytes per second | 7,691.08 | 4,841.79 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.12 | 0.83 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Operations per second | 7,729,812.11 | 4,994,957.56 |
| Mebibytes per second | 7,548.64 | 4,877.89 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.16 | 0.96 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Reads per Second | 4,671.85 | 4,047.78 |
| Writes per Second | 3,114.56 | 2,698.52 |
| Fsyncs per Second | 9,976.90 | 8,646.86 |
| Read Mebibytes per Second | 73.00 | 63.25 |
| Written Mebibytes per Second | 48.67 | 42.16 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.06 | 0.06 |
| Maximum Latency (ms) | 2.76 | 3.35 |
| 95th Percentile Latency (ms) | 0.17 | 0.19 |
Mutex
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Minimum Latency (ms) | 543.27 | 1,571.60 |
| Average Latency (ms) | 554.74 | 1,588.95 |
| Maximum Latency (ms) | 563.70 | 1,599.96 |
| 95th Percentile Latency (ms) | 559.50 | 1,589.90 |
MySQL
MySQL Read-only
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 10,621.00 | 8,137.00 |
| Queries per second | 106,210.00 | 81,370.00 |
| Minimum Latency (ms) | 0.86 | 1.08 |
| Average Latency (ms) | 0.94 | 1.23 |
| Maximum Latency (ms) | 2.5 | 6.86 |
| 95th Percentile Latency (ms) | 1.03 | 1.42 |
MySQL Write-only
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 10,229.00 | 7,462.00 |
| Queries per second | 102,290.00 | 74,620.00 |
| Minimum Latency (ms) | 0.64 | 0.77 |
| Average Latency (ms) | 0.98 | 1.34 |
| Maximum Latency (ms) | 2.08 | 5.26 |
| 95th Percentile Latency (ms) | 1.23 | 1.93 |
MySQL Read/Write
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 5,072.00 | 3,070.00 |
| Queries per second | 50,720.00 | 30,700.00 |
| Minimum Latency (ms) | 1.59 | 2.45 |
| Average Latency (ms) | 1.97 | 3.25 |
| Maximum Latency (ms) | 3.94 | 8.6 |
| 95th Percentile Latency (ms) | 2.39 | 4.18 |
MySQL INSERT
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 16,038.00 | 15,069.00 |
| Queries per second | 160,380.00 | 150,690.00 |
| Minimum Latency (ms) | 0.38 | 0.43 |
| Average Latency (ms) | 0.62 | 0.66 |
| Maximum Latency (ms) | 13.18 | 3.39 |
| 95th Percentile Latency (ms) | 0.8 | 0.87 |
MySQL Bulk INSERT
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 2,424,342.00 | 964,103.00 |
| Queries per second | 24,243,420.00 | 9,641,030.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0.01 |
| Maximum Latency (ms) | 205.81 | 458.6 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 241,313.00 | 213,306.00 |
| Queries per second | 2,413,130.00 | 2,133,060.00 |
| Minimum Latency (ms) | 0.03 | 0.04 |
| Average Latency (ms) | 0.04 | 0.05 |
| Maximum Latency (ms) | 0.76 | 4.3 |
| 95th Percentile Latency (ms) | 0.05 | 0.07 |
MySQL SELECT (Random Points)
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 12,080.00 | 5,672.00 |
| Queries per second | 120,800.00 | 56,720.00 |
| Minimum Latency (ms) | 0.21 | 0.58 |
| Average Latency (ms) | 0.83 | 1.76 |
| Maximum Latency (ms) | 3.31 | 8.16 |
| 95th Percentile Latency (ms) | 1.04 | 2.52 |
MySQL SELECT (Random Ranges)
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 10,527.00 | 7,910.00 |
| Queries per second | 105,270.00 | 79,100.00 |
| Minimum Latency (ms) | 0.16 | 0.43 |
| Average Latency (ms) | 0.95 | 1.26 |
| Maximum Latency (ms) | 3.25 | 3.43 |
| 95th Percentile Latency (ms) | 1.23 | 1.67 |
MySQL UPDATE (Indexed)
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 17,123.00 | 13,874.00 |
| Queries per second | 171,230.00 | 138,740.00 |
| Minimum Latency (ms) | 0.38 | 0.43 |
| Average Latency (ms) | 0.58 | 0.72 |
| Maximum Latency (ms) | 2 | 10.49 |
| 95th Percentile Latency (ms) | 0.78 | 1.08 |
MySQL UPDATE (Non-Indexed)
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 16,979.00 | 15,344.00 |
| Queries per second | 169,790.00 | 153,440.00 |
| Minimum Latency (ms) | 0.38 | 0.42 |
| Average Latency (ms) | 0.59 | 0.65 |
| Maximum Latency (ms) | 4.13 | 4.43 |
| 95th Percentile Latency (ms) | 0.8 | 0.86 |
MySQL DELETE
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 156,424.00 | 83,214.00 |
| Queries per second | 1,564,240.00 | 832,140.00 |
| Minimum Latency (ms) | 0.03 | 0.05 |
| Average Latency (ms) | 0.06 | 0.12 |
| Maximum Latency (ms) | 4.87 | 4.88 |
| 95th Percentile Latency (ms) | 0.07 | 0.31 |
Redis
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| PING_INLINE per Second | 88,652.48 | 45,998.16 |
| PING_MBULK per Second | 89,605.73 | 46,210.72 |
| SET per Second | 90,171.33 | 48,756.70 |
| GET per Second | 90,579.71 | 47,014.57 |
| INCR per Second | 90,744.10 | 46,707.14 |
| LPUSH per Second | 90,497.73 | 46,296.29 |
| RPUSH per Second | 90,415.91 | 45,248.87 |
| LPOP per Second | 90,909.09 | 47,551.12 |
| RPOP per Second | 90,661.83 | 47,573.74 |
| SADD per Second | 90,252.70 | 46,794.57 |
| HSET per Second | 90,415.91 | 42,662.11 |
| SPOP per Second | 89,928.05 | 46,794.57 |
| ZADD per Second | 90,415.91 | 45,433.89 |
| ZPOPMIN per Second | 90,009.01 | 46,296.29 |
| LRANGE_100 (first 100 elements) per Second | 66,533.60 | 24,260.07 |
| LRANGE_300 (first 300 elements) per Second | 36,179.45 | 14,120.31 |
| LRANGE_500 (first 500 elements) per Second | 26,239.83 | 9,612.61 |
| LRANGE_600 (first 600 elements) per Second | 22,547.91 | 8,560.91 |
| MSET (10 keys) per Second | 88,105.73 | 43,859.65 |
Redis Average Latency (ms)
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| PING_INLINE | 0.30 | 0.71 |
| PING_MBULK | 0.29 | 0.70 |
| SET | 0.29 | 0.68 |
| GET | 0.29 | 0.70 |
| INCR | 0.28 | 0.71 |
| LPUSH | 0.29 | 0.72 |
| RPUSH | 0.29 | 0.73 |
| LPOP | 0.28 | 0.70 |
| RPOP | 0.28 | 0.70 |
| SADD | 0.29 | 0.70 |
| HSET | 0.29 | 0.76 |
| SPOP | 0.29 | 0.70 |
| ZADD | 0.29 | 0.72 |
| ZPOPMIN | 0.29 | 0.70 |
| LRANGE_100 (first 100 elements) | 0.39 | 1.42 |
| LRANGE_300 (first 300 elements) | 0.71 | 2.51 |
| LRANGE_500 (first 500 elements) | 0.97 | 3.69 |
| LRANGE_600 (first 600 elements) | 1.14 | 4.14 |
| MSET (10 keys) | 0.30 | 0.78 |
Conclusion
From the friendly robots:
Based on the benchmark results, the High Frequency Intel (2 GB, 2 Cores) instance from Vultr offers significantly better performance across all metrics compared to the High Performance Intel (1 GB) instance. This is most evident in the Redis benchmarks where the former achieves higher request rates per second and lower latencies for various operations, suggesting superior CPU and memory handling capabilities. The file I/O and CPU benchmarks also reflect this, with the higher frequency instance delivering better throughput, lower latencies, and more consistent thread fairness. Ideal use cases for the higher frequency instance would be CPU-intensive workloads, database operations requiring high concurrency, and any scenario where memory performance is critical. The lower performance instance, while still capable, may be more suitable for simpler, less resource-intensive applications where cost is a primary consideration.
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.