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

vs.

Welcome to another round of the VPS Showdown. Today I've spun up some brand new instance from Vultr and ran my world famous suite of benchmarking scripts. 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 (2 GB, 2 Cores) Vultr – High Performance Intel (8 GB, 4 Cores)
Last Benchmarked Mon, 11 May 2026 04:00:52 GMT Tue, 12 May 2026 15:00:51 GMT
Linux Distro Ubuntu 24.04 LTS x64 Ubuntu 24.04 LTS x64
Kernel Version 6.8.0-111-generic 6.8.0-111-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 $15.00 $48.00
RAM (GB) 2 8
CPU Cores 2 4
Storage (TB) 65 180
Storage Type SSD NVMe
Transfer (TB) 3 6

CPU

Vultr – Cloud Compute (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,792.00 2,893.17
CPU Cache Size (KB) 16,384.00 16,384.00
BogoMips 7,583.99 5,786.33
Events per Second 1,481.60 1,059.70
Minimum Latency (ms) 0.63 0.83
Average Latency (ms) 0.67 0.94
Maximum Latency (ms) 1.95 3.58
95th Percentile Latency (ms) 0.77 1.14

Memory

Memory Read

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance Intel (8 GB, 4 Cores)
Operations per second 6,401,389.08 4,705,509.24
Mebibytes per second 6,251.36 4,595.22
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 0.23 2.22
95th Percentile Latency (ms) 0 0

Memory Write

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance Intel (8 GB, 4 Cores)
Operations per second 6,411,085.35 4,676,375.38
Mebibytes per second 6,260.83 4,566.77
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 0.18 3.29
95th Percentile Latency (ms) 0 0

File I/O

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance Intel (8 GB, 4 Cores)
Reads per Second 4,345.71 5,906.11
Writes per Second 2,897.07 3,937.40
Fsyncs per Second 9,273.19 12,611.69
Read Mebibytes per Second 67.90 92.28
Written Mebibytes per Second 45.27 61.52
Minimum Latency (ms) 0 0
Average Latency (ms) 0.06 0.04
Maximum Latency (ms) 2.92 82.27
95th Percentile Latency (ms) 0.17 0.14

Mutex

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance Intel (8 GB, 4 Cores)
Minimum Latency (ms) 214.63 408.47
Average Latency (ms) 569.72 478.75
Maximum Latency (ms) 636.55 528.55
95th Percentile Latency (ms) 634.66 530.08

MySQL

MySQL Read-only

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance Intel (8 GB, 4 Cores)
Transactions per second 8,015.00 5,148.00
Queries per second 80,150.00 51,480.00
Minimum Latency (ms) 0.92 1.24
Average Latency (ms) 1.25 1.94
Maximum Latency (ms) 5.5 16.42
95th Percentile Latency (ms) 1.86 2.66

MySQL Write-only

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance Intel (8 GB, 4 Cores)
Transactions per second 8,497.00 4,781.00
Queries per second 84,970.00 47,810.00
Minimum Latency (ms) 0.76 1.01
Average Latency (ms) 1.17 2.09
Maximum Latency (ms) 3.04 9.33
95th Percentile Latency (ms) 1.55 3.07

MySQL Read/Write

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance Intel (8 GB, 4 Cores)
Transactions per second 3,726.00 2,243.00
Queries per second 37,260.00 22,430.00
Minimum Latency (ms) 1.78 2.88
Average Latency (ms) 2.68 4.45
Maximum Latency (ms) 5.82 24.12
95th Percentile Latency (ms) 3.43 6.09

MySQL INSERT

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance Intel (8 GB, 4 Cores)
Transactions per second 15,028.00 6,381.00
Queries per second 150,280.00 63,810.00
Minimum Latency (ms) 0.41 0.61
Average Latency (ms) 0.66 1.56
Maximum Latency (ms) 2.42 29.34
95th Percentile Latency (ms) 0.86 2.52

MySQL Bulk INSERT

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance Intel (8 GB, 4 Cores)
Transactions per second 1,696,217.00 1,346,717.00
Queries per second 16,962,170.00 13,467,170.00
Minimum Latency (ms) 0 0
Average Latency (ms) 0.01 0.01
Maximum Latency (ms) 283.37 473.72
95th Percentile Latency (ms) 0 0

MySQL SELECT

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance Intel (8 GB, 4 Cores)
Transactions per second 201,989.00 151,547.00
Queries per second 2,019,890.00 1,515,470.00
Minimum Latency (ms) 0.03 0.03
Average Latency (ms) 0.05 0.07
Maximum Latency (ms) 0.51 3.93
95th Percentile Latency (ms) 0.07 0.12

MySQL SELECT (Random Points)

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance Intel (8 GB, 4 Cores)
Transactions per second 8,025.00 5,574.00
Queries per second 80,250.00 55,740.00
Minimum Latency (ms) 0.35 0.48
Average Latency (ms) 1.24 1.79
Maximum Latency (ms) 3.55 7.01
95th Percentile Latency (ms) 2.07 2.57

MySQL SELECT (Random Ranges)

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance Intel (8 GB, 4 Cores)
Transactions per second 8,336.00 6,208.00
Queries per second 83,360.00 62,080.00
Minimum Latency (ms) 0.4 0.59
Average Latency (ms) 1.2 1.61
Maximum Latency (ms) 4.25 36.71
95th Percentile Latency (ms) 2.22 2.39

MySQL UPDATE (Indexed)

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance Intel (8 GB, 4 Cores)
Transactions per second 13,858.00 8,467.00
Queries per second 138,580.00 84,670.00
Minimum Latency (ms) 0.42 0.51
Average Latency (ms) 0.72 1.18
Maximum Latency (ms) 6.33 30.73
95th Percentile Latency (ms) 0.95 1.73

MySQL UPDATE (Non-Indexed)

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance Intel (8 GB, 4 Cores)
Transactions per second 14,587.00 8,471.00
Queries per second 145,870.00 84,710.00
Minimum Latency (ms) 0.4 0.52
Average Latency (ms) 0.68 1.18
Maximum Latency (ms) 11.69 61.8
95th Percentile Latency (ms) 0.9 1.73

MySQL DELETE

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance Intel (8 GB, 4 Cores)
Transactions per second 129,013.00 68,717.00
Queries per second 1,290,130.00 687,170.00
Minimum Latency (ms) 0.03 0.04
Average Latency (ms) 0.08 0.14
Maximum Latency (ms) 2.61 18.05
95th Percentile Latency (ms) 0.09 0.87

Redis

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance Intel (8 GB, 4 Cores)
PING_INLINE per Second 78,247.26 47,236.65
PING_MBULK per Second 74,738.41 49,067.71
SET per Second 77,041.60 45,641.26
GET per Second 83,333.33 45,495.91
INCR per Second 80,971.66 50,709.94
LPUSH per Second 79,113.92 47,505.94
RPUSH per Second 77,160.49 52,938.06
LPOP per Second 81,499.59 50,735.67
RPOP per Second 82,440.23 52,083.34
SADD per Second 80,192.46 46,232.08
HSET per Second 83,612.04 49,701.79
SPOP per Second 85,034.02 48,638.13
ZADD per Second 83,263.95 50,968.40
ZPOPMIN per Second 82,987.55 50,175.61
LRANGE_100 (first 100 elements) per Second 55,555.56 28,050.49
LRANGE_300 (first 300 elements) per Second 28,851.70 18,871.49
LRANGE_500 (first 500 elements) per Second 19,391.12 14,110.34
LRANGE_600 (first 600 elements) per Second 17,211.71 10,855.41
MSET (10 keys) per Second 80,256.82 46,274.87

Redis Average Latency (ms)

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance Intel (8 GB, 4 Cores)
PING_INLINE0.340.56
PING_MBULK0.350.56
SET0.340.59
GET0.320.59
INCR0.320.52
LPUSH0.340.56
RPUSH0.340.50
LPOP0.320.52
RPOP0.320.52
SADD0.320.61
HSET0.310.53
SPOP0.300.54
ZADD0.310.53
ZPOPMIN0.310.53
LRANGE_100 (first 100 elements)0.541.06
LRANGE_300 (first 300 elements)1.111.68
LRANGE_500 (first 500 elements)1.622.30
LRANGE_600 (first 600 elements)1.842.96
MSET (10 keys)0.380.65

Conclusion

From the friendly robots:

Comparing the two Vultr instances, the High Performance Intel (8 GB, 4 Cores) instance demonstrates superior overall performance across various metrics due to its higher CPU power, more RAM, and NVMe storage. It achieves higher requests per second (rps) and lower latencies in Redis benchmarks like GET, SET, and LPUSH, as well as better CPU, file I/O, memory, and MySQL performance. However, the Cloud Compute (2 GB, 2 Cores) instance still performs adequately for less demanding tasks and offers better price-performance for users prioritizing cost over raw performance, making it ideal for less CPU-intensive, I/O-heavy workloads, or when budget constraints are a concern.

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.