My friend, I'm so glad you're here! Today I've spun up some brand new instance from DigitalOcean and Vultr and did some benchmarking. Each instance was running 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 (2 GB, 2 Cores)
Vultr – Cloud Compute (2 GB, 2 Cores)
Last Benchmarked
Tue, 12 May 2026 11:00:52 GMT
Mon, 11 May 2026 04: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-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
New York, NY
Newark, NJ
Monthly Price
$21.00
$15.00
RAM (GB)
2
2
CPU Cores
2
2
Storage (TB)
60
65
Storage Type
NVMe
SSD
Transfer (TB)
3
3
CPU
DigitalOcean – Premium AMD (2 GB, 2 Cores)
Vultr – Cloud Compute (2 GB, 2 Cores)
Vendor
AuthenticAMD
GenuineIntel
Model Name
DO-Premium-AMD
Intel Core Processor (Skylake, IBRS, no TSX)
Clock Speed (MHz)
1,996.25
3,792.00
CPU Cache Size (KB)
512.00
16,384.00
BogoMips
3,992.49
7,583.99
Events per Second
1,560.26
1,481.60
Minimum Latency (ms)
0.59
0.63
Average Latency (ms)
0.64
0.67
Maximum Latency (ms)
2.06
1.95
95th Percentile Latency (ms)
0.69
0.77
Memory
Memory Read
DigitalOcean – Premium AMD (2 GB, 2 Cores)
Vultr – Cloud Compute (2 GB, 2 Cores)
Operations per second
4,876,345.27
6,401,389.08
Mebibytes per second
4,762.06
6,251.36
Minimum Latency (ms)
0
0
Average Latency (ms)
0
0
Maximum Latency (ms)
0.21
0.23
95th Percentile Latency (ms)
0
0
Memory Write
DigitalOcean – Premium AMD (2 GB, 2 Cores)
Vultr – Cloud Compute (2 GB, 2 Cores)
Operations per second
4,927,449.86
6,411,085.35
Mebibytes per second
4,811.96
6,260.83
Minimum Latency (ms)
0
0
Average Latency (ms)
0
0
Maximum Latency (ms)
0.19
0.18
95th Percentile Latency (ms)
0
0
File I/O
DigitalOcean – Premium AMD (2 GB, 2 Cores)
Vultr – Cloud Compute (2 GB, 2 Cores)
Reads per Second
1,725.18
4,345.71
Writes per Second
1,150.12
2,897.07
Fsyncs per Second
3,684.17
9,273.19
Read Mebibytes per Second
26.96
67.90
Written Mebibytes per Second
17.97
45.27
Minimum Latency (ms)
0
0
Average Latency (ms)
0.15
0.06
Maximum Latency (ms)
6.97
2.92
95th Percentile Latency (ms)
0.55
0.17
Mutex
DigitalOcean – Premium AMD (2 GB, 2 Cores)
Vultr – Cloud Compute (2 GB, 2 Cores)
Minimum Latency (ms)
861.23
214.63
Average Latency (ms)
896.40
569.72
Maximum Latency (ms)
924.38
636.55
95th Percentile Latency (ms)
926.33
634.66
MySQL
MySQL Read-only
DigitalOcean – Premium AMD (2 GB, 2 Cores)
Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second
5,447.00
8,015.00
Queries per second
54,470.00
80,150.00
Minimum Latency (ms)
1.4
0.92
Average Latency (ms)
1.83
1.25
Maximum Latency (ms)
3.52
5.5
95th Percentile Latency (ms)
2.26
1.86
MySQL Write-only
DigitalOcean – Premium AMD (2 GB, 2 Cores)
Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second
3,769.00
8,497.00
Queries per second
37,690.00
84,970.00
Minimum Latency (ms)
1.41
0.76
Average Latency (ms)
2.65
1.17
Maximum Latency (ms)
21.31
3.04
95th Percentile Latency (ms)
3.82
1.55
MySQL Read/Write
DigitalOcean – Premium AMD (2 GB, 2 Cores)
Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second
2,009.00
3,726.00
Queries per second
20,090.00
37,260.00
Minimum Latency (ms)
3.1
1.78
Average Latency (ms)
4.98
2.68
Maximum Latency (ms)
15.84
5.82
95th Percentile Latency (ms)
6.79
3.43
MySQL INSERT
DigitalOcean – Premium AMD (2 GB, 2 Cores)
Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second
5,188.00
15,028.00
Queries per second
51,880.00
150,280.00
Minimum Latency (ms)
1.06
0.41
Average Latency (ms)
1.92
0.66
Maximum Latency (ms)
12.78
2.42
95th Percentile Latency (ms)
3.02
0.86
MySQL Bulk INSERT
DigitalOcean – Premium AMD (2 GB, 2 Cores)
Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second
1,375,842.00
1,696,217.00
Queries per second
13,758,420.00
16,962,170.00
Minimum Latency (ms)
0
0
Average Latency (ms)
0.01
0.01
Maximum Latency (ms)
448.37
283.37
95th Percentile Latency (ms)
0
0
MySQL SELECT
DigitalOcean – Premium AMD (2 GB, 2 Cores)
Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second
119,183.00
201,989.00
Queries per second
1,191,830.00
2,019,890.00
Minimum Latency (ms)
0.05
0.03
Average Latency (ms)
0.08
0.05
Maximum Latency (ms)
1.81
0.51
95th Percentile Latency (ms)
0.11
0.07
MySQL SELECT (Random Points)
DigitalOcean – Premium AMD (2 GB, 2 Cores)
Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second
7,445.00
8,025.00
Queries per second
74,450.00
80,250.00
Minimum Latency (ms)
0.43
0.35
Average Latency (ms)
1.34
1.24
Maximum Latency (ms)
8.47
3.55
95th Percentile Latency (ms)
1.89
2.07
MySQL SELECT (Random Ranges)
DigitalOcean – Premium AMD (2 GB, 2 Cores)
Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second
6,562.00
8,336.00
Queries per second
65,620.00
83,360.00
Minimum Latency (ms)
0.49
0.4
Average Latency (ms)
1.52
1.2
Maximum Latency (ms)
3.46
4.25
95th Percentile Latency (ms)
2.03
2.22
MySQL UPDATE (Indexed)
DigitalOcean – Premium AMD (2 GB, 2 Cores)
Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second
4,890.00
13,858.00
Queries per second
48,900.00
138,580.00
Minimum Latency (ms)
1.01
0.42
Average Latency (ms)
2.04
0.72
Maximum Latency (ms)
17.91
6.33
95th Percentile Latency (ms)
3.13
0.95
MySQL UPDATE (Non-Indexed)
DigitalOcean – Premium AMD (2 GB, 2 Cores)
Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second
5,023.00
14,587.00
Queries per second
50,230.00
145,870.00
Minimum Latency (ms)
1.12
0.4
Average Latency (ms)
1.99
0.68
Maximum Latency (ms)
28.99
11.69
95th Percentile Latency (ms)
2.97
0.9
MySQL DELETE
DigitalOcean – Premium AMD (2 GB, 2 Cores)
Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second
41,819.00
129,013.00
Queries per second
418,190.00
1,290,130.00
Minimum Latency (ms)
0.05
0.03
Average Latency (ms)
0.24
0.08
Maximum Latency (ms)
14.59
2.61
95th Percentile Latency (ms)
1.61
0.09
Redis
DigitalOcean – Premium AMD (2 GB, 2 Cores)
Vultr – Cloud Compute (2 GB, 2 Cores)
PING_INLINE per Second
50,581.69
78,247.26
PING_MBULK per Second
50,100.20
74,738.41
SET per Second
49,751.24
77,041.60
GET per Second
49,925.11
83,333.33
INCR per Second
51,733.06
80,971.66
LPUSH per Second
52,521.01
79,113.92
RPUSH per Second
50,864.70
77,160.49
LPOP per Second
46,663.56
81,499.59
RPOP per Second
47,664.44
82,440.23
SADD per Second
50,813.01
80,192.46
HSET per Second
51,308.36
83,612.04
SPOP per Second
49,677.10
85,034.02
ZADD per Second
49,358.34
83,263.95
ZPOPMIN per Second
48,851.98
82,987.55
LRANGE_100 (first 100 elements) per Second
40,355.12
55,555.56
LRANGE_300 (first 300 elements) per Second
23,148.15
28,851.70
LRANGE_500 (first 500 elements) per Second
16,949.15
19,391.12
LRANGE_600 (first 600 elements) per Second
15,008.25
17,211.71
MSET (10 keys) per Second
52,576.24
80,256.82
Redis Average Latency (ms)
DigitalOcean – Premium AMD (2 GB, 2 Cores)
Vultr – Cloud Compute (2 GB, 2 Cores)
PING_INLINE
0.52
0.34
PING_MBULK
0.52
0.35
SET
0.53
0.34
GET
0.52
0.32
INCR
0.50
0.32
LPUSH
0.50
0.34
RPUSH
0.51
0.34
LPOP
0.56
0.32
RPOP
0.55
0.32
SADD
0.51
0.32
HSET
0.51
0.31
SPOP
0.52
0.30
ZADD
0.53
0.31
ZPOPMIN
0.54
0.31
LRANGE_100 (first 100 elements)
0.66
0.54
LRANGE_300 (first 300 elements)
1.15
1.11
LRANGE_500 (first 500 elements)
1.58
1.62
LRANGE_600 (first 600 elements)
1.87
1.84
MSET (10 keys)
0.53
0.38
Conclusion
From the friendly robots:
After analyzing the benchmark data for both the DigitalOcean and Vultr instances, it's evident that Vultr's Cloud Compute instance excels in general performance metrics, especially in Redis operations where it shows significantly higher request rates per second and lower latencies across various commands. DigitalOcean's Premium AMD instance, however, shines in certain areas like CPU-bound tasks and I/O operations, demonstrating better throughput and lower latencies in file I/O and memory operations. The Vultr instance offers a competitive edge in raw processing power and higher throughput for memory operations, while the DigitalOcean instance is more optimized for workloads that benefit from lower latencies in file I/O and memory. Ideal use cases for Vultr would be scenarios requiring high Redis throughput and lower latency in CPU-bound tasks, whereas DigitalOcean would be preferable for workloads emphasizing low latency in file I/O and memory operations.
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.