Welcome to another round of the VPS Showdown. Today I've spun up brand new instance from DigitalOcean and Vultr and ran my world famous suite of benchmarking scripts. All instances were spun up with Ubuntu 24.04 LTS x64 and were created in or around the New York / New Jersey area. Enough talk. Here's the data.
Overview
DigitalOcean – Premium AMD (2 GB)
Vultr – Cloud Compute (2 GB, 2 Cores)
Last Benchmarked
Tue, 12 May 2026 21: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
$14.00
$15.00
RAM (GB)
2
2
CPU Cores
1
2
Storage (TB)
50
65
Storage Type
NVMe
SSD
Transfer (TB)
2
3
CPU
DigitalOcean – Premium AMD (2 GB)
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.50
7,583.99
Events per Second
773.24
1,481.60
Minimum Latency (ms)
0.59
0.63
Average Latency (ms)
1.29
0.67
Maximum Latency (ms)
9.33
1.95
95th Percentile Latency (ms)
2.52
0.77
Memory
Memory Read
DigitalOcean – Premium AMD (2 GB)
Vultr – Cloud Compute (2 GB, 2 Cores)
Operations per second
2,488,460.19
6,401,389.08
Mebibytes per second
2,430.14
6,251.36
Minimum Latency (ms)
0
0
Average Latency (ms)
0
0
Maximum Latency (ms)
4.04
0.23
95th Percentile Latency (ms)
0
0
Memory Write
DigitalOcean – Premium AMD (2 GB)
Vultr – Cloud Compute (2 GB, 2 Cores)
Operations per second
4,683,187.88
6,411,085.35
Mebibytes per second
4,573.43
6,260.83
Minimum Latency (ms)
0
0
Average Latency (ms)
0
0
Maximum Latency (ms)
2.71
0.18
95th Percentile Latency (ms)
0
0
File I/O
DigitalOcean – Premium AMD (2 GB)
Vultr – Cloud Compute (2 GB, 2 Cores)
Reads per Second
1,845.04
4,345.71
Writes per Second
1,230.03
2,897.07
Fsyncs per Second
3,937.98
9,273.19
Read Mebibytes per Second
28.83
67.90
Written Mebibytes per Second
19.22
45.27
Minimum Latency (ms)
0
0
Average Latency (ms)
0.14
0.06
Maximum Latency (ms)
17.63
2.92
95th Percentile Latency (ms)
0.52
0.17
Mutex
DigitalOcean – Premium AMD (2 GB)
Vultr – Cloud Compute (2 GB, 2 Cores)
Minimum Latency (ms)
1,667.72
214.63
Average Latency (ms)
1,679.59
569.72
Maximum Latency (ms)
1,689.52
636.55
95th Percentile Latency (ms)
1,678.14
634.66
MySQL
MySQL Read-only
DigitalOcean – Premium AMD (2 GB)
Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second
6,277.00
8,015.00
Queries per second
62,770.00
80,150.00
Minimum Latency (ms)
1.39
0.92
Average Latency (ms)
1.59
1.25
Maximum Latency (ms)
3.05
5.5
95th Percentile Latency (ms)
2
1.86
MySQL Write-only
DigitalOcean – Premium AMD (2 GB)
Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second
3,904.00
8,497.00
Queries per second
39,040.00
84,970.00
Minimum Latency (ms)
1.49
0.76
Average Latency (ms)
2.56
1.17
Maximum Latency (ms)
16.24
3.04
95th Percentile Latency (ms)
3.75
1.55
MySQL Read/Write
DigitalOcean – Premium AMD (2 GB)
Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second
2,018.00
3,726.00
Queries per second
20,180.00
37,260.00
Minimum Latency (ms)
3.18
1.78
Average Latency (ms)
4.95
2.68
Maximum Latency (ms)
20.02
5.82
95th Percentile Latency (ms)
6.91
3.43
MySQL INSERT
DigitalOcean – Premium AMD (2 GB)
Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second
5,620.00
15,028.00
Queries per second
56,200.00
150,280.00
Minimum Latency (ms)
1.05
0.41
Average Latency (ms)
1.78
0.66
Maximum Latency (ms)
16.02
2.42
95th Percentile Latency (ms)
2.97
0.86
MySQL Bulk INSERT
DigitalOcean – Premium AMD (2 GB)
Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second
1,259,342.00
1,696,217.00
Queries per second
12,593,420.00
16,962,170.00
Minimum Latency (ms)
0
0
Average Latency (ms)
0.01
0.01
Maximum Latency (ms)
470.38
283.37
95th Percentile Latency (ms)
0
0
MySQL SELECT
DigitalOcean – Premium AMD (2 GB)
Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second
139,730.00
201,989.00
Queries per second
1,397,300.00
2,019,890.00
Minimum Latency (ms)
0.06
0.03
Average Latency (ms)
0.07
0.05
Maximum Latency (ms)
0.87
0.51
95th Percentile Latency (ms)
0.1
0.07
MySQL SELECT (Random Points)
DigitalOcean – Premium AMD (2 GB)
Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second
6,629.00
8,025.00
Queries per second
66,290.00
80,250.00
Minimum Latency (ms)
0.52
0.35
Average Latency (ms)
1.51
1.24
Maximum Latency (ms)
7.6
3.55
95th Percentile Latency (ms)
2.14
2.07
MySQL SELECT (Random Ranges)
DigitalOcean – Premium AMD (2 GB)
Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second
7,182.00
8,336.00
Queries per second
71,820.00
83,360.00
Minimum Latency (ms)
0.45
0.4
Average Latency (ms)
1.39
1.2
Maximum Latency (ms)
3.32
4.25
95th Percentile Latency (ms)
1.82
2.22
MySQL UPDATE (Indexed)
DigitalOcean – Premium AMD (2 GB)
Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second
5,947.00
13,858.00
Queries per second
59,470.00
138,580.00
Minimum Latency (ms)
0.88
0.42
Average Latency (ms)
1.68
0.72
Maximum Latency (ms)
23.74
6.33
95th Percentile Latency (ms)
2.57
0.95
MySQL UPDATE (Non-Indexed)
DigitalOcean – Premium AMD (2 GB)
Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second
6,209.00
14,587.00
Queries per second
62,090.00
145,870.00
Minimum Latency (ms)
1.06
0.4
Average Latency (ms)
1.61
0.68
Maximum Latency (ms)
20.85
11.69
95th Percentile Latency (ms)
2.39
0.9
MySQL DELETE
DigitalOcean – Premium AMD (2 GB)
Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second
44,794.00
129,013.00
Queries per second
447,940.00
1,290,130.00
Minimum Latency (ms)
0.06
0.03
Average Latency (ms)
0.22
0.08
Maximum Latency (ms)
16.86
2.61
95th Percentile Latency (ms)
1.42
0.09
Redis
DigitalOcean – Premium AMD (2 GB)
Vultr – Cloud Compute (2 GB, 2 Cores)
PING_INLINE per Second
39,729.84
78,247.26
PING_MBULK per Second
41,000.41
74,738.41
SET per Second
39,824.77
77,041.60
GET per Second
39,984.01
83,333.33
INCR per Second
39,184.95
80,971.66
LPUSH per Second
40,257.65
79,113.92
RPUSH per Second
39,936.10
77,160.49
LPOP per Second
39,777.25
81,499.59
RPOP per Second
38,865.14
82,440.23
SADD per Second
40,176.78
80,192.46
HSET per Second
36,995.93
83,612.04
SPOP per Second
39,184.95
85,034.02
ZADD per Second
39,339.10
83,263.95
ZPOPMIN per Second
41,050.90
82,987.55
LRANGE_100 (first 100 elements) per Second
26,702.27
55,555.56
LRANGE_300 (first 300 elements) per Second
14,887.60
28,851.70
LRANGE_500 (first 500 elements) per Second
10,069.48
19,391.12
LRANGE_600 (first 600 elements) per Second
9,017.13
17,211.71
MSET (10 keys) per Second
35,816.62
80,256.82
Redis Average Latency (ms)
DigitalOcean – Premium AMD (2 GB)
Vultr – Cloud Compute (2 GB, 2 Cores)
PING_INLINE
0.86
0.34
PING_MBULK
0.83
0.35
SET
0.86
0.34
GET
0.85
0.32
INCR
0.87
0.32
LPUSH
0.85
0.34
RPUSH
0.85
0.34
LPOP
0.86
0.32
RPOP
0.88
0.32
SADD
0.85
0.32
HSET
0.92
0.31
SPOP
0.87
0.30
ZADD
0.88
0.31
ZPOPMIN
0.83
0.31
LRANGE_100 (first 100 elements)
1.31
0.54
LRANGE_300 (first 300 elements)
2.40
1.11
LRANGE_500 (first 500 elements)
3.52
1.62
LRANGE_600 (first 600 elements)
3.96
1.84
MSET (10 keys)
0.98
0.38
Conclusion
From the friendly robots:
Upon comparing the benchmarks from the DigitalOcean Premium AMD and Vultr Cloud Compute instances, it is clear that the Vultr instance offers superior performance metrics in most areas, particularly in Redis operations where it consistently achieves higher requests per second and lower latencies. Both instances perform well in CPU-bound tasks but Vultr's dual-core Intel Xeon setup edges out the single-core AMD processor in most CPU benchmarks. File I/O operations also see better throughput and lower latencies on the Vultr server. However, DigitalOcean's instance provides very competitive results in memory operations and MySQL benchmarks, suggesting it might be more suitable for applications that heavily rely on memory efficiency and database operations. For workloads favoring CPU throughput and low latency in data handling, the Vultr instance is the better choice, whereas DigitalOcean's might be preferred for memory-intensive tasks and specific database 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.