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

vs.

Fresh benchmarks coming at ya. Today I've spun up brand new instance from DigitalOcean and Vultr and ran some benchmarks. All instances were 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 AMD (4 GB, 2 Cores) Vultr – Cloud Compute (4 GB, 2 Cores)
Last Benchmarked Fri, 12 Jun 2026 02:00:51 GMT Thu, 11 Jun 2026 09: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-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 New York, NY Newark, NJ
Monthly Price $28.00 $20.00
RAM (GB) 4 4
CPU Cores 2 2
Storage (TB) 80 80
Storage Type NVMe SSD
Transfer (TB) 2 3

CPU

DigitalOcean – Premium AMD (4 GB, 2 Cores) Vultr – Cloud Compute (4 GB, 2 Cores)
Vendor AuthenticAMD GenuineIntel
Model Name DO-Premium-AMD Intel Xeon Processor (Skylake, IBRS)
Clock Speed (MHz) 1,996.25 2,593.91
CPU Cache Size (KB) 512.00 16,384.00
BogoMips 3,992.49 5,187.81
Events per Second 1,513.81 1,022.39
Minimum Latency (ms) 0.6 0.88
Average Latency (ms) 0.66 0.98
Maximum Latency (ms) 1.82 1.77
95th Percentile Latency (ms) 0.7 1.21

Memory

Memory Read

DigitalOcean – Premium AMD (4 GB, 2 Cores) Vultr – Cloud Compute (4 GB, 2 Cores)
Operations per second 4,581,225.47 3,523,809.57
Mebibytes per second 4,473.85 3,441.22
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 0.23 0.22
95th Percentile Latency (ms) 0 0

Memory Write

DigitalOcean – Premium AMD (4 GB, 2 Cores) Vultr – Cloud Compute (4 GB, 2 Cores)
Operations per second 4,782,039.81 3,568,203.77
Mebibytes per second 4,669.96 3,484.57
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 0.18 1.02
95th Percentile Latency (ms) 0 0

File I/O

DigitalOcean – Premium AMD (4 GB, 2 Cores) Vultr – Cloud Compute (4 GB, 2 Cores)
Reads per Second 1,641.75 2,972.63
Writes per Second 1,094.50 1,981.75
Fsyncs per Second 3,509.79 6,347.81
Read Mebibytes per Second 25.65 46.45
Written Mebibytes per Second 17.10 30.96
Minimum Latency (ms) 0 0
Average Latency (ms) 0.16 0.09
Maximum Latency (ms) 16.81 17.12
95th Percentile Latency (ms) 0.61 0.33

Mutex

DigitalOcean – Premium AMD (4 GB, 2 Cores) Vultr – Cloud Compute (4 GB, 2 Cores)
Minimum Latency (ms) 895.16 899.28
Average Latency (ms) 967.85 935.93
Maximum Latency (ms) 992.95 969.92
95th Percentile Latency (ms) 995.51 977.74

MySQL

MySQL Read-only

DigitalOcean – Premium AMD (4 GB, 2 Cores) Vultr – Cloud Compute (4 GB, 2 Cores)
Transactions per second 5,791.00 3,779.00
Queries per second 57,910.00 37,790.00
Minimum Latency (ms) 1.36 1.84
Average Latency (ms) 1.72 2.64
Maximum Latency (ms) 4.34 24.55
95th Percentile Latency (ms) 2.26 3.82

MySQL Write-only

DigitalOcean – Premium AMD (4 GB, 2 Cores) Vultr – Cloud Compute (4 GB, 2 Cores)
Transactions per second 3,248.00 4,044.00
Queries per second 32,480.00 40,440.00
Minimum Latency (ms) 1.46 1.4
Average Latency (ms) 3.08 2.47
Maximum Latency (ms) 27.41 13.46
95th Percentile Latency (ms) 5 3.3

MySQL Read/Write

DigitalOcean – Premium AMD (4 GB, 2 Cores) Vultr – Cloud Compute (4 GB, 2 Cores)
Transactions per second 2,085.00 1,798.00
Queries per second 20,850.00 17,980.00
Minimum Latency (ms) 3.01 3.86
Average Latency (ms) 4.79 5.56
Maximum Latency (ms) 16.55 27.33
95th Percentile Latency (ms) 6.43 6.91

MySQL INSERT

DigitalOcean – Premium AMD (4 GB, 2 Cores) Vultr – Cloud Compute (4 GB, 2 Cores)
Transactions per second 4,752.00 6,405.00
Queries per second 47,520.00 64,050.00
Minimum Latency (ms) 0.97 0.99
Average Latency (ms) 2.1 1.56
Maximum Latency (ms) 14.79 15.15
95th Percentile Latency (ms) 3.49 2.03

MySQL Bulk INSERT

DigitalOcean – Premium AMD (4 GB, 2 Cores) Vultr – Cloud Compute (4 GB, 2 Cores)
Transactions per second 1,404,967.00 865,805.00
Queries per second 14,049,670.00 8,658,050.00
Minimum Latency (ms) 0 0
Average Latency (ms) 0.01 0.01
Maximum Latency (ms) 436.99 538.25
95th Percentile Latency (ms) 0 0

MySQL SELECT

DigitalOcean – Premium AMD (4 GB, 2 Cores) Vultr – Cloud Compute (4 GB, 2 Cores)
Transactions per second 117,344.00 126,618.00
Queries per second 1,173,440.00 1,266,180.00
Minimum Latency (ms) 0.05 0.05
Average Latency (ms) 0.08 0.08
Maximum Latency (ms) 0.93 2.46
95th Percentile Latency (ms) 0.12 0.11

MySQL SELECT (Random Points)

DigitalOcean – Premium AMD (4 GB, 2 Cores) Vultr – Cloud Compute (4 GB, 2 Cores)
Transactions per second 7,008.00 3,674.00
Queries per second 70,080.00 36,740.00
Minimum Latency (ms) 0.49 1.07
Average Latency (ms) 1.43 2.72
Maximum Latency (ms) 9.98 6.45
95th Percentile Latency (ms) 2.03 3.55

MySQL SELECT (Random Ranges)

DigitalOcean – Premium AMD (4 GB, 2 Cores) Vultr – Cloud Compute (4 GB, 2 Cores)
Transactions per second 6,940.00 2,728.00
Queries per second 69,400.00 27,280.00
Minimum Latency (ms) 0.41 1.3
Average Latency (ms) 1.44 3.66
Maximum Latency (ms) 3.15 11.85
95th Percentile Latency (ms) 1.89 5

MySQL UPDATE (Indexed)

DigitalOcean – Premium AMD (4 GB, 2 Cores) Vultr – Cloud Compute (4 GB, 2 Cores)
Transactions per second 5,067.00 5,438.00
Queries per second 50,670.00 54,380.00
Minimum Latency (ms) 1.01 0.99
Average Latency (ms) 1.97 1.84
Maximum Latency (ms) 12.82 13.86
95th Percentile Latency (ms) 3.02 2.71

MySQL UPDATE (Non-Indexed)

DigitalOcean – Premium AMD (4 GB, 2 Cores) Vultr – Cloud Compute (4 GB, 2 Cores)
Transactions per second 5,010.00 6,370.00
Queries per second 50,100.00 63,700.00
Minimum Latency (ms) 0.99 1.01
Average Latency (ms) 1.99 1.57
Maximum Latency (ms) 23.15 8.99
95th Percentile Latency (ms) 3.02 2.07

MySQL DELETE

DigitalOcean – Premium AMD (4 GB, 2 Cores) Vultr – Cloud Compute (4 GB, 2 Cores)
Transactions per second 38,772.00 51,180.00
Queries per second 387,720.00 511,800.00
Minimum Latency (ms) 0.05 0.05
Average Latency (ms) 0.26 0.19
Maximum Latency (ms) 18.57 6.11
95th Percentile Latency (ms) 1.73 1.39

Redis

DigitalOcean – Premium AMD (4 GB, 2 Cores) Vultr – Cloud Compute (4 GB, 2 Cores)
PING_INLINE per Second 57,870.37 49,677.10
PING_MBULK per Second 51,840.33 45,372.05
SET per Second 52,383.45 45,392.64
GET per Second 52,714.81 53,163.21
INCR per Second 51,840.33 48,732.94
LPUSH per Second 50,709.94 50,327.12
RPUSH per Second 50,864.70 48,285.85
LPOP per Second 51,177.07 48,355.90
RPOP per Second 52,219.32 51,413.88
SADD per Second 51,493.30 48,332.53
HSET per Second 52,192.07 49,285.36
SPOP per Second 52,301.26 48,332.53
ZADD per Second 49,358.34 51,229.51
ZPOPMIN per Second 52,687.04 45,085.66
LRANGE_100 (first 100 elements) per Second 39,154.27 27,122.32
LRANGE_300 (first 300 elements) per Second 23,691.07 12,442.45
LRANGE_500 (first 500 elements) per Second 16,614.05 7,930.21
LRANGE_600 (first 600 elements) per Second 15,320.97 6,902.74
MSET (10 keys) per Second 52,603.89 45,146.73

Redis Average Latency (ms)

DigitalOcean – Premium AMD (4 GB, 2 Cores) Vultr – Cloud Compute (4 GB, 2 Cores)
PING_INLINE0.450.53
PING_MBULK0.500.57
SET0.500.57
GET0.490.49
INCR0.500.53
LPUSH0.520.51
RPUSH0.510.54
LPOP0.510.54
RPOP0.500.52
SADD0.500.55
HSET0.500.54
SPOP0.500.54
ZADD0.540.52
ZPOPMIN0.500.57
LRANGE_100 (first 100 elements)0.711.02
LRANGE_300 (first 300 elements)1.152.29
LRANGE_500 (first 500 elements)1.783.27
LRANGE_600 (first 600 elements)1.813.91
MSET (10 keys)0.510.78

Conclusion

From the friendly robots:

Both VPS instances showcase solid performance metrics across various benchmarks, with subtle differences indicating varying strengths. The DigitalOcean instance, powered by AMD Ryzen processors, demonstrates slightly higher Redis and MySQL performance with more efficient CPU utilization, particularly in read-heavy operations and concurrency scenarios, but the Vultr instance with its Intel Xeon Processor shows slightly better write operations and overall file IO performance. The Vultr instance also edges out in price, making it a more economical choice for budget-conscious users, while DigitalOcean offers a slight edge in Redis operations and memory throughput. Therefore, the DigitalOcean instance is ideal for high-concurrency, I/O-intensive workloads, while the Vultr instance would be better suited for scenarios requiring more extensive storage operations and where cost savings are a priority.

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.