DigitalOcean Premium Intel (2 GB, 2 Cores) vs. Vultr Cloud Compute (8 GB, 4 Cores)

vs.

Fresh benchmarks coming at ya. Today I've spun up some brand new instance from DigitalOcean and Vultr to run some benchmarks on. Each instance was spun up with Ubuntu 24.04 LTS x64 and all resided in or around the New York / New Jersey area. Time to see who showed up today.

Overview

DigitalOcean – Premium Intel (2 GB, 2 Cores) Vultr – Cloud Compute (8 GB, 4 Cores)
Last Benchmarked Thu, 21 May 2026 13:00:52 GMT Sat, 23 May 2026 11:00:52 GMT
Linux Distro Ubuntu 24.04 LTS x64 Ubuntu 24.04 LTS x64
Kernel Version 6.8.0-71-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 New York, NY Newark, NJ
Monthly Price $24.00 $40.00
RAM (GB) 2 8
CPU Cores 2 4
Storage (TB) 90 160
Storage Type NVMe SSD
Transfer (TB) 3 4

CPU

DigitalOcean – Premium Intel (2 GB, 2 Cores) Vultr – Cloud Compute (8 GB, 4 Cores)
Vendor GenuineIntel GenuineIntel
Model Name DO-Premium-Intel Intel Xeon Processor (Skylake, IBRS)
Clock Speed (MHz) 1,995.31 2,593.90
CPU Cache Size (KB) 4,096.00 16,384.00
BogoMips 3,990.62 5,187.80
Events per Second 2,094.53 1,100.82
Minimum Latency (ms) 0.46 0.88
Average Latency (ms) 0.48 0.91
Maximum Latency (ms) 0.64 1.56
95th Percentile Latency (ms) 0.49 0.97

Memory

Memory Read

DigitalOcean – Premium Intel (2 GB, 2 Cores) Vultr – Cloud Compute (8 GB, 4 Cores)
Operations per second 4,227,679.19 3,685,781.23
Mebibytes per second 4,128.59 3,599.40
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 0.08 1.03
95th Percentile Latency (ms) 0 0

Memory Write

DigitalOcean – Premium Intel (2 GB, 2 Cores) Vultr – Cloud Compute (8 GB, 4 Cores)
Operations per second 4,316,563.36 3,590,629.63
Mebibytes per second 4,215.39 3,506.47
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 0.06 1.16
95th Percentile Latency (ms) 0 0

File I/O

DigitalOcean – Premium Intel (2 GB, 2 Cores) Vultr – Cloud Compute (8 GB, 4 Cores)
Reads per Second 2,558.02 4,999.39
Writes per Second 1,705.35 3,332.93
Fsyncs per Second 5,460.70 10,670.47
Read Mebibytes per Second 39.97 78.12
Written Mebibytes per Second 26.65 52.08
Minimum Latency (ms) 0 0
Average Latency (ms) 0.1 0.05
Maximum Latency (ms) 9.91 37.52
95th Percentile Latency (ms) 0.37 0.18

Mutex

DigitalOcean – Premium Intel (2 GB, 2 Cores) Vultr – Cloud Compute (8 GB, 4 Cores)
Minimum Latency (ms) 1,115.02 369.37
Average Latency (ms) 1,136.65 416.22
Maximum Latency (ms) 1,162.06 441.77
95th Percentile Latency (ms) 1,170.65 442.73

MySQL

MySQL Read-only

DigitalOcean – Premium Intel (2 GB, 2 Cores) Vultr – Cloud Compute (8 GB, 4 Cores)
Transactions per second 6,074.00 5,144.00
Queries per second 60,740.00 51,440.00
Minimum Latency (ms) 1.12 1.72
Average Latency (ms) 1.64 1.94
Maximum Latency (ms) 3.93 7.67
95th Percentile Latency (ms) 2.22 2.35

MySQL Write-only

DigitalOcean – Premium Intel (2 GB, 2 Cores) Vultr – Cloud Compute (8 GB, 4 Cores)
Transactions per second 3,950.00 5,108.00
Queries per second 39,500.00 51,080.00
Minimum Latency (ms) 1.13 1.15
Average Latency (ms) 2.53 1.96
Maximum Latency (ms) 46.55 12.52
95th Percentile Latency (ms) 3.82 2.71

MySQL Read/Write

DigitalOcean – Premium Intel (2 GB, 2 Cores) Vultr – Cloud Compute (8 GB, 4 Cores)
Transactions per second 2,284.00 2,247.00
Queries per second 22,840.00 22,470.00
Minimum Latency (ms) 2.45 3.08
Average Latency (ms) 4.37 4.45
Maximum Latency (ms) 21.51 29.7
95th Percentile Latency (ms) 5.77 5.28

MySQL INSERT

DigitalOcean – Premium Intel (2 GB, 2 Cores) Vultr – Cloud Compute (8 GB, 4 Cores)
Transactions per second 7,678.00 7,630.00
Queries per second 76,780.00 76,300.00
Minimum Latency (ms) 0.64 0.71
Average Latency (ms) 1.3 1.31
Maximum Latency (ms) 7.37 29.81
95th Percentile Latency (ms) 1.96 1.55

MySQL Bulk INSERT

DigitalOcean – Premium Intel (2 GB, 2 Cores) Vultr – Cloud Compute (8 GB, 4 Cores)
Transactions per second 1,375,842.00 898,571.00
Queries per second 13,758,420.00 8,985,710.00
Minimum Latency (ms) 0 0
Average Latency (ms) 0.01 0.01
Maximum Latency (ms) 399.3 505.86
95th Percentile Latency (ms) 0 0

MySQL SELECT

DigitalOcean – Premium Intel (2 GB, 2 Cores) Vultr – Cloud Compute (8 GB, 4 Cores)
Transactions per second 163,156.00 149,465.00
Queries per second 1,631,560.00 1,494,650.00
Minimum Latency (ms) 0.04 0.05
Average Latency (ms) 0.06 0.07
Maximum Latency (ms) 3.78 1.22
95th Percentile Latency (ms) 0.09 0.09

MySQL SELECT (Random Points)

DigitalOcean – Premium Intel (2 GB, 2 Cores) Vultr – Cloud Compute (8 GB, 4 Cores)
Transactions per second 5,461.00 4,249.00
Queries per second 54,610.00 42,490.00
Minimum Latency (ms) 0.69 0.83
Average Latency (ms) 1.83 2.35
Maximum Latency (ms) 10.38 6.6
95th Percentile Latency (ms) 2.76 3.02

MySQL SELECT (Random Ranges)

DigitalOcean – Premium Intel (2 GB, 2 Cores) Vultr – Cloud Compute (8 GB, 4 Cores)
Transactions per second 6,481.00 2,637.00
Queries per second 64,810.00 26,370.00
Minimum Latency (ms) 0.27 0.94
Average Latency (ms) 1.54 3.79
Maximum Latency (ms) 4.07 6.3
95th Percentile Latency (ms) 2.52 5.09

MySQL UPDATE (Indexed)

DigitalOcean – Premium Intel (2 GB, 2 Cores) Vultr – Cloud Compute (8 GB, 4 Cores)
Transactions per second 6,847.00 7,166.00
Queries per second 68,470.00 71,660.00
Minimum Latency (ms) 0.71 0.7
Average Latency (ms) 1.46 1.39
Maximum Latency (ms) 7.84 28.84
95th Percentile Latency (ms) 2.14 1.79

MySQL UPDATE (Non-Indexed)

DigitalOcean – Premium Intel (2 GB, 2 Cores) Vultr – Cloud Compute (8 GB, 4 Cores)
Transactions per second 5,708.00 7,661.00
Queries per second 57,080.00 76,610.00
Minimum Latency (ms) 0.69 0.7
Average Latency (ms) 1.75 1.3
Maximum Latency (ms) 60.56 33.97
95th Percentile Latency (ms) 2.57 1.58

MySQL DELETE

DigitalOcean – Premium Intel (2 GB, 2 Cores) Vultr – Cloud Compute (8 GB, 4 Cores)
Transactions per second 87,979.00 69,690.00
Queries per second 879,790.00 696,900.00
Minimum Latency (ms) 0.04 0.05
Average Latency (ms) 0.11 0.14
Maximum Latency (ms) 30.66 27.73
95th Percentile Latency (ms) 0.16 0.87

Redis

DigitalOcean – Premium Intel (2 GB, 2 Cores) Vultr – Cloud Compute (8 GB, 4 Cores)
PING_INLINE per Second 75,414.78 54,436.58
PING_MBULK per Second 74,906.37 48,828.12
SET per Second 73,367.57 51,572.98
GET per Second 72,516.32 48,239.27
INCR per Second 66,577.90 52,328.62
LPUSH per Second 70,871.72 45,454.54
RPUSH per Second 67,430.88 49,751.24
LPOP per Second 72,727.27 53,390.28
RPOP per Second 69,832.40 53,648.07
SADD per Second 75,700.23 48,285.85
HSET per Second 73,637.70 51,493.30
SPOP per Second 57,703.40 52,910.05
ZADD per Second 59,772.86 53,504.55
ZPOPMIN per Second 82,987.55 53,590.57
LRANGE_100 (first 100 elements) per Second 45,682.96 28,645.09
LRANGE_300 (first 300 elements) per Second 22,675.74 13,131.98
LRANGE_500 (first 500 elements) per Second 14,122.30 8,529.51
LRANGE_600 (first 600 elements) per Second 10,827.20 7,479.99
MSET (10 keys) per Second 65,789.48 49,212.60

Redis Average Latency (ms)

DigitalOcean – Premium Intel (2 GB, 2 Cores) Vultr – Cloud Compute (8 GB, 4 Cores)
PING_INLINE0.380.47
PING_MBULK0.360.53
SET0.400.50
GET0.410.54
INCR0.440.49
LPUSH0.480.58
RPUSH0.450.52
LPOP0.450.49
RPOP0.400.48
SADD0.400.54
HSET0.390.53
SPOP0.450.49
ZADD0.430.48
ZPOPMIN0.350.48
LRANGE_100 (first 100 elements)0.670.91
LRANGE_300 (first 300 elements)1.401.94
LRANGE_500 (first 500 elements)2.303.00
LRANGE_600 (first 600 elements)2.723.43
MSET (10 keys)0.650.77

Conclusion

From the friendly robots:

After analyzing the benchmarks for both the DigitalOcean Premium Intel and Vultr Cloud Compute instances, it's clear that the DigitalOcean instance excels in CPU-bound tasks, delivering higher Redis operation rates and lower latencies across various operations like LPUSH and LRANGE. The Vultr instance, on the other hand, is more suited to I/O intensive tasks thanks to its higher CPU clock speed, more substantial memory, and faster file I/O operations. If you are running applications that require more CPU processing power and low latency for Redis operations, the DigitalOcean instance is the better choice. However, if your workload involves significant data reading and writing, such as large-scale databases or high-throughput file services, the Vultr instance would be more appropriate.

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 links for DigitalOcean and Vultr.

You can also support me directly by buying me a coffee.