DigitalOcean Regular (4 GB, 2 Cores) vs. Vultr High Performance AMD (2 GB, 2 Cores)

vs.

Fresh benchmarks coming at ya. Today I've spun up brand new instance from DigitalOcean and Vultr and did some benchmarking. Each instance was running 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

DigitalOcean – Regular (4 GB, 2 Cores) Vultr – High Performance AMD (2 GB, 2 Cores)
Last Benchmarked Sat, 30 May 2026 15:00:52 GMT Sun, 31 May 2026 07: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 $18.00
RAM (GB) 4 2
CPU Cores 2 2
Storage (TB) 80 60
Storage Type SSD NVMe
Transfer (TB) 4 4

CPU

DigitalOcean – Regular (4 GB, 2 Cores) Vultr – High Performance AMD (2 GB, 2 Cores)
Vendor GenuineIntel AuthenticAMD
Model Name DO-Regular AMD EPYC-Genoa Processor
Clock Speed (MHz) 2,494.15 2,899.99
CPU Cache Size (KB) 4,096.00 1,024.00
BogoMips 4,988.29 5,799.98
Events per Second 871.36 4,648.14
Minimum Latency (ms) 0.91 0.2
Average Latency (ms) 1.15 0.21
Maximum Latency (ms) 5.11 1.26
95th Percentile Latency (ms) 1.34 0.23

Memory

Memory Read

DigitalOcean – Regular (4 GB, 2 Cores) Vultr – High Performance AMD (2 GB, 2 Cores)
Operations per second 4,167,908.44 7,548,502.85
Mebibytes per second 4,070.22 7,371.58
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 0.26 0.08
95th Percentile Latency (ms) 0 0

Memory Write

DigitalOcean – Regular (4 GB, 2 Cores) Vultr – High Performance AMD (2 GB, 2 Cores)
Operations per second 4,455,346.90 7,544,807.09
Mebibytes per second 4,350.92 7,367.98
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 0.26 0.12
95th Percentile Latency (ms) 0 0

File I/O

DigitalOcean – Regular (4 GB, 2 Cores) Vultr – High Performance AMD (2 GB, 2 Cores)
Reads per Second 2,278.19 5,114.79
Writes per Second 1,518.80 3,409.86
Fsyncs per Second 4,871.44 10,914.44
Read Mebibytes per Second 35.60 79.92
Written Mebibytes per Second 23.73 53.28
Minimum Latency (ms) 0 0
Average Latency (ms) 0.11 0.05
Maximum Latency (ms) 12.59 3.7
95th Percentile Latency (ms) 0.37 0.12

Mutex

DigitalOcean – Regular (4 GB, 2 Cores) Vultr – High Performance AMD (2 GB, 2 Cores)
Minimum Latency (ms) 1,307.95 574.03
Average Latency (ms) 1,349.23 637.47
Maximum Latency (ms) 1,391.63 663.74
95th Percentile Latency (ms) 1,401.61 657.93

MySQL

MySQL Read-only

DigitalOcean – Regular (4 GB, 2 Cores) Vultr – High Performance AMD (2 GB, 2 Cores)
Transactions per second 4,297.00 9,622.00
Queries per second 42,970.00 96,220.00
Minimum Latency (ms) 1.39 0.73
Average Latency (ms) 2.32 1.04
Maximum Latency (ms) 5.78 2.22
95th Percentile Latency (ms) 2.97 1.12

MySQL Write-only

DigitalOcean – Regular (4 GB, 2 Cores) Vultr – High Performance AMD (2 GB, 2 Cores)
Transactions per second 3,514.00 9,585.00
Queries per second 35,140.00 95,850.00
Minimum Latency (ms) 1.29 0.8
Average Latency (ms) 2.84 1.04
Maximum Latency (ms) 13.78 2.18
95th Percentile Latency (ms) 4.1 1.32

MySQL Read/Write

DigitalOcean – Regular (4 GB, 2 Cores) Vultr – High Performance AMD (2 GB, 2 Cores)
Transactions per second 1,947.00 4,686.00
Queries per second 19,470.00 46,860.00
Minimum Latency (ms) 2.91 1.57
Average Latency (ms) 5.13 2.13
Maximum Latency (ms) 13.08 4.26
95th Percentile Latency (ms) 6.67 2.52

MySQL INSERT

DigitalOcean – Regular (4 GB, 2 Cores) Vultr – High Performance AMD (2 GB, 2 Cores)
Transactions per second 6,796.00 15,965.00
Queries per second 67,960.00 159,650.00
Minimum Latency (ms) 0.65 0.45
Average Latency (ms) 1.47 0.62
Maximum Latency (ms) 10.09 2.23
95th Percentile Latency (ms) 2.18 0.74

MySQL Bulk INSERT

DigitalOcean – Regular (4 GB, 2 Cores) Vultr – High Performance AMD (2 GB, 2 Cores)
Transactions per second 1,055,467.00 3,065,092.00
Queries per second 10,554,670.00 30,650,920.00
Minimum Latency (ms) 0 0
Average Latency (ms) 0.01 0
Maximum Latency (ms) 573.76 208.51
95th Percentile Latency (ms) 0 0

MySQL SELECT

DigitalOcean – Regular (4 GB, 2 Cores) Vultr – High Performance AMD (2 GB, 2 Cores)
Transactions per second 123,372.00 217,035.00
Queries per second 1,233,720.00 2,170,350.00
Minimum Latency (ms) 0.04 0.02
Average Latency (ms) 0.08 0.05
Maximum Latency (ms) 1.53 0.61
95th Percentile Latency (ms) 0.12 0.06

MySQL SELECT (Random Points)

DigitalOcean – Regular (4 GB, 2 Cores) Vultr – High Performance AMD (2 GB, 2 Cores)
Transactions per second 4,146.00 14,818.00
Queries per second 41,460.00 148,180.00
Minimum Latency (ms) 0.81 0.24
Average Latency (ms) 2.41 0.67
Maximum Latency (ms) 21.02 1.94
95th Percentile Latency (ms) 3.36 0.86

MySQL SELECT (Random Ranges)

DigitalOcean – Regular (4 GB, 2 Cores) Vultr – High Performance AMD (2 GB, 2 Cores)
Transactions per second 4,644.00 14,341.00
Queries per second 46,440.00 143,410.00
Minimum Latency (ms) 0.75 0.27
Average Latency (ms) 2.15 0.7
Maximum Latency (ms) 8.73 1.67
95th Percentile Latency (ms) 3.19 0.89

MySQL UPDATE (Indexed)

DigitalOcean – Regular (4 GB, 2 Cores) Vultr – High Performance AMD (2 GB, 2 Cores)
Transactions per second 5,918.00 14,864.00
Queries per second 59,180.00 148,640.00
Minimum Latency (ms) 0.61 0.47
Average Latency (ms) 1.69 0.67
Maximum Latency (ms) 17.54 2.36
95th Percentile Latency (ms) 2.71 0.87

MySQL UPDATE (Non-Indexed)

DigitalOcean – Regular (4 GB, 2 Cores) Vultr – High Performance AMD (2 GB, 2 Cores)
Transactions per second 6,844.00 15,284.00
Queries per second 68,440.00 152,840.00
Minimum Latency (ms) 0.7 0.46
Average Latency (ms) 1.46 0.65
Maximum Latency (ms) 11.43 1.65
95th Percentile Latency (ms) 2.11 0.83

MySQL DELETE

DigitalOcean – Regular (4 GB, 2 Cores) Vultr – High Performance AMD (2 GB, 2 Cores)
Transactions per second 55,206.00 151,536.00
Queries per second 552,060.00 1,515,360.00
Minimum Latency (ms) 0.04 0.02
Average Latency (ms) 0.18 0.07
Maximum Latency (ms) 6.66 4.83
95th Percentile Latency (ms) 1.18 0.08

Redis

DigitalOcean – Regular (4 GB, 2 Cores) Vultr – High Performance AMD (2 GB, 2 Cores)
PING_INLINE per Second 50,607.29 55,991.04
PING_MBULK per Second 44,169.61 57,903.88
SET per Second 44,444.45 57,703.40
GET per Second 47,619.05 57,703.40
INCR per Second 48,638.13 57,372.34
LPUSH per Second 49,603.17 57,836.90
RPUSH per Second 47,664.44 58,173.36
LPOP per Second 50,942.43 58,343.06
RPOP per Second 48,216.01 58,343.06
SADD per Second 48,379.30 58,241.12
HSET per Second 48,053.82 58,858.15
SPOP per Second 50,301.81 58,892.82
ZADD per Second 54,495.91 57,504.31
ZPOPMIN per Second 50,864.70 57,870.37
LRANGE_100 (first 100 elements) per Second 33,523.30 49,236.83
LRANGE_300 (first 300 elements) per Second 16,619.58 34,818.94
LRANGE_500 (first 500 elements) per Second 10,716.96 26,766.60
LRANGE_600 (first 600 elements) per Second 9,849.31 24,207.21
MSET (10 keys) per Second 46,189.38 58,548.01

Redis Average Latency (ms)

DigitalOcean – Regular (4 GB, 2 Cores) Vultr – High Performance AMD (2 GB, 2 Cores)
PING_INLINE0.550.48
PING_MBULK0.590.44
SET0.600.45
GET0.560.45
INCR0.550.45
LPUSH0.540.44
RPUSH0.560.44
LPOP0.530.44
RPOP0.560.44
SADD0.550.44
HSET0.570.44
SPOP0.530.44
ZADD0.500.45
ZPOPMIN0.520.44
LRANGE_100 (first 100 elements)1.040.53
LRANGE_300 (first 300 elements)1.780.74
LRANGE_500 (first 500 elements)2.920.95
LRANGE_600 (first 600 elements)3.431.05
MSET (10 keys)0.670.44

Conclusion

From the friendly robots:

After analyzing the benchmark results for both instances, the DigitalOcean Regular (4 GB, 2 Cores) and Vultr High Performance AMD (2 GB, 2 Cores) offer distinct advantages based on workload requirements. The DigitalOcean instance excels in memory operations, with high read and write throughput, and performs well in CPU-intensive tasks such as bulk MySQL inserts and OLTP operations, though it lags slightly in some Redis commands. The Vultr instance, with its faster CPU and higher frequency, shows remarkable performance in Redis operations, including higher request rates per second and lower latencies, though it performs moderately in CPU and memory benchmarks. Overall, the DigitalOcean instance is ideal for applications requiring substantial memory and CPU performance, while the Vultr instance is best suited for workloads that prioritize high Redis performance, such as real-time data processing and caching.

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.