Vultr Cloud Compute (4 GB, 2 Cores) vs. Vultr High Frequency Intel (4 GB, 2 Cores)

vs.

Same showdown, different day. Today I've spun up some 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 or around the New York / New Jersey area. Time to see who showed up today.

Overview

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Frequency Intel (4 GB, 2 Cores)
Last Benchmarked Thu, 11 Jun 2026 09:00:52 GMT Wed, 10 Jun 2026 03:00:53 GMT
Linux Distro Ubuntu 24.04 LTS x64 Ubuntu 24.04 LTS x64
Kernel Version 6.8.0-124-generic 6.8.0-124-generic
MySQL Version 8.0.46-0ubuntu0.24.04.2 8.0.46-0ubuntu0.24.04.2
Redis Version 7.0.15 7.0.15
Location Newark, NJ Newark, NJ
Monthly Price $20.00 $24.00
RAM (GB) 4 4
CPU Cores 2 2
Storage (TB) 80 128
Storage Type SSD NVMe
Transfer (TB) 3 3

CPU

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Frequency Intel (4 GB, 2 Cores)
Vendor GenuineIntel GenuineIntel
Model Name Intel Xeon Processor (Skylake, IBRS) Intel Core Processor (Skylake, IBRS, no TSX)
Clock Speed (MHz) 2,593.91 3,792.00
CPU Cache Size (KB) 16,384.00 16,384.00
BogoMips 5,187.81 7,583.99
Events per Second 1,022.39 1,594.80
Minimum Latency (ms) 0.88 0.61
Average Latency (ms) 0.98 0.63
Maximum Latency (ms) 1.77 0.99
95th Percentile Latency (ms) 1.21 0.67

Memory

Memory Read

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Frequency Intel (4 GB, 2 Cores)
Operations per second 3,523,809.57 7,900,769.28
Mebibytes per second 3,441.22 7,715.59
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 0.22 0.27
95th Percentile Latency (ms) 0 0

Memory Write

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Frequency Intel (4 GB, 2 Cores)
Operations per second 3,568,203.77 7,874,840.92
Mebibytes per second 3,484.57 7,690.27
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 1.02 1.12
95th Percentile Latency (ms) 0 0

File I/O

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Frequency Intel (4 GB, 2 Cores)
Reads per Second 2,972.63 7,560.59
Writes per Second 1,981.75 5,040.36
Fsyncs per Second 6,347.81 16,129.48
Read Mebibytes per Second 46.45 118.13
Written Mebibytes per Second 30.96 78.76
Minimum Latency (ms) 0 0
Average Latency (ms) 0.09 0.03
Maximum Latency (ms) 17.12 3.76
95th Percentile Latency (ms) 0.33 0.13

Mutex

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Frequency Intel (4 GB, 2 Cores)
Minimum Latency (ms) 899.28 488.87
Average Latency (ms) 935.93 535.13
Maximum Latency (ms) 969.92 560.03
95th Percentile Latency (ms) 977.74 559.50

MySQL

MySQL Read-only

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Frequency Intel (4 GB, 2 Cores)
Transactions per second 3,779.00 10,436.00
Queries per second 37,790.00 104,360.00
Minimum Latency (ms) 1.84 0.87
Average Latency (ms) 2.64 0.96
Maximum Latency (ms) 24.55 2.15
95th Percentile Latency (ms) 3.82 1.1

MySQL Write-only

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Frequency Intel (4 GB, 2 Cores)
Transactions per second 4,044.00 10,763.00
Queries per second 40,440.00 107,630.00
Minimum Latency (ms) 1.4 0.63
Average Latency (ms) 2.47 0.93
Maximum Latency (ms) 13.46 2.46
95th Percentile Latency (ms) 3.3 1.23

MySQL Read/Write

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Frequency Intel (4 GB, 2 Cores)
Transactions per second 1,798.00 4,891.00
Queries per second 17,980.00 48,910.00
Minimum Latency (ms) 3.86 1.56
Average Latency (ms) 5.56 2.04
Maximum Latency (ms) 27.33 4.33
95th Percentile Latency (ms) 6.91 2.57

MySQL INSERT

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Frequency Intel (4 GB, 2 Cores)
Transactions per second 6,405.00 17,483.00
Queries per second 64,050.00 174,830.00
Minimum Latency (ms) 0.99 0.37
Average Latency (ms) 1.56 0.57
Maximum Latency (ms) 15.15 2.77
95th Percentile Latency (ms) 2.03 0.8

MySQL Bulk INSERT

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Frequency Intel (4 GB, 2 Cores)
Transactions per second 865,805.00 2,307,842.00
Queries per second 8,658,050.00 23,078,420.00
Minimum Latency (ms) 0 0
Average Latency (ms) 0.01 0
Maximum Latency (ms) 538.25 248.91
95th Percentile Latency (ms) 0 0

MySQL SELECT

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Frequency Intel (4 GB, 2 Cores)
Transactions per second 126,618.00 239,222.00
Queries per second 1,266,180.00 2,392,220.00
Minimum Latency (ms) 0.05 0.03
Average Latency (ms) 0.08 0.04
Maximum Latency (ms) 2.46 0.53
95th Percentile Latency (ms) 0.11 0.05

MySQL SELECT (Random Points)

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Frequency Intel (4 GB, 2 Cores)
Transactions per second 3,674.00 12,005.00
Queries per second 36,740.00 120,050.00
Minimum Latency (ms) 1.07 0.29
Average Latency (ms) 2.72 0.83
Maximum Latency (ms) 6.45 2.25
95th Percentile Latency (ms) 3.55 1.08

MySQL SELECT (Random Ranges)

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Frequency Intel (4 GB, 2 Cores)
Transactions per second 2,728.00 10,500.00
Queries per second 27,280.00 105,000.00
Minimum Latency (ms) 1.3 0.33
Average Latency (ms) 3.66 0.95
Maximum Latency (ms) 11.85 3.74
95th Percentile Latency (ms) 5 1.25

MySQL UPDATE (Indexed)

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Frequency Intel (4 GB, 2 Cores)
Transactions per second 5,438.00 16,647.00
Queries per second 54,380.00 166,470.00
Minimum Latency (ms) 0.99 0.38
Average Latency (ms) 1.84 0.6
Maximum Latency (ms) 13.86 3.02
95th Percentile Latency (ms) 2.71 0.87

MySQL UPDATE (Non-Indexed)

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Frequency Intel (4 GB, 2 Cores)
Transactions per second 6,370.00 16,754.00
Queries per second 63,700.00 167,540.00
Minimum Latency (ms) 1.01 0.38
Average Latency (ms) 1.57 0.6
Maximum Latency (ms) 8.99 1.62
95th Percentile Latency (ms) 2.07 0.8

MySQL DELETE

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Frequency Intel (4 GB, 2 Cores)
Transactions per second 51,180.00 155,630.00
Queries per second 511,800.00 1,556,300.00
Minimum Latency (ms) 0.05 0.03
Average Latency (ms) 0.19 0.06
Maximum Latency (ms) 6.11 3.76
95th Percentile Latency (ms) 1.39 0.07

Redis

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Frequency Intel (4 GB, 2 Cores)
PING_INLINE per Second 49,677.10 84,459.46
PING_MBULK per Second 45,372.05 85,689.80
SET per Second 45,392.64 86,355.79
GET per Second 53,163.21 86,355.79
INCR per Second 48,732.94 86,206.90
LPUSH per Second 50,327.12 86,880.97
RPUSH per Second 48,285.85 85,984.52
LPOP per Second 48,355.90 86,956.52
RPOP per Second 51,413.88 85,106.38
SADD per Second 48,332.53 81,766.15
HSET per Second 49,285.36 81,433.22
SPOP per Second 48,332.53 82,781.46
ZADD per Second 51,229.51 84,889.65
ZPOPMIN per Second 45,085.66 80,256.82
LRANGE_100 (first 100 elements) per Second 27,122.32 59,880.24
LRANGE_300 (first 300 elements) per Second 12,442.45 32,071.84
LRANGE_500 (first 500 elements) per Second 7,930.21 24,420.03
LRANGE_600 (first 600 elements) per Second 6,902.74 21,533.16
MSET (10 keys) per Second 45,146.73 88,339.23

Redis Average Latency (ms)

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Frequency Intel (4 GB, 2 Cores)
PING_INLINE0.530.31
PING_MBULK0.570.30
SET0.570.30
GET0.490.30
INCR0.530.30
LPUSH0.510.30
RPUSH0.540.30
LPOP0.540.30
RPOP0.520.30
SADD0.550.32
HSET0.540.32
SPOP0.540.31
ZADD0.520.31
ZPOPMIN0.570.32
LRANGE_100 (first 100 elements)1.020.46
LRANGE_300 (first 300 elements)2.290.83
LRANGE_500 (first 500 elements)3.271.08
LRANGE_600 (first 600 elements)3.911.22
MSET (10 keys)0.780.31

Conclusion

From the friendly robots:

Upon analyzing the benchmark results, the Vultr High Frequency Intel instance (2 cores, 4 GB RAM, NVMe storage) outperforms the Cloud Compute instance (also 2 cores, 4 GB RAM) across all tested metrics. The High Frequency instance shows superior performance in Redis operations, CPU utilization, file I/O operations, and memory transfer rates, with significantly lower latencies and higher throughput values. The Cloud Compute instance, while still competent, lags behind in most metrics, particularly in more complex operations like large range retrievals in Redis. Given these results, the High Frequency Intel instance is better suited for demanding applications requiring high throughput and low latency, such as real-time data processing and high-frequency trading systems, while the Cloud Compute instance may be more appropriate for less demanding workloads or cost-sensitive applications.

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.