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

vs.

New day, new benchmarks. Today I've spun up brand new instance from DigitalOcean and Vultr and ran my world famous suite of benchmarking scripts. Each instance was spun up with Ubuntu 24.04 LTS x64 and all resided in or around the New York / New Jersey area. Enough talk. Here's the data.

Overview

DigitalOcean – Regular (2 GB) Vultr – High Performance Intel (2 GB, 2 Cores)
Last Benchmarked Tue, 12 May 2026 23:00:52 GMT Sun, 10 May 2026 11: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 $12.00 $18.00
RAM (GB) 2 2
CPU Cores 1 2
Storage (TB) 50 60
Storage Type SSD NVMe
Transfer (TB) 2 4

CPU

DigitalOcean – Regular (2 GB) Vultr – High Performance Intel (2 GB, 2 Cores)
Vendor GenuineIntel GenuineIntel
Model Name DO-Regular Intel Xeon Processor (Cascadelake)
Clock Speed (MHz) 2,294.61 2,992.97
CPU Cache Size (KB) 4,096.00 16,384.00
BogoMips 4,589.21 5,985.94
Events per Second 408.72 1,206.35
Minimum Latency (ms) 0.98 0.81
Average Latency (ms) 2.44 0.83
Maximum Latency (ms) 30.57 3.72
95th Percentile Latency (ms) 4.1 0.87

Memory

Memory Read

DigitalOcean – Regular (2 GB) Vultr – High Performance Intel (2 GB, 2 Cores)
Operations per second 1,633,276.41 5,547,051.31
Mebibytes per second 1,595.00 5,417.04
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 3.35 0.26
95th Percentile Latency (ms) 0 0

Memory Write

DigitalOcean – Regular (2 GB) Vultr – High Performance Intel (2 GB, 2 Cores)
Operations per second 1,592,941.48 5,558,117.22
Mebibytes per second 1,555.61 5,427.85
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 5.53 0.27
95th Percentile Latency (ms) 0 0

File I/O

DigitalOcean – Regular (2 GB) Vultr – High Performance Intel (2 GB, 2 Cores)
Reads per Second 1,584.78 4,995.49
Writes per Second 1,056.52 3,330.33
Fsyncs per Second 3,385.97 10,663.75
Read Mebibytes per Second 24.76 78.05
Written Mebibytes per Second 16.51 52.04
Minimum Latency (ms) 0 0
Average Latency (ms) 0.16 0.05
Maximum Latency (ms) 20.31 2.44
95th Percentile Latency (ms) 0.51 0.16

Mutex

DigitalOcean – Regular (2 GB) Vultr – High Performance Intel (2 GB, 2 Cores)
Minimum Latency (ms) 2,434.32 683.77
Average Latency (ms) 2,473.55 748.22
Maximum Latency (ms) 2,489.41 783.12
95th Percentile Latency (ms) 2,493.86 787.74

MySQL

MySQL Read-only

DigitalOcean – Regular (2 GB) Vultr – High Performance Intel (2 GB, 2 Cores)
Transactions per second 4,752.00 8,426.00
Queries per second 47,520.00 84,260.00
Minimum Latency (ms) 1.23 1.06
Average Latency (ms) 2.1 1.19
Maximum Latency (ms) 5.76 2.7
95th Percentile Latency (ms) 2.66 1.42

MySQL Write-only

DigitalOcean – Regular (2 GB) Vultr – High Performance Intel (2 GB, 2 Cores)
Transactions per second 1,930.00 9,541.00
Queries per second 19,300.00 95,410.00
Minimum Latency (ms) 2.65 0.71
Average Latency (ms) 5.18 1.05
Maximum Latency (ms) 56.83 2.61
95th Percentile Latency (ms) 7.98 1.39

MySQL Read/Write

DigitalOcean – Regular (2 GB) Vultr – High Performance Intel (2 GB, 2 Cores)
Transactions per second 1,306.00 4,278.00
Queries per second 13,060.00 42,780.00
Minimum Latency (ms) 4.6 1.88
Average Latency (ms) 7.65 2.34
Maximum Latency (ms) 28.54 4.6
95th Percentile Latency (ms) 10.09 2.91

MySQL INSERT

DigitalOcean – Regular (2 GB) Vultr – High Performance Intel (2 GB, 2 Cores)
Transactions per second 3,148.00 17,143.00
Queries per second 31,480.00 171,430.00
Minimum Latency (ms) 1.72 0.41
Average Latency (ms) 3.17 0.58
Maximum Latency (ms) 32.67 4.51
95th Percentile Latency (ms) 4.41 0.74

MySQL Bulk INSERT

DigitalOcean – Regular (2 GB) Vultr – High Performance Intel (2 GB, 2 Cores)
Transactions per second 669,209.00 1,637,967.00
Queries per second 6,692,090.00 16,379,670.00
Minimum Latency (ms) 0 0
Average Latency (ms) 0.02 0.01
Maximum Latency (ms) 772.1 276.34
95th Percentile Latency (ms) 0 0

MySQL SELECT

DigitalOcean – Regular (2 GB) Vultr – High Performance Intel (2 GB, 2 Cores)
Transactions per second 136,020.00 214,349.00
Queries per second 1,360,200.00 2,143,490.00
Minimum Latency (ms) 0.04 0.03
Average Latency (ms) 0.07 0.05
Maximum Latency (ms) 3.33 1.06
95th Percentile Latency (ms) 0.11 0.06

MySQL SELECT (Random Points)

DigitalOcean – Regular (2 GB) Vultr – High Performance Intel (2 GB, 2 Cores)
Transactions per second 3,617.00 7,396.00
Queries per second 36,170.00 73,960.00
Minimum Latency (ms) 0.82 0.54
Average Latency (ms) 2.76 1.35
Maximum Latency (ms) 12.27 3.05
95th Percentile Latency (ms) 3.82 1.86

MySQL SELECT (Random Ranges)

DigitalOcean – Regular (2 GB) Vultr – High Performance Intel (2 GB, 2 Cores)
Transactions per second 3,087.00 7,947.00
Queries per second 30,870.00 79,470.00
Minimum Latency (ms) 0.67 0.46
Average Latency (ms) 3.23 1.26
Maximum Latency (ms) 8.52 3.14
95th Percentile Latency (ms) 5.18 1.7

MySQL UPDATE (Indexed)

DigitalOcean – Regular (2 GB) Vultr – High Performance Intel (2 GB, 2 Cores)
Transactions per second 2,586.00 16,993.00
Queries per second 25,860.00 169,930.00
Minimum Latency (ms) 1.8 0.41
Average Latency (ms) 3.86 0.59
Maximum Latency (ms) 45.13 9.08
95th Percentile Latency (ms) 6.21 0.8

MySQL UPDATE (Non-Indexed)

DigitalOcean – Regular (2 GB) Vultr – High Performance Intel (2 GB, 2 Cores)
Transactions per second 3,094.00 17,168.00
Queries per second 30,940.00 171,680.00
Minimum Latency (ms) 1.83 0.39
Average Latency (ms) 3.23 0.58
Maximum Latency (ms) 35.75 1.77
95th Percentile Latency (ms) 4.65 0.75

MySQL DELETE

DigitalOcean – Regular (2 GB) Vultr – High Performance Intel (2 GB, 2 Cores)
Transactions per second 19,562.00 139,126.00
Queries per second 195,620.00 1,391,260.00
Minimum Latency (ms) 0.04 0.03
Average Latency (ms) 0.51 0.07
Maximum Latency (ms) 32.94 2.43
95th Percentile Latency (ms) 3.02 0.1

Redis

DigitalOcean – Regular (2 GB) Vultr – High Performance Intel (2 GB, 2 Cores)
PING_INLINE per Second 39,729.84 66,622.25
PING_MBULK per Second 42,176.30 66,050.20
SET per Second 40,833.00 67,567.57
GET per Second 34,590.11 68,027.21
INCR per Second 35,410.77 67,934.78
LPUSH per Second 39,184.95 68,306.01
RPUSH per Second 36,509.68 69,444.45
LPOP per Second 36,791.76 70,028.02
RPOP per Second 38,834.95 67,613.25
SADD per Second 35,727.05 66,711.14
HSET per Second 35,790.98 69,060.77
SPOP per Second 39,478.88 68,352.70
ZADD per Second 38,850.04 68,917.99
ZPOPMIN per Second 40,338.84 67,613.25
LRANGE_100 (first 100 elements) per Second 17,461.15 52,576.24
LRANGE_300 (first 300 elements) per Second 7,711.29 29,841.84
LRANGE_500 (first 500 elements) per Second 4,860.50 20,157.23
LRANGE_600 (first 600 elements) per Second 4,094.67 17,624.25
MSET (10 keys) per Second 32,041.01 71,684.59

Redis Average Latency (ms)

DigitalOcean – Regular (2 GB) Vultr – High Performance Intel (2 GB, 2 Cores)
PING_INLINE0.830.40
PING_MBULK0.780.39
SET0.820.38
GET0.940.38
INCR0.930.38
LPUSH0.850.38
RPUSH0.910.37
LPOP0.920.37
RPOP0.870.38
SADD0.920.39
HSET0.930.38
SPOP0.840.38
ZADD0.860.37
ZPOPMIN0.820.38
LRANGE_100 (first 100 elements)2.050.50
LRANGE_300 (first 300 elements)4.590.90
LRANGE_500 (first 500 elements)7.191.32
LRANGE_600 (first 600 elements)8.421.58
MSET (10 keys)1.120.36

Conclusion

From the friendly robots:

The Vultr High Performance Intel (2 GB, 2 Cores) instance shows superior performance in most benchmarks compared to the DigitalOcean Regular (2 GB) instance, notably in CPU-intensive tasks like Redis operations where the Vultr instance delivers higher requests per second (rps) and lower latencies. The Vultr instance also outperforms in file I/O and memory operations, suggesting it's better suited for I/O-heavy workloads. The DigitalOcean instance, while still capable, lags behind in these metrics but offers acceptable performance for basic tasks. The Vultr's dual-core setup provides a significant edge in parallel processing and higher throughput, making it ideal for demanding applications such as high-concurrency web services, database operations, and data processing tasks. On the other hand, the DigitalOcean instance is a cost-effective solution for less demanding workloads where lower cost is a primary concern.

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.