Vultr High Frequency Intel (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 to run some benchmarks on. Each instance was spun up with 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 – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Last Benchmarked | Sun, 31 May 2026 13:00:55 GMT | Mon, 01 Jun 2026 07: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 | $12.00 |
| RAM (GB) | 2 | 2 |
| CPU Cores | 2 | 1 |
| Storage (TB) | 80 | 50 |
| Storage Type | NVMe | NVMe |
| Transfer (TB) | 3 | 3 |
CPU
| Vultr – High Frequency Intel (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,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,048.47 |
| Minimum Latency (ms) | 0.62 | 0.83 |
| Average Latency (ms) | 0.64 | 0.95 |
| Maximum Latency (ms) | 4.61 | 5.25 |
| 95th Percentile Latency (ms) | 0.69 | 1.21 |
Memory
Memory Read
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Operations per second | 7,875,668.83 | 4,854,174.96 |
| Mebibytes per second | 7,691.08 | 4,740.41 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.12 | 2.23 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Operations per second | 7,729,812.11 | 4,942,528.76 |
| Mebibytes per second | 7,548.64 | 4,826.69 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.16 | 4.94 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Reads per Second | 4,671.85 | 4,132.87 |
| Writes per Second | 3,114.56 | 2,755.21 |
| Fsyncs per Second | 9,976.90 | 8,825.96 |
| Read Mebibytes per Second | 73.00 | 64.58 |
| Written Mebibytes per Second | 48.67 | 43.05 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.06 | 0.06 |
| Maximum Latency (ms) | 2.76 | 2.15 |
| 95th Percentile Latency (ms) | 0.17 | 0.19 |
Mutex
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Minimum Latency (ms) | 543.27 | 1,776.90 |
| Average Latency (ms) | 554.74 | 1,797.61 |
| Maximum Latency (ms) | 563.70 | 1,811.62 |
| 95th Percentile Latency (ms) | 559.50 | 1,803.47 |
MySQL
MySQL Read-only
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 10,621.00 | 7,971.00 |
| Queries per second | 106,210.00 | 79,710.00 |
| Minimum Latency (ms) | 0.86 | 1.06 |
| Average Latency (ms) | 0.94 | 1.25 |
| Maximum Latency (ms) | 2.5 | 4.3 |
| 95th Percentile Latency (ms) | 1.03 | 1.58 |
MySQL Write-only
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 10,229.00 | 7,352.00 |
| Queries per second | 102,290.00 | 73,520.00 |
| Minimum Latency (ms) | 0.64 | 0.83 |
| Average Latency (ms) | 0.98 | 1.36 |
| Maximum Latency (ms) | 2.08 | 4.44 |
| 95th Percentile Latency (ms) | 1.23 | 2 |
MySQL Read/Write
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 5,072.00 | 3,189.00 |
| Queries per second | 50,720.00 | 31,890.00 |
| Minimum Latency (ms) | 1.59 | 2.31 |
| Average Latency (ms) | 1.97 | 3.13 |
| Maximum Latency (ms) | 3.94 | 15.9 |
| 95th Percentile Latency (ms) | 2.39 | 4.18 |
MySQL INSERT
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 16,038.00 | 13,921.00 |
| Queries per second | 160,380.00 | 139,210.00 |
| Minimum Latency (ms) | 0.38 | 0.43 |
| Average Latency (ms) | 0.62 | 0.71 |
| Maximum Latency (ms) | 13.18 | 3.82 |
| 95th Percentile Latency (ms) | 0.8 | 0.97 |
MySQL Bulk INSERT
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 2,424,342.00 | 1,230,217.00 |
| Queries per second | 24,243,420.00 | 12,302,170.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0.01 |
| Maximum Latency (ms) | 205.81 | 357.55 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 241,313.00 | 207,049.00 |
| Queries per second | 2,413,130.00 | 2,070,490.00 |
| Minimum Latency (ms) | 0.03 | 0.04 |
| Average Latency (ms) | 0.04 | 0.05 |
| Maximum Latency (ms) | 0.76 | 2.95 |
| 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) | |
|---|---|---|
| Transactions per second | 12,080.00 | 6,025.00 |
| Queries per second | 120,800.00 | 60,250.00 |
| Minimum Latency (ms) | 0.21 | 0.49 |
| Average Latency (ms) | 0.83 | 1.66 |
| Maximum Latency (ms) | 3.31 | 4.45 |
| 95th Percentile Latency (ms) | 1.04 | 2.35 |
MySQL SELECT (Random Ranges)
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 10,527.00 | 7,229.00 |
| Queries per second | 105,270.00 | 72,290.00 |
| Minimum Latency (ms) | 0.16 | 0.53 |
| Average Latency (ms) | 0.95 | 1.38 |
| Maximum Latency (ms) | 3.25 | 5.38 |
| 95th Percentile Latency (ms) | 1.23 | 1.96 |
MySQL UPDATE (Indexed)
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 17,123.00 | 12,590.00 |
| Queries per second | 171,230.00 | 125,900.00 |
| Minimum Latency (ms) | 0.38 | 0.44 |
| Average Latency (ms) | 0.58 | 0.79 |
| Maximum Latency (ms) | 2 | 6.03 |
| 95th Percentile Latency (ms) | 0.78 | 1.23 |
MySQL UPDATE (Non-Indexed)
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 16,979.00 | 13,129.00 |
| Queries per second | 169,790.00 | 131,290.00 |
| Minimum Latency (ms) | 0.38 | 0.43 |
| Average Latency (ms) | 0.59 | 0.76 |
| Maximum Latency (ms) | 4.13 | 3.97 |
| 95th Percentile Latency (ms) | 0.8 | 1.08 |
MySQL DELETE
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| Transactions per second | 156,424.00 | 111,517.00 |
| Queries per second | 1,564,240.00 | 1,115,170.00 |
| Minimum Latency (ms) | 0.03 | 0.04 |
| Average Latency (ms) | 0.06 | 0.09 |
| Maximum Latency (ms) | 4.87 | 10.16 |
| 95th Percentile Latency (ms) | 0.07 | 0.18 |
Redis
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| PING_INLINE per Second | 88,652.48 | 43,252.59 |
| PING_MBULK per Second | 89,605.73 | 43,917.44 |
| SET per Second | 90,171.33 | 44,189.13 |
| GET per Second | 90,579.71 | 45,228.40 |
| INCR per Second | 90,744.10 | 44,662.79 |
| LPUSH per Second | 90,497.73 | 42,936.88 |
| RPUSH per Second | 90,415.91 | 42,955.32 |
| LPOP per Second | 90,909.09 | 39,339.10 |
| RPOP per Second | 90,661.83 | 43,572.98 |
| SADD per Second | 90,252.70 | 43,878.89 |
| HSET per Second | 90,415.91 | 43,010.75 |
| SPOP per Second | 89,928.05 | 43,497.17 |
| ZADD per Second | 90,415.91 | 42,034.47 |
| ZPOPMIN per Second | 90,009.01 | 44,052.86 |
| LRANGE_100 (first 100 elements) per Second | 66,533.60 | 25,893.32 |
| LRANGE_300 (first 300 elements) per Second | 36,179.45 | 13,837.00 |
| LRANGE_500 (first 500 elements) per Second | 26,239.83 | 8,880.99 |
| LRANGE_600 (first 600 elements) per Second | 22,547.91 | 8,015.39 |
| MSET (10 keys) per Second | 88,105.73 | 38,865.14 |
Redis Average Latency (ms)
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (2 GB) | |
|---|---|---|
| PING_INLINE | 0.30 | 0.75 |
| PING_MBULK | 0.29 | 0.75 |
| SET | 0.29 | 0.75 |
| GET | 0.29 | 0.73 |
| INCR | 0.28 | 0.73 |
| LPUSH | 0.29 | 0.76 |
| RPUSH | 0.29 | 0.77 |
| LPOP | 0.28 | 0.86 |
| RPOP | 0.28 | 0.76 |
| SADD | 0.29 | 0.74 |
| HSET | 0.29 | 0.76 |
| SPOP | 0.29 | 0.75 |
| ZADD | 0.29 | 0.78 |
| ZPOPMIN | 0.29 | 0.74 |
| LRANGE_100 (first 100 elements) | 0.39 | 1.30 |
| LRANGE_300 (first 300 elements) | 0.71 | 2.56 |
| LRANGE_500 (first 500 elements) | 0.97 | 3.99 |
| LRANGE_600 (first 600 elements) | 1.14 | 4.43 |
| MSET (10 keys) | 0.30 | 0.87 |
Conclusion
From the friendly robots:
After comparing the benchmark results for Vultr's High Frequency Intel (2 GB, 2 Cores) and High Performance Intel (2 GB, 1 Core) instances, it's clear that the High Frequency Intel instance significantly outperforms the High Performance Intel instance in most metrics, especially for CPU-bound and memory-bound workloads. The High Frequency Intel instance demonstrates higher rates of operations per second for Redis commands, better CPU performance with lower latency, and superior memory throughput. It also handles MySQL OLTP operations more efficiently. The High Performance Intel instance, while having a slightly higher clock speed, shows lower overall performance in most benchmarks, likely due to having fewer CPU cores and threads. The High Frequency Intel instance is ideal for workloads that are CPU and memory intensive, such as high-traffic web servers, complex data processing, or memory-optimized applications. Meanwhile, the High Performance Intel instance may be more suited for applications that do not require as much computational throughput and benefit from a single, high-frequency CPU core.
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.