Vultr High Frequency Intel (2 GB, 2 Cores) vs. Vultr High Performance Intel (8 GB, 4 Cores)
Same showdown, different day. Today I've spun up some brand new instance from Vultr and ran some benchmarks. Each instance was spun up with Ubuntu 24.04 LTS x64 and were created 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 (8 GB, 4 Cores) | |
|---|---|---|
| Last Benchmarked | Sun, 31 May 2026 13:00:55 GMT | Sun, 31 May 2026 03: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 | $48.00 |
| RAM (GB) | 2 | 8 |
| CPU Cores | 2 | 4 |
| Storage (TB) | 80 | 180 |
| Storage Type | NVMe | NVMe |
| Transfer (TB) | 3 | 6 |
CPU
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (8 GB, 4 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,164.11 |
| Minimum Latency (ms) | 0.62 | 0.83 |
| Average Latency (ms) | 0.64 | 0.86 |
| Maximum Latency (ms) | 4.61 | 1.81 |
| 95th Percentile Latency (ms) | 0.69 | 0.9 |
Memory
Memory Read
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Operations per second | 7,875,668.83 | 5,268,671.27 |
| Mebibytes per second | 7,691.08 | 5,145.19 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.12 | 0.85 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Operations per second | 7,729,812.11 | 5,300,398.23 |
| Mebibytes per second | 7,548.64 | 5,176.17 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.16 | 0.29 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Reads per Second | 4,671.85 | 8,120.73 |
| Writes per Second | 3,114.56 | 5,413.82 |
| Fsyncs per Second | 9,976.90 | 17,334.39 |
| Read Mebibytes per Second | 73.00 | 126.89 |
| Written Mebibytes per Second | 48.67 | 84.59 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.06 | 0.03 |
| Maximum Latency (ms) | 2.76 | 16.4 |
| 95th Percentile Latency (ms) | 0.17 | 0.1 |
Mutex
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 543.27 | 197.88 |
| Average Latency (ms) | 554.74 | 357.16 |
| Maximum Latency (ms) | 563.70 | 411.19 |
| 95th Percentile Latency (ms) | 559.50 | 411.96 |
MySQL
MySQL Read-only
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 10,621.00 | 7,388.00 |
| Queries per second | 106,210.00 | 73,880.00 |
| Minimum Latency (ms) | 0.86 | 1.14 |
| Average Latency (ms) | 0.94 | 1.35 |
| Maximum Latency (ms) | 2.5 | 3.22 |
| 95th Percentile Latency (ms) | 1.03 | 1.7 |
MySQL Write-only
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 10,229.00 | 7,997.00 |
| Queries per second | 102,290.00 | 79,970.00 |
| Minimum Latency (ms) | 0.64 | 0.87 |
| Average Latency (ms) | 0.98 | 1.25 |
| Maximum Latency (ms) | 2.08 | 3.16 |
| 95th Percentile Latency (ms) | 1.23 | 1.55 |
MySQL Read/Write
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 5,072.00 | 3,262.00 |
| Queries per second | 50,720.00 | 32,620.00 |
| Minimum Latency (ms) | 1.59 | 2.17 |
| Average Latency (ms) | 1.97 | 3.06 |
| Maximum Latency (ms) | 3.94 | 7.36 |
| 95th Percentile Latency (ms) | 2.39 | 3.82 |
MySQL INSERT
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 16,038.00 | 12,898.00 |
| Queries per second | 160,380.00 | 128,980.00 |
| Minimum Latency (ms) | 0.38 | 0.44 |
| Average Latency (ms) | 0.62 | 0.77 |
| Maximum Latency (ms) | 13.18 | 11.56 |
| 95th Percentile Latency (ms) | 0.8 | 1.04 |
MySQL Bulk INSERT
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 2,424,342.00 | 1,434,092.00 |
| Queries per second | 24,243,420.00 | 14,340,920.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0.01 |
| Maximum Latency (ms) | 205.81 | 363.55 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 241,313.00 | 190,206.00 |
| Queries per second | 2,413,130.00 | 1,902,060.00 |
| Minimum Latency (ms) | 0.03 | 0.04 |
| Average Latency (ms) | 0.04 | 0.05 |
| Maximum Latency (ms) | 0.76 | 2 |
| 95th Percentile Latency (ms) | 0.05 | 0.07 |
MySQL SELECT (Random Points)
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 12,080.00 | 6,349.00 |
| Queries per second | 120,800.00 | 63,490.00 |
| Minimum Latency (ms) | 0.21 | 0.37 |
| Average Latency (ms) | 0.83 | 1.57 |
| Maximum Latency (ms) | 3.31 | 3.86 |
| 95th Percentile Latency (ms) | 1.04 | 2.11 |
MySQL SELECT (Random Ranges)
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 10,527.00 | 7,578.00 |
| Queries per second | 105,270.00 | 75,780.00 |
| Minimum Latency (ms) | 0.16 | 0.33 |
| Average Latency (ms) | 0.95 | 1.32 |
| Maximum Latency (ms) | 3.25 | 3.34 |
| 95th Percentile Latency (ms) | 1.23 | 1.79 |
MySQL UPDATE (Indexed)
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 17,123.00 | 12,520.00 |
| Queries per second | 171,230.00 | 125,200.00 |
| Minimum Latency (ms) | 0.38 | 0.44 |
| Average Latency (ms) | 0.58 | 0.8 |
| Maximum Latency (ms) | 2 | 3.4 |
| 95th Percentile Latency (ms) | 0.78 | 1.06 |
MySQL UPDATE (Non-Indexed)
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 16,979.00 | 13,084.00 |
| Queries per second | 169,790.00 | 130,840.00 |
| Minimum Latency (ms) | 0.38 | 0.45 |
| Average Latency (ms) | 0.59 | 0.76 |
| Maximum Latency (ms) | 4.13 | 4.55 |
| 95th Percentile Latency (ms) | 0.8 | 0.99 |
MySQL DELETE
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| Transactions per second | 156,424.00 | 116,263.00 |
| Queries per second | 1,564,240.00 | 1,162,630.00 |
| Minimum Latency (ms) | 0.03 | 0.03 |
| Average Latency (ms) | 0.06 | 0.09 |
| Maximum Latency (ms) | 4.87 | 3.79 |
| 95th Percentile Latency (ms) | 0.07 | 0.12 |
Redis
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| PING_INLINE per Second | 88,652.48 | 53,022.27 |
| PING_MBULK per Second | 89,605.73 | 58,139.54 |
| SET per Second | 90,171.33 | 58,309.04 |
| GET per Second | 90,579.71 | 59,453.03 |
| INCR per Second | 90,744.10 | 60,024.01 |
| LPUSH per Second | 90,497.73 | 58,997.05 |
| RPUSH per Second | 90,415.91 | 59,916.12 |
| LPOP per Second | 90,909.09 | 60,938.45 |
| RPOP per Second | 90,661.83 | 61,804.70 |
| SADD per Second | 90,252.70 | 62,189.05 |
| HSET per Second | 90,415.91 | 63,131.31 |
| SPOP per Second | 89,928.05 | 61,274.51 |
| ZADD per Second | 90,415.91 | 61,312.08 |
| ZPOPMIN per Second | 90,009.01 | 63,653.72 |
| LRANGE_100 (first 100 elements) per Second | 66,533.60 | 42,535.09 |
| LRANGE_300 (first 300 elements) per Second | 36,179.45 | 25,018.76 |
| LRANGE_500 (first 500 elements) per Second | 26,239.83 | 17,895.49 |
| LRANGE_600 (first 600 elements) per Second | 22,547.91 | 15,649.45 |
| MSET (10 keys) per Second | 88,105.73 | 61,199.51 |
Redis Average Latency (ms)
| Vultr – High Frequency Intel (2 GB, 2 Cores) | Vultr – High Performance Intel (8 GB, 4 Cores) | |
|---|---|---|
| PING_INLINE | 0.30 | 0.49 |
| PING_MBULK | 0.29 | 0.44 |
| SET | 0.29 | 0.44 |
| GET | 0.29 | 0.43 |
| INCR | 0.28 | 0.43 |
| LPUSH | 0.29 | 0.44 |
| RPUSH | 0.29 | 0.43 |
| LPOP | 0.28 | 0.43 |
| RPOP | 0.28 | 0.42 |
| SADD | 0.29 | 0.47 |
| HSET | 0.29 | 0.45 |
| SPOP | 0.29 | 0.42 |
| ZADD | 0.29 | 0.43 |
| ZPOPMIN | 0.29 | 0.45 |
| LRANGE_100 (first 100 elements) | 0.39 | 0.87 |
| LRANGE_300 (first 300 elements) | 0.71 | 1.46 |
| LRANGE_500 (first 500 elements) | 0.97 | 1.69 |
| LRANGE_600 (first 600 elements) | 1.14 | 1.77 |
| MSET (10 keys) | 0.30 | 0.45 |
Conclusion
From the friendly robots:
Upon analyzing the benchmark performance, the High Frequency Intel (2 GB, 2 Cores) instance from Vultr shows excellent performance in Redis operations with high request rates per second (rps) and low latency across various commands, along with good CPU and file I/O performance, making it suitable for memory-intensive and low-latency applications. Conversely, the High Performance Intel (8 GB, 4 Cores) instance demonstrates superior overall performance across the board, with higher rps rates, lower latencies, and more robust CPU, memory, and I/O operations, making it ideal for CPU-intensive, I/O-heavy, and large-scale applications requiring substantial computational and data throughput capabilities. The choice between these instances will depend on the specific needs of your workload, with the former being a strong choice for less demanding tasks and the latter excelling in more resource-intensive scenarios.
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.