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

vs.

Same showdown, different day. Today I've spun up 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. Without further ado, here's the results.

Overview

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance Intel (2 GB, 2 Cores)
Last Benchmarked Mon, 11 May 2026 04:00:52 GMT Sun, 10 May 2026 11:00:52 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 $18.00
RAM (GB) 2 2
CPU Cores 2 2
Storage (TB) 65 60
Storage Type SSD NVMe
Transfer (TB) 3 4

CPU

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance Intel (2 GB, 2 Cores)
Vendor GenuineIntel GenuineIntel
Model Name Intel Core Processor (Skylake, IBRS, no TSX) Intel Xeon Processor (Cascadelake)
Clock Speed (MHz) 3,792.00 2,992.97
CPU Cache Size (KB) 16,384.00 16,384.00
BogoMips 7,583.99 5,985.94
Events per Second 1,481.60 1,206.35
Minimum Latency (ms) 0.63 0.81
Average Latency (ms) 0.67 0.83
Maximum Latency (ms) 1.95 3.72
95th Percentile Latency (ms) 0.77 0.87

Memory

Memory Read

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance Intel (2 GB, 2 Cores)
Operations per second 6,401,389.08 5,547,051.31
Mebibytes per second 6,251.36 5,417.04
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 0.23 0.26
95th Percentile Latency (ms) 0 0

Memory Write

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance Intel (2 GB, 2 Cores)
Operations per second 6,411,085.35 5,558,117.22
Mebibytes per second 6,260.83 5,427.85
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 0.18 0.27
95th Percentile Latency (ms) 0 0

File I/O

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance Intel (2 GB, 2 Cores)
Reads per Second 4,345.71 4,995.49
Writes per Second 2,897.07 3,330.33
Fsyncs per Second 9,273.19 10,663.75
Read Mebibytes per Second 67.90 78.05
Written Mebibytes per Second 45.27 52.04
Minimum Latency (ms) 0 0
Average Latency (ms) 0.06 0.05
Maximum Latency (ms) 2.92 2.44
95th Percentile Latency (ms) 0.17 0.16

Mutex

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance Intel (2 GB, 2 Cores)
Minimum Latency (ms) 214.63 683.77
Average Latency (ms) 569.72 748.22
Maximum Latency (ms) 636.55 783.12
95th Percentile Latency (ms) 634.66 787.74

MySQL

MySQL Read-only

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance Intel (2 GB, 2 Cores)
Transactions per second 8,015.00 8,426.00
Queries per second 80,150.00 84,260.00
Minimum Latency (ms) 0.92 1.06
Average Latency (ms) 1.25 1.19
Maximum Latency (ms) 5.5 2.7
95th Percentile Latency (ms) 1.86 1.42

MySQL Write-only

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance Intel (2 GB, 2 Cores)
Transactions per second 8,497.00 9,541.00
Queries per second 84,970.00 95,410.00
Minimum Latency (ms) 0.76 0.71
Average Latency (ms) 1.17 1.05
Maximum Latency (ms) 3.04 2.61
95th Percentile Latency (ms) 1.55 1.39

MySQL Read/Write

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance Intel (2 GB, 2 Cores)
Transactions per second 3,726.00 4,278.00
Queries per second 37,260.00 42,780.00
Minimum Latency (ms) 1.78 1.88
Average Latency (ms) 2.68 2.34
Maximum Latency (ms) 5.82 4.6
95th Percentile Latency (ms) 3.43 2.91

MySQL INSERT

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance Intel (2 GB, 2 Cores)
Transactions per second 15,028.00 17,143.00
Queries per second 150,280.00 171,430.00
Minimum Latency (ms) 0.41 0.41
Average Latency (ms) 0.66 0.58
Maximum Latency (ms) 2.42 4.51
95th Percentile Latency (ms) 0.86 0.74

MySQL Bulk INSERT

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance Intel (2 GB, 2 Cores)
Transactions per second 1,696,217.00 1,637,967.00
Queries per second 16,962,170.00 16,379,670.00
Minimum Latency (ms) 0 0
Average Latency (ms) 0.01 0.01
Maximum Latency (ms) 283.37 276.34
95th Percentile Latency (ms) 0 0

MySQL SELECT

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance Intel (2 GB, 2 Cores)
Transactions per second 201,989.00 214,349.00
Queries per second 2,019,890.00 2,143,490.00
Minimum Latency (ms) 0.03 0.03
Average Latency (ms) 0.05 0.05
Maximum Latency (ms) 0.51 1.06
95th Percentile Latency (ms) 0.07 0.06

MySQL SELECT (Random Points)

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance Intel (2 GB, 2 Cores)
Transactions per second 8,025.00 7,396.00
Queries per second 80,250.00 73,960.00
Minimum Latency (ms) 0.35 0.54
Average Latency (ms) 1.24 1.35
Maximum Latency (ms) 3.55 3.05
95th Percentile Latency (ms) 2.07 1.86

MySQL SELECT (Random Ranges)

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance Intel (2 GB, 2 Cores)
Transactions per second 8,336.00 7,947.00
Queries per second 83,360.00 79,470.00
Minimum Latency (ms) 0.4 0.46
Average Latency (ms) 1.2 1.26
Maximum Latency (ms) 4.25 3.14
95th Percentile Latency (ms) 2.22 1.7

MySQL UPDATE (Indexed)

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance Intel (2 GB, 2 Cores)
Transactions per second 13,858.00 16,993.00
Queries per second 138,580.00 169,930.00
Minimum Latency (ms) 0.42 0.41
Average Latency (ms) 0.72 0.59
Maximum Latency (ms) 6.33 9.08
95th Percentile Latency (ms) 0.95 0.8

MySQL UPDATE (Non-Indexed)

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance Intel (2 GB, 2 Cores)
Transactions per second 14,587.00 17,168.00
Queries per second 145,870.00 171,680.00
Minimum Latency (ms) 0.4 0.39
Average Latency (ms) 0.68 0.58
Maximum Latency (ms) 11.69 1.77
95th Percentile Latency (ms) 0.9 0.75

MySQL DELETE

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance Intel (2 GB, 2 Cores)
Transactions per second 129,013.00 139,126.00
Queries per second 1,290,130.00 1,391,260.00
Minimum Latency (ms) 0.03 0.03
Average Latency (ms) 0.08 0.07
Maximum Latency (ms) 2.61 2.43
95th Percentile Latency (ms) 0.09 0.1

Redis

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance Intel (2 GB, 2 Cores)
PING_INLINE per Second 78,247.26 66,622.25
PING_MBULK per Second 74,738.41 66,050.20
SET per Second 77,041.60 67,567.57
GET per Second 83,333.33 68,027.21
INCR per Second 80,971.66 67,934.78
LPUSH per Second 79,113.92 68,306.01
RPUSH per Second 77,160.49 69,444.45
LPOP per Second 81,499.59 70,028.02
RPOP per Second 82,440.23 67,613.25
SADD per Second 80,192.46 66,711.14
HSET per Second 83,612.04 69,060.77
SPOP per Second 85,034.02 68,352.70
ZADD per Second 83,263.95 68,917.99
ZPOPMIN per Second 82,987.55 67,613.25
LRANGE_100 (first 100 elements) per Second 55,555.56 52,576.24
LRANGE_300 (first 300 elements) per Second 28,851.70 29,841.84
LRANGE_500 (first 500 elements) per Second 19,391.12 20,157.23
LRANGE_600 (first 600 elements) per Second 17,211.71 17,624.25
MSET (10 keys) per Second 80,256.82 71,684.59

Redis Average Latency (ms)

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance Intel (2 GB, 2 Cores)
PING_INLINE0.340.40
PING_MBULK0.350.39
SET0.340.38
GET0.320.38
INCR0.320.38
LPUSH0.340.38
RPUSH0.340.37
LPOP0.320.37
RPOP0.320.38
SADD0.320.39
HSET0.310.38
SPOP0.300.38
ZADD0.310.37
ZPOPMIN0.310.38
LRANGE_100 (first 100 elements)0.540.50
LRANGE_300 (first 300 elements)1.110.90
LRANGE_500 (first 500 elements)1.621.32
LRANGE_600 (first 600 elements)1.841.58
MSET (10 keys)0.380.36

Conclusion

From the friendly robots:

In comparing the Vultr Cloud Compute (2 GB, 2 Cores) and the High Performance Intel (2 GB, 2 Cores) instances, it is evident that the High Performance Intel configuration excels in most benchmarks, particularly in Redis operations where it shows higher requests per second and better latency across various commands. The file I/O operations also display superior throughput and lower latency. While both instances perform comparably in basic CPU, memory, and MySQL benchmarks, the High Performance Intel instance, with its advanced CPU model and NVMe support, clearly offers better performance for I/O-heavy workloads, making it ideal for applications requiring high data throughput and low latency, whereas the Cloud Compute instance, with its more modest performance and lower monthly cost, may be more suitable for lighter workloads or cost-sensitive use cases.

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.