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

vs.

Fresh benchmarks coming at ya. Today I've spun up some brand new instance from Vultr to run some benchmarks on. All instances were spun up with Ubuntu 24.04 LTS x64 and were created in the New York area (or close to it). Time to see who showed up today.

Overview

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance Intel (4 GB, 2 Cores)
Last Benchmarked Sat, 23 May 2026 11:00:52 GMT Sat, 23 May 2026 02: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 $40.00 $24.00
RAM (GB) 8 4
CPU Cores 4 2
Storage (TB) 160 100
Storage Type SSD NVMe
Transfer (TB) 4 5

CPU

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance Intel (4 GB, 2 Cores)
Vendor GenuineIntel GenuineIntel
Model Name Intel Xeon Processor (Skylake, IBRS) Intel Xeon Processor (Cascadelake)
Clock Speed (MHz) 2,593.90 2,893.20
CPU Cache Size (KB) 16,384.00 16,384.00
BogoMips 5,187.80 5,786.40
Events per Second 1,100.82 1,147.81
Minimum Latency (ms) 0.88 0.83
Average Latency (ms) 0.91 0.87
Maximum Latency (ms) 1.56 2.59
95th Percentile Latency (ms) 0.97 0.95

Memory

Memory Read

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance Intel (4 GB, 2 Cores)
Operations per second 3,685,781.23 5,252,644.69
Mebibytes per second 3,599.40 5,129.54
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 1.03 0.4
95th Percentile Latency (ms) 0 0

Memory Write

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance Intel (4 GB, 2 Cores)
Operations per second 3,590,629.63 5,265,823.22
Mebibytes per second 3,506.47 5,142.41
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 1.16 0.9
95th Percentile Latency (ms) 0 0

File I/O

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance Intel (4 GB, 2 Cores)
Reads per Second 4,999.39 8,574.40
Writes per Second 3,332.93 5,716.26
Fsyncs per Second 10,670.47 18,293.44
Read Mebibytes per Second 78.12 133.97
Written Mebibytes per Second 52.08 89.32
Minimum Latency (ms) 0 0
Average Latency (ms) 0.05 0.03
Maximum Latency (ms) 37.52 10.32
95th Percentile Latency (ms) 0.18 0.09

Mutex

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance Intel (4 GB, 2 Cores)
Minimum Latency (ms) 369.37 800.81
Average Latency (ms) 416.22 810.92
Maximum Latency (ms) 441.77 817.00
95th Percentile Latency (ms) 442.73 816.63

MySQL

MySQL Read-only

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance Intel (4 GB, 2 Cores)
Transactions per second 5,144.00 7,453.00
Queries per second 51,440.00 74,530.00
Minimum Latency (ms) 1.72 1.11
Average Latency (ms) 1.94 1.34
Maximum Latency (ms) 7.67 19.41
95th Percentile Latency (ms) 2.35 1.76

MySQL Write-only

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance Intel (4 GB, 2 Cores)
Transactions per second 5,108.00 8,696.00
Queries per second 51,080.00 86,960.00
Minimum Latency (ms) 1.15 0.78
Average Latency (ms) 1.96 1.15
Maximum Latency (ms) 12.52 3.13
95th Percentile Latency (ms) 2.71 1.55

MySQL Read/Write

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance Intel (4 GB, 2 Cores)
Transactions per second 2,247.00 3,942.00
Queries per second 22,470.00 39,420.00
Minimum Latency (ms) 3.08 1.97
Average Latency (ms) 4.45 2.53
Maximum Latency (ms) 29.7 6.89
95th Percentile Latency (ms) 5.28 3.19

MySQL INSERT

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance Intel (4 GB, 2 Cores)
Transactions per second 7,630.00 15,222.00
Queries per second 76,300.00 152,220.00
Minimum Latency (ms) 0.71 0.42
Average Latency (ms) 1.31 0.65
Maximum Latency (ms) 29.81 2.85
95th Percentile Latency (ms) 1.55 0.89

MySQL Bulk INSERT

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance Intel (4 GB, 2 Cores)
Transactions per second 898,571.00 1,579,717.00
Queries per second 8,985,710.00 15,797,170.00
Minimum Latency (ms) 0 0
Average Latency (ms) 0.01 0.01
Maximum Latency (ms) 505.86 298.32
95th Percentile Latency (ms) 0 0

MySQL SELECT

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance Intel (4 GB, 2 Cores)
Transactions per second 149,465.00 193,212.00
Queries per second 1,494,650.00 1,932,120.00
Minimum Latency (ms) 0.05 0.03
Average Latency (ms) 0.07 0.05
Maximum Latency (ms) 1.22 1.26
95th Percentile Latency (ms) 0.09 0.07

MySQL SELECT (Random Points)

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance Intel (4 GB, 2 Cores)
Transactions per second 4,249.00 7,012.00
Queries per second 42,490.00 70,120.00
Minimum Latency (ms) 0.83 0.37
Average Latency (ms) 2.35 1.42
Maximum Latency (ms) 6.6 4.26
95th Percentile Latency (ms) 3.02 1.93

MySQL SELECT (Random Ranges)

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance Intel (4 GB, 2 Cores)
Transactions per second 2,637.00 7,451.00
Queries per second 26,370.00 74,510.00
Minimum Latency (ms) 0.94 0.53
Average Latency (ms) 3.79 1.34
Maximum Latency (ms) 6.3 3.04
95th Percentile Latency (ms) 5.09 1.82

MySQL UPDATE (Indexed)

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance Intel (4 GB, 2 Cores)
Transactions per second 7,166.00 15,219.00
Queries per second 71,660.00 152,190.00
Minimum Latency (ms) 0.7 0.41
Average Latency (ms) 1.39 0.66
Maximum Latency (ms) 28.84 2.9
95th Percentile Latency (ms) 1.79 0.9

MySQL UPDATE (Non-Indexed)

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance Intel (4 GB, 2 Cores)
Transactions per second 7,661.00 15,386.00
Queries per second 76,610.00 153,860.00
Minimum Latency (ms) 0.7 0.41
Average Latency (ms) 1.3 0.65
Maximum Latency (ms) 33.97 4.05
95th Percentile Latency (ms) 1.58 0.89

MySQL DELETE

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance Intel (4 GB, 2 Cores)
Transactions per second 69,690.00 132,809.00
Queries per second 696,900.00 1,328,090.00
Minimum Latency (ms) 0.05 0.03
Average Latency (ms) 0.14 0.07
Maximum Latency (ms) 27.73 2.36
95th Percentile Latency (ms) 0.87 0.11

Redis

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance Intel (4 GB, 2 Cores)
PING_INLINE per Second 54,436.58 62,656.64
PING_MBULK per Second 48,828.12 63,251.11
SET per Second 51,572.98 64,350.06
GET per Second 48,239.27 62,421.97
INCR per Second 52,328.62 63,211.12
LPUSH per Second 45,454.54 65,832.78
RPUSH per Second 49,751.24 64,892.93
LPOP per Second 53,390.28 66,844.91
RPOP per Second 53,648.07 64,599.48
SADD per Second 48,285.85 59,952.04
HSET per Second 51,493.30 62,073.25
SPOP per Second 52,910.05 60,240.96
ZADD per Second 53,504.55 63,532.40
ZPOPMIN per Second 53,590.57 61,766.52
LRANGE_100 (first 100 elements) per Second 28,645.09 43,478.26
LRANGE_300 (first 300 elements) per Second 13,131.98 25,387.15
LRANGE_500 (first 500 elements) per Second 8,529.51 18,234.87
LRANGE_600 (first 600 elements) per Second 7,479.99 15,257.86
MSET (10 keys) per Second 49,212.60 60,132.29

Redis Average Latency (ms)

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance Intel (4 GB, 2 Cores)
PING_INLINE0.470.43
PING_MBULK0.530.41
SET0.500.41
GET0.540.41
INCR0.490.41
LPUSH0.580.40
RPUSH0.520.40
LPOP0.490.39
RPOP0.480.42
SADD0.540.44
HSET0.530.42
SPOP0.490.43
ZADD0.480.42
ZPOPMIN0.480.42
LRANGE_100 (first 100 elements)0.910.62
LRANGE_300 (first 300 elements)1.941.14
LRANGE_500 (first 500 elements)3.001.58
LRANGE_600 (first 600 elements)3.431.98
MSET (10 keys)0.770.46

Conclusion

From the friendly robots:

When comparing the two Vultr instances, it's clear that the Cloud Compute (8 GB, 4 Cores) instance provides superior performance across the board for most tasks, especially in memory and file I/O operations where it shows higher throughput and lower latencies. However, the High Performance Intel (4 GB, 2 Cores) instance excels in Redis benchmarks, displaying higher request per second rates and significantly lower latencies for various Redis commands, suggesting it is more suited for applications that rely heavily on fast in-memory data handling. Both instances offer robust CPU performance, but the 8 GB instance has a slight edge in handling larger workloads due to its higher RAM and storage capacities, making it a better choice for CPU-intensive or memory-heavy tasks, whereas the 4 GB instance could be more cost-effective for applications that prioritize Redis performance over overall computational capacity.

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.