DigitalOcean Regular (4 GB, 2 Cores) vs. Vultr High Frequency Intel (2 GB, 2 Cores)

vs.

New day, new benchmarks. 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). Let's get into the numbers.

Overview

DigitalOcean – Regular (4 GB, 2 Cores) Vultr – High Frequency Intel (2 GB, 2 Cores)
Last Benchmarked Sat, 30 May 2026 15:00:52 GMT Sun, 31 May 2026 13:00:55 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 80
Storage Type SSD NVMe
Transfer (TB) 4 3

CPU

DigitalOcean – Regular (4 GB, 2 Cores) Vultr – High Frequency Intel (2 GB, 2 Cores)
Vendor GenuineIntel GenuineIntel
Model Name DO-Regular Intel Core Processor (Skylake, IBRS, no TSX)
Clock Speed (MHz) 2,494.15 3,791.98
CPU Cache Size (KB) 4,096.00 16,384.00
BogoMips 4,988.29 7,583.95
Events per Second 871.36 1,552.05
Minimum Latency (ms) 0.91 0.62
Average Latency (ms) 1.15 0.64
Maximum Latency (ms) 5.11 4.61
95th Percentile Latency (ms) 1.34 0.69

Memory

Memory Read

DigitalOcean – Regular (4 GB, 2 Cores) Vultr – High Frequency Intel (2 GB, 2 Cores)
Operations per second 4,167,908.44 7,875,668.83
Mebibytes per second 4,070.22 7,691.08
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 0.26 0.12
95th Percentile Latency (ms) 0 0

Memory Write

DigitalOcean – Regular (4 GB, 2 Cores) Vultr – High Frequency Intel (2 GB, 2 Cores)
Operations per second 4,455,346.90 7,729,812.11
Mebibytes per second 4,350.92 7,548.64
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 0.26 0.16
95th Percentile Latency (ms) 0 0

File I/O

DigitalOcean – Regular (4 GB, 2 Cores) Vultr – High Frequency Intel (2 GB, 2 Cores)
Reads per Second 2,278.19 4,671.85
Writes per Second 1,518.80 3,114.56
Fsyncs per Second 4,871.44 9,976.90
Read Mebibytes per Second 35.60 73.00
Written Mebibytes per Second 23.73 48.67
Minimum Latency (ms) 0 0
Average Latency (ms) 0.11 0.06
Maximum Latency (ms) 12.59 2.76
95th Percentile Latency (ms) 0.37 0.17

Mutex

DigitalOcean – Regular (4 GB, 2 Cores) Vultr – High Frequency Intel (2 GB, 2 Cores)
Minimum Latency (ms) 1,307.95 543.27
Average Latency (ms) 1,349.23 554.74
Maximum Latency (ms) 1,391.63 563.70
95th Percentile Latency (ms) 1,401.61 559.50

MySQL

MySQL Read-only

DigitalOcean – Regular (4 GB, 2 Cores) Vultr – High Frequency Intel (2 GB, 2 Cores)
Transactions per second 4,297.00 10,621.00
Queries per second 42,970.00 106,210.00
Minimum Latency (ms) 1.39 0.86
Average Latency (ms) 2.32 0.94
Maximum Latency (ms) 5.78 2.5
95th Percentile Latency (ms) 2.97 1.03

MySQL Write-only

DigitalOcean – Regular (4 GB, 2 Cores) Vultr – High Frequency Intel (2 GB, 2 Cores)
Transactions per second 3,514.00 10,229.00
Queries per second 35,140.00 102,290.00
Minimum Latency (ms) 1.29 0.64
Average Latency (ms) 2.84 0.98
Maximum Latency (ms) 13.78 2.08
95th Percentile Latency (ms) 4.1 1.23

MySQL Read/Write

DigitalOcean – Regular (4 GB, 2 Cores) Vultr – High Frequency Intel (2 GB, 2 Cores)
Transactions per second 1,947.00 5,072.00
Queries per second 19,470.00 50,720.00
Minimum Latency (ms) 2.91 1.59
Average Latency (ms) 5.13 1.97
Maximum Latency (ms) 13.08 3.94
95th Percentile Latency (ms) 6.67 2.39

MySQL INSERT

DigitalOcean – Regular (4 GB, 2 Cores) Vultr – High Frequency Intel (2 GB, 2 Cores)
Transactions per second 6,796.00 16,038.00
Queries per second 67,960.00 160,380.00
Minimum Latency (ms) 0.65 0.38
Average Latency (ms) 1.47 0.62
Maximum Latency (ms) 10.09 13.18
95th Percentile Latency (ms) 2.18 0.8

MySQL Bulk INSERT

DigitalOcean – Regular (4 GB, 2 Cores) Vultr – High Frequency Intel (2 GB, 2 Cores)
Transactions per second 1,055,467.00 2,424,342.00
Queries per second 10,554,670.00 24,243,420.00
Minimum Latency (ms) 0 0
Average Latency (ms) 0.01 0
Maximum Latency (ms) 573.76 205.81
95th Percentile Latency (ms) 0 0

MySQL SELECT

DigitalOcean – Regular (4 GB, 2 Cores) Vultr – High Frequency Intel (2 GB, 2 Cores)
Transactions per second 123,372.00 241,313.00
Queries per second 1,233,720.00 2,413,130.00
Minimum Latency (ms) 0.04 0.03
Average Latency (ms) 0.08 0.04
Maximum Latency (ms) 1.53 0.76
95th Percentile Latency (ms) 0.12 0.05

MySQL SELECT (Random Points)

DigitalOcean – Regular (4 GB, 2 Cores) Vultr – High Frequency Intel (2 GB, 2 Cores)
Transactions per second 4,146.00 12,080.00
Queries per second 41,460.00 120,800.00
Minimum Latency (ms) 0.81 0.21
Average Latency (ms) 2.41 0.83
Maximum Latency (ms) 21.02 3.31
95th Percentile Latency (ms) 3.36 1.04

MySQL SELECT (Random Ranges)

DigitalOcean – Regular (4 GB, 2 Cores) Vultr – High Frequency Intel (2 GB, 2 Cores)
Transactions per second 4,644.00 10,527.00
Queries per second 46,440.00 105,270.00
Minimum Latency (ms) 0.75 0.16
Average Latency (ms) 2.15 0.95
Maximum Latency (ms) 8.73 3.25
95th Percentile Latency (ms) 3.19 1.23

MySQL UPDATE (Indexed)

DigitalOcean – Regular (4 GB, 2 Cores) Vultr – High Frequency Intel (2 GB, 2 Cores)
Transactions per second 5,918.00 17,123.00
Queries per second 59,180.00 171,230.00
Minimum Latency (ms) 0.61 0.38
Average Latency (ms) 1.69 0.58
Maximum Latency (ms) 17.54 2
95th Percentile Latency (ms) 2.71 0.78

MySQL UPDATE (Non-Indexed)

DigitalOcean – Regular (4 GB, 2 Cores) Vultr – High Frequency Intel (2 GB, 2 Cores)
Transactions per second 6,844.00 16,979.00
Queries per second 68,440.00 169,790.00
Minimum Latency (ms) 0.7 0.38
Average Latency (ms) 1.46 0.59
Maximum Latency (ms) 11.43 4.13
95th Percentile Latency (ms) 2.11 0.8

MySQL DELETE

DigitalOcean – Regular (4 GB, 2 Cores) Vultr – High Frequency Intel (2 GB, 2 Cores)
Transactions per second 55,206.00 156,424.00
Queries per second 552,060.00 1,564,240.00
Minimum Latency (ms) 0.04 0.03
Average Latency (ms) 0.18 0.06
Maximum Latency (ms) 6.66 4.87
95th Percentile Latency (ms) 1.18 0.07

Redis

DigitalOcean – Regular (4 GB, 2 Cores) Vultr – High Frequency Intel (2 GB, 2 Cores)
PING_INLINE per Second 50,607.29 88,652.48
PING_MBULK per Second 44,169.61 89,605.73
SET per Second 44,444.45 90,171.33
GET per Second 47,619.05 90,579.71
INCR per Second 48,638.13 90,744.10
LPUSH per Second 49,603.17 90,497.73
RPUSH per Second 47,664.44 90,415.91
LPOP per Second 50,942.43 90,909.09
RPOP per Second 48,216.01 90,661.83
SADD per Second 48,379.30 90,252.70
HSET per Second 48,053.82 90,415.91
SPOP per Second 50,301.81 89,928.05
ZADD per Second 54,495.91 90,415.91
ZPOPMIN per Second 50,864.70 90,009.01
LRANGE_100 (first 100 elements) per Second 33,523.30 66,533.60
LRANGE_300 (first 300 elements) per Second 16,619.58 36,179.45
LRANGE_500 (first 500 elements) per Second 10,716.96 26,239.83
LRANGE_600 (first 600 elements) per Second 9,849.31 22,547.91
MSET (10 keys) per Second 46,189.38 88,105.73

Redis Average Latency (ms)

DigitalOcean – Regular (4 GB, 2 Cores) Vultr – High Frequency Intel (2 GB, 2 Cores)
PING_INLINE0.550.30
PING_MBULK0.590.29
SET0.600.29
GET0.560.29
INCR0.550.28
LPUSH0.540.29
RPUSH0.560.29
LPOP0.530.28
RPOP0.560.28
SADD0.550.29
HSET0.570.29
SPOP0.530.29
ZADD0.500.29
ZPOPMIN0.520.29
LRANGE_100 (first 100 elements)1.040.39
LRANGE_300 (first 300 elements)1.780.71
LRANGE_500 (first 500 elements)2.920.97
LRANGE_600 (first 600 elements)3.431.14
MSET (10 keys)0.670.30

Conclusion

From the friendly robots:

Both DigitalOcean's Regular instance and Vultr's High Frequency Intel instance showcase strong performance metrics, though they cater to different use cases. DigitalOcean's instance provides slightly better Redis throughput and lower latency for most Redis operations, along with robust CPU performance, making it a good choice for CPU-intensive workloads. It also has excellent file I/O and memory operations. However, Vultr's High Frequency Intel instance shows superior Redis rps, better CPU throughput, and faster MySQL operations, which makes it highly suited for applications requiring high-speed Redis interaction and more aggressive CPU-bound tasks. The NVMe storage of Vultr could also give it an edge in I/O-heavy scenarios. Ultimately, the choice between these instances will depend on whether your priority is on CPU-intensive tasks, general-purpose performance, or high-speed Redis 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.

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