Vultr Cloud Compute (4 GB, 2 Cores) vs. Vultr High Performance Intel (2 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. Each instance was spun up with 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 Performance Intel (2 GB, 2 Cores)
Last Benchmarked Thu, 11 Jun 2026 09:00:52 GMT Wed, 10 Jun 2026 05:00:52 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 $18.00
RAM (GB) 4 2
CPU Cores 2 2
Storage (TB) 80 60
Storage Type SSD NVMe
Transfer (TB) 3 4

CPU

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Performance Intel (2 GB, 2 Cores)
Vendor GenuineIntel GenuineIntel
Model Name Intel Xeon Processor (Skylake, IBRS) Intel Xeon Processor (Cascadelake)
Clock Speed (MHz) 2,593.91 2,893.20
CPU Cache Size (KB) 16,384.00 16,384.00
BogoMips 5,187.81 5,786.40
Events per Second 1,022.39 1,169.25
Minimum Latency (ms) 0.88 0.83
Average Latency (ms) 0.98 0.85
Maximum Latency (ms) 1.77 5.36
95th Percentile Latency (ms) 1.21 0.9

Memory

Memory Read

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Performance Intel (2 GB, 2 Cores)
Operations per second 3,523,809.57 5,411,395.93
Mebibytes per second 3,441.22 5,284.57
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 0.22 0.61
95th Percentile Latency (ms) 0 0

Memory Write

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Performance Intel (2 GB, 2 Cores)
Operations per second 3,568,203.77 5,435,853.49
Mebibytes per second 3,484.57 5,308.45
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 1.02 0.18
95th Percentile Latency (ms) 0 0

File I/O

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Performance Intel (2 GB, 2 Cores)
Reads per Second 2,972.63 5,210.92
Writes per Second 1,981.75 3,473.95
Fsyncs per Second 6,347.81 11,118.74
Read Mebibytes per Second 46.45 81.42
Written Mebibytes per Second 30.96 54.28
Minimum Latency (ms) 0 0
Average Latency (ms) 0.09 0.05
Maximum Latency (ms) 17.12 2.57
95th Percentile Latency (ms) 0.33 0.15

Mutex

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Performance Intel (2 GB, 2 Cores)
Minimum Latency (ms) 899.28 575.32
Average Latency (ms) 935.93 751.26
Maximum Latency (ms) 969.92 786.35
95th Percentile Latency (ms) 977.74 787.74

MySQL

MySQL Read-only

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Performance Intel (2 GB, 2 Cores)
Transactions per second 3,779.00 8,449.00
Queries per second 37,790.00 84,490.00
Minimum Latency (ms) 1.84 1.08
Average Latency (ms) 2.64 1.18
Maximum Latency (ms) 24.55 2.32
95th Percentile Latency (ms) 3.82 1.32

MySQL Write-only

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Performance Intel (2 GB, 2 Cores)
Transactions per second 4,044.00 10,071.00
Queries per second 40,440.00 100,710.00
Minimum Latency (ms) 1.4 0.72
Average Latency (ms) 2.47 0.99
Maximum Latency (ms) 13.46 3.03
95th Percentile Latency (ms) 3.3 1.3

MySQL Read/Write

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Performance Intel (2 GB, 2 Cores)
Transactions per second 1,798.00 4,394.00
Queries per second 17,980.00 43,940.00
Minimum Latency (ms) 3.86 1.9
Average Latency (ms) 5.56 2.27
Maximum Latency (ms) 27.33 4.74
95th Percentile Latency (ms) 6.91 2.76

MySQL INSERT

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Performance Intel (2 GB, 2 Cores)
Transactions per second 6,405.00 18,253.00
Queries per second 64,050.00 182,530.00
Minimum Latency (ms) 0.99 0.4
Average Latency (ms) 1.56 0.55
Maximum Latency (ms) 15.15 3.79
95th Percentile Latency (ms) 2.03 0.68

MySQL Bulk INSERT

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Performance Intel (2 GB, 2 Cores)
Transactions per second 865,805.00 1,696,217.00
Queries per second 8,658,050.00 16,962,170.00
Minimum Latency (ms) 0 0
Average Latency (ms) 0.01 0.01
Maximum Latency (ms) 538.25 276.74
95th Percentile Latency (ms) 0 0

MySQL SELECT

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Performance Intel (2 GB, 2 Cores)
Transactions per second 126,618.00 210,617.00
Queries per second 1,266,180.00 2,106,170.00
Minimum Latency (ms) 0.05 0.03
Average Latency (ms) 0.08 0.05
Maximum Latency (ms) 2.46 1.09
95th Percentile Latency (ms) 0.11 0.06

MySQL SELECT (Random Points)

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Performance Intel (2 GB, 2 Cores)
Transactions per second 3,674.00 8,355.00
Queries per second 36,740.00 83,550.00
Minimum Latency (ms) 1.07 0.53
Average Latency (ms) 2.72 1.2
Maximum Latency (ms) 6.45 3.63
95th Percentile Latency (ms) 3.55 1.52

MySQL SELECT (Random Ranges)

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Performance Intel (2 GB, 2 Cores)
Transactions per second 2,728.00 8,301.00
Queries per second 27,280.00 83,010.00
Minimum Latency (ms) 1.3 0.42
Average Latency (ms) 3.66 1.2
Maximum Latency (ms) 11.85 2.57
95th Percentile Latency (ms) 5 1.55

MySQL UPDATE (Indexed)

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Performance Intel (2 GB, 2 Cores)
Transactions per second 5,438.00 17,582.00
Queries per second 54,380.00 175,820.00
Minimum Latency (ms) 0.99 0.4
Average Latency (ms) 1.84 0.57
Maximum Latency (ms) 13.86 9.2
95th Percentile Latency (ms) 2.71 0.74

MySQL UPDATE (Non-Indexed)

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Performance Intel (2 GB, 2 Cores)
Transactions per second 6,370.00 18,457.00
Queries per second 63,700.00 184,570.00
Minimum Latency (ms) 1.01 0.39
Average Latency (ms) 1.57 0.54
Maximum Latency (ms) 8.99 1.59
95th Percentile Latency (ms) 2.07 0.67

MySQL DELETE

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Performance Intel (2 GB, 2 Cores)
Transactions per second 51,180.00 155,310.00
Queries per second 511,800.00 1,553,100.00
Minimum Latency (ms) 0.05 0.03
Average Latency (ms) 0.19 0.06
Maximum Latency (ms) 6.11 3.74
95th Percentile Latency (ms) 1.39 0.08

Redis

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Performance Intel (2 GB, 2 Cores)
PING_INLINE per Second 49,677.10 67,796.61
PING_MBULK per Second 45,372.05 67,114.09
SET per Second 45,392.64 68,917.99
GET per Second 53,163.21 69,492.70
INCR per Second 48,732.94 69,013.11
LPUSH per Second 50,327.12 70,323.48
RPUSH per Second 48,285.85 69,783.67
LPOP per Second 48,355.90 70,472.16
RPOP per Second 51,413.88 70,274.07
SADD per Second 48,332.53 69,444.45
HSET per Second 49,285.36 68,823.12
SPOP per Second 48,332.53 69,252.08
ZADD per Second 51,229.51 69,396.25
ZPOPMIN per Second 45,085.66 69,492.70
LRANGE_100 (first 100 elements) per Second 27,122.32 51,519.84
LRANGE_300 (first 300 elements) per Second 12,442.45 29,515.94
LRANGE_500 (first 500 elements) per Second 7,930.21 18,910.74
LRANGE_600 (first 600 elements) per Second 6,902.74 17,424.64
MSET (10 keys) per Second 45,146.73 71,073.21

Redis Average Latency (ms)

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Performance Intel (2 GB, 2 Cores)
PING_INLINE0.530.38
PING_MBULK0.570.39
SET0.570.37
GET0.490.37
INCR0.530.37
LPUSH0.510.37
RPUSH0.540.37
LPOP0.540.37
RPOP0.520.37
SADD0.550.37
HSET0.540.37
SPOP0.540.37
ZADD0.520.37
ZPOPMIN0.570.37
LRANGE_100 (first 100 elements)1.020.51
LRANGE_300 (first 300 elements)2.290.90
LRANGE_500 (first 500 elements)3.271.43
LRANGE_600 (first 600 elements)3.911.52
MSET (10 keys)0.780.37

Conclusion

From the friendly robots:

In comparing the two Vultr instances, the Cloud Compute (4 GB, 2 Cores) and the High Performance Intel (2 GB, 2 Cores) benchmarks, the former showcases higher memory throughput and slightly better CPU performance with more RAM and comparable cores, while the latter exhibits superior Redis benchmark results, notably in read operations and throughput, and also performs better in MySQL and general file I/O operations due to its Intel Cascade Lake CPU. The Cloud Compute instance shows a slight edge in handling memory-intensive tasks and has a more substantial random read/write throughput. Conversely, the High Performance Intel instance has a higher Redis request per second and better latency in most benchmarks, indicating it might excel in data processing and high-speed data operations. For users needing more RAM and better memory throughput, the Cloud Compute instance would be ideal, whereas the High Performance Intel would be more suited for Redis-heavy workloads and systems that benefit from the higher clock speed and efficient data processing of the Intel Cascade Lake CPU.

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.