Vultr High Frequency Intel (2 GB, 2 Cores) vs. Vultr High Performance Intel (2 GB, 2 Cores)
Same showdown, different day. Today I've spun up some brand new instance from Vultr and did some benchmarking. All instances were spun up with Ubuntu 24.04 LTS x64 and were created in the New York area (or close to it). Let's get into the numbers.
Overview
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB, 2 Cores) | |
|---|---|---|
| Last Benchmarked | Sun, 31 May 2026 13:00:55 GMT | Sun, 31 May 2026 20:00:51 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 | $18.00 |
| RAM (GB) | 2 | 2 |
| CPU Cores | 2 | 2 |
| Storage (TB) | 80 | 60 |
| Storage Type | NVMe | NVMe |
| Transfer (TB) | 3 | 4 |
CPU
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB, 2 Cores) | |
|---|---|---|
| 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,140.16 |
| Minimum Latency (ms) | 0.62 | 0.83 |
| Average Latency (ms) | 0.64 | 0.88 |
| Maximum Latency (ms) | 4.61 | 5.04 |
| 95th Percentile Latency (ms) | 0.69 | 0.95 |
Memory
Memory Read
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 7,875,668.83 | 5,101,642.66 |
| Mebibytes per second | 7,691.08 | 4,982.07 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.12 | 0.8 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 7,729,812.11 | 5,260,565.97 |
| Mebibytes per second | 7,548.64 | 5,137.27 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.16 | 1.09 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB, 2 Cores) | |
|---|---|---|
| Reads per Second | 4,671.85 | 4,398.81 |
| Writes per Second | 3,114.56 | 2,932.54 |
| Fsyncs per Second | 9,976.90 | 9,388.60 |
| Read Mebibytes per Second | 73.00 | 68.73 |
| Written Mebibytes per Second | 48.67 | 45.82 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.06 | 0.06 |
| Maximum Latency (ms) | 2.76 | 3.17 |
| 95th Percentile Latency (ms) | 0.17 | 0.18 |
Mutex
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB, 2 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 543.27 | 749.20 |
| Average Latency (ms) | 554.74 | 793.98 |
| Maximum Latency (ms) | 563.70 | 843.04 |
| 95th Percentile Latency (ms) | 559.50 | 846.57 |
MySQL
MySQL Read-only
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 10,621.00 | 7,145.00 |
| Queries per second | 106,210.00 | 71,450.00 |
| Minimum Latency (ms) | 0.86 | 1.12 |
| Average Latency (ms) | 0.94 | 1.4 |
| Maximum Latency (ms) | 2.5 | 3.41 |
| 95th Percentile Latency (ms) | 1.03 | 1.79 |
MySQL Write-only
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 10,229.00 | 8,110.00 |
| Queries per second | 102,290.00 | 81,100.00 |
| Minimum Latency (ms) | 0.64 | 0.77 |
| Average Latency (ms) | 0.98 | 1.23 |
| Maximum Latency (ms) | 2.08 | 3.33 |
| 95th Percentile Latency (ms) | 1.23 | 1.67 |
MySQL Read/Write
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 5,072.00 | 3,631.00 |
| Queries per second | 50,720.00 | 36,310.00 |
| Minimum Latency (ms) | 1.59 | 2.09 |
| Average Latency (ms) | 1.97 | 2.75 |
| Maximum Latency (ms) | 3.94 | 6.05 |
| 95th Percentile Latency (ms) | 2.39 | 3.55 |
MySQL INSERT
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 16,038.00 | 14,582.00 |
| Queries per second | 160,380.00 | 145,820.00 |
| Minimum Latency (ms) | 0.38 | 0.43 |
| Average Latency (ms) | 0.62 | 0.68 |
| Maximum Latency (ms) | 13.18 | 11.71 |
| 95th Percentile Latency (ms) | 0.8 | 0.92 |
MySQL Bulk INSERT
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 2,424,342.00 | 1,492,342.00 |
| Queries per second | 24,243,420.00 | 14,923,420.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0.01 |
| Maximum Latency (ms) | 205.81 | 314.04 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 241,313.00 | 197,860.00 |
| Queries per second | 2,413,130.00 | 1,978,600.00 |
| Minimum Latency (ms) | 0.03 | 0.03 |
| Average Latency (ms) | 0.04 | 0.05 |
| Maximum Latency (ms) | 0.76 | 0.62 |
| 95th Percentile Latency (ms) | 0.05 | 0.07 |
MySQL SELECT (Random Points)
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 12,080.00 | 6,871.00 |
| Queries per second | 120,800.00 | 68,710.00 |
| Minimum Latency (ms) | 0.21 | 0.57 |
| Average Latency (ms) | 0.83 | 1.45 |
| Maximum Latency (ms) | 3.31 | 4.9 |
| 95th Percentile Latency (ms) | 1.04 | 1.96 |
MySQL SELECT (Random Ranges)
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 10,527.00 | 7,407.00 |
| Queries per second | 105,270.00 | 74,070.00 |
| Minimum Latency (ms) | 0.16 | 0.53 |
| Average Latency (ms) | 0.95 | 1.35 |
| Maximum Latency (ms) | 3.25 | 3.5 |
| 95th Percentile Latency (ms) | 1.23 | 1.82 |
MySQL UPDATE (Indexed)
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 17,123.00 | 13,481.00 |
| Queries per second | 171,230.00 | 134,810.00 |
| Minimum Latency (ms) | 0.38 | 0.45 |
| Average Latency (ms) | 0.58 | 0.74 |
| Maximum Latency (ms) | 2 | 3.61 |
| 95th Percentile Latency (ms) | 0.78 | 1.03 |
MySQL UPDATE (Non-Indexed)
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 16,979.00 | 14,448.00 |
| Queries per second | 169,790.00 | 144,480.00 |
| Minimum Latency (ms) | 0.38 | 0.43 |
| Average Latency (ms) | 0.59 | 0.69 |
| Maximum Latency (ms) | 4.13 | 3.44 |
| 95th Percentile Latency (ms) | 0.8 | 0.92 |
MySQL DELETE
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 156,424.00 | 121,404.00 |
| Queries per second | 1,564,240.00 | 1,214,040.00 |
| Minimum Latency (ms) | 0.03 | 0.03 |
| Average Latency (ms) | 0.06 | 0.08 |
| Maximum Latency (ms) | 4.87 | 4.39 |
| 95th Percentile Latency (ms) | 0.07 | 0.12 |
Redis
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE per Second | 88,652.48 | 62,189.05 |
| PING_MBULK per Second | 89,605.73 | 60,606.06 |
| SET per Second | 90,171.33 | 62,034.74 |
| GET per Second | 90,579.71 | 62,344.14 |
| INCR per Second | 90,744.10 | 61,349.70 |
| LPUSH per Second | 90,497.73 | 61,274.51 |
| RPUSH per Second | 90,415.91 | 63,816.21 |
| LPOP per Second | 90,909.09 | 63,291.14 |
| RPOP per Second | 90,661.83 | 62,814.07 |
| SADD per Second | 90,252.70 | 62,073.25 |
| HSET per Second | 90,415.91 | 59,559.26 |
| SPOP per Second | 89,928.05 | 60,496.07 |
| ZADD per Second | 90,415.91 | 62,150.41 |
| ZPOPMIN per Second | 90,009.01 | 62,539.09 |
| LRANGE_100 (first 100 elements) per Second | 66,533.60 | 47,125.36 |
| LRANGE_300 (first 300 elements) per Second | 36,179.45 | 26,143.79 |
| LRANGE_500 (first 500 elements) per Second | 26,239.83 | 17,905.10 |
| LRANGE_600 (first 600 elements) per Second | 22,547.91 | 15,535.19 |
| MSET (10 keys) per Second | 88,105.73 | 61,576.36 |
Redis Average Latency (ms)
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE | 0.30 | 0.42 |
| PING_MBULK | 0.29 | 0.42 |
| SET | 0.29 | 0.42 |
| GET | 0.29 | 0.41 |
| INCR | 0.28 | 0.42 |
| LPUSH | 0.29 | 0.42 |
| RPUSH | 0.29 | 0.40 |
| LPOP | 0.28 | 0.41 |
| RPOP | 0.28 | 0.41 |
| SADD | 0.29 | 0.42 |
| HSET | 0.29 | 0.45 |
| SPOP | 0.29 | 0.43 |
| ZADD | 0.29 | 0.43 |
| ZPOPMIN | 0.29 | 0.41 |
| LRANGE_100 (first 100 elements) | 0.39 | 0.57 |
| LRANGE_300 (first 300 elements) | 0.71 | 1.04 |
| LRANGE_500 (first 500 elements) | 0.97 | 1.47 |
| LRANGE_600 (first 600 elements) | 1.14 | 1.72 |
| MSET (10 keys) | 0.30 | 0.44 |
Conclusion
From the friendly robots:
Both Vultr instances showcase strong performance across various metrics, but they excel in different areas. The High Frequency Intel instance delivers outstanding Redis performance with high requests per second (rps) and low latencies for most commands, indicating excellent processing capabilities for memory-intensive tasks. This instance also shows remarkable CPU and file I/O performance, making it suitable for CPU-intensive and I/O-heavy workloads. Conversely, the High Performance Intel instance provides slightly lower Redis performance in most metrics but shines in MySQL benchmarks, particularly in OLTP read-write operations with lower latencies. It also performs well in memory operations and file I/O, suggesting it's a strong choice for database-driven applications requiring high throughput and consistency. Overall, the High Frequency Intel instance is ideal for general-purpose, high-performance tasks, while the High Performance Intel instance is better suited for applications with significant database interaction and high transactional loads.
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.