DigitalOcean Regular (1 GB) vs. Vultr Cloud Compute (1 GB)
New day, new benchmarks. Today I've spun up brand new instance from DigitalOcean and Vultr and ran some benchmarks. Each instance was running Ubuntu 24.04 LTS x64 and all resided in or around the New York / New Jersey area. Without further ado, here's the results.
Overview
| DigitalOcean – Regular (1 GB) | Vultr – Cloud Compute (1 GB) | |
|---|---|---|
| Last Benchmarked | Thu, 25 Dec 2025 17:00:52 GMT | Tue, 23 Dec 2025 19:00:51 GMT |
| Linux Distro | Ubuntu 24.04 LTS x64 | Ubuntu 24.04 LTS x64 |
| Kernel Version | 6.8.0-71-generic | 6.8.0-90-generic |
| MySQL Version | 8.0.44-0ubuntu0.24.04.2 | 8.0.44-0ubuntu0.24.04.2 |
| Redis Version | 7.0.15 | 7.0.15 |
| Location | New York, NY | Newark, NJ |
| Monthly Price | $6.00 | $5.00 |
| RAM (GB) | 1 | 1 |
| CPU Cores | 1 | 1 |
| Storage (TB) | 25 | 25 |
| Storage Type | SSD | SSD |
| Transfer (TB) | 1 | 1 |
CPU
| DigitalOcean – Regular (1 GB) | Vultr – Cloud Compute (1 GB) | |
|---|---|---|
| Vendor | GenuineIntel | GenuineIntel |
| Model Name | DO-Regular | Intel Core Processor (Broadwell, no TSX, IBRS) |
| Clock Speed (MHz) | 2,494.14 | 2,400.00 |
| CPU Cache Size (KB) | 4,096.00 | 16,384.00 |
| BogoMips | 4,988.27 | 4,799.99 |
| Events per Second | 658.25 | 774.49 |
| Minimum Latency (ms) | 0.91 | 1.13 |
| Average Latency (ms) | 1.52 | 1.29 |
| Maximum Latency (ms) | 4.37 | 3.64 |
| 95th Percentile Latency (ms) | 2.76 | 1.55 |
Memory
Memory Read
| DigitalOcean – Regular (1 GB) | Vultr – Cloud Compute (1 GB) | |
|---|---|---|
| Operations per second | 4,590,506.96 | 3,563,144.39 |
| Mebibytes per second | 4,482.92 | 3,479.63 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 1.47 | 2.33 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| DigitalOcean – Regular (1 GB) | Vultr – Cloud Compute (1 GB) | |
|---|---|---|
| Operations per second | 4,461,825.89 | 3,578,279.14 |
| Mebibytes per second | 4,357.25 | 3,494.41 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 1.05 | 1.36 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| DigitalOcean – Regular (1 GB) | Vultr – Cloud Compute (1 GB) | |
|---|---|---|
| Reads per Second | 2,902.70 | 1,893.29 |
| Writes per Second | 1,935.13 | 1,262.20 |
| Fsyncs per Second | 6,204.32 | 4,041.52 |
| Read Mebibytes per Second | 45.35 | 29.58 |
| Written Mebibytes per Second | 30.24 | 19.72 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.09 | 0.14 |
| Maximum Latency (ms) | 31.01 | 7.93 |
| 95th Percentile Latency (ms) | 0.24 | 0.35 |
Mutex
| DigitalOcean – Regular (1 GB) | Vultr – Cloud Compute (1 GB) | |
|---|---|---|
| Minimum Latency (ms) | 1,886.90 | 2,405.08 |
| Average Latency (ms) | 1,902.88 | 2,423.84 |
| Maximum Latency (ms) | 1,917.74 | 2,436.20 |
| 95th Percentile Latency (ms) | 1,903.57 | 2,449.36 |
MySQL
MySQL Read-only
| DigitalOcean – Regular (1 GB) | Vultr – Cloud Compute (1 GB) | |
|---|---|---|
| Transactions per second | 6,616.00 | 4,627.00 |
| Queries per second | 66,160.00 | 46,270.00 |
| Minimum Latency (ms) | 1.13 | 1.69 |
| Average Latency (ms) | 1.51 | 2.16 |
| Maximum Latency (ms) | 6.91 | 14.35 |
| 95th Percentile Latency (ms) | 2.22 | 3.13 |
MySQL Write-only
| DigitalOcean – Regular (1 GB) | Vultr – Cloud Compute (1 GB) | |
|---|---|---|
| Transactions per second | 5,741.00 | 3,192.00 |
| Queries per second | 57,410.00 | 31,920.00 |
| Minimum Latency (ms) | 0.97 | 1.88 |
| Average Latency (ms) | 1.74 | 3.13 |
| Maximum Latency (ms) | 25.7 | 32.5 |
| 95th Percentile Latency (ms) | 2.61 | 4.57 |
MySQL Read/Write
| DigitalOcean – Regular (1 GB) | Vultr – Cloud Compute (1 GB) | |
|---|---|---|
| Transactions per second | 2,490.00 | 1,733.00 |
| Queries per second | 24,900.00 | 17,330.00 |
| Minimum Latency (ms) | 2.67 | 3.98 |
| Average Latency (ms) | 4.01 | 5.77 |
| Maximum Latency (ms) | 26.68 | 15.77 |
| 95th Percentile Latency (ms) | 5.67 | 8.28 |
MySQL INSERT
| DigitalOcean – Regular (1 GB) | Vultr – Cloud Compute (1 GB) | |
|---|---|---|
| Transactions per second | 9,069.00 | 5,038.00 |
| Queries per second | 90,690.00 | 50,380.00 |
| Minimum Latency (ms) | 0.48 | 1.29 |
| Average Latency (ms) | 1.1 | 1.98 |
| Maximum Latency (ms) | 80.73 | 20.82 |
| 95th Percentile Latency (ms) | 1.73 | 2.76 |
MySQL Bulk INSERT
| DigitalOcean – Regular (1 GB) | Vultr – Cloud Compute (1 GB) | |
|---|---|---|
| Transactions per second | 1,055,467.00 | 800,273.00 |
| Queries per second | 10,554,670.00 | 8,002,730.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0.01 |
| Maximum Latency (ms) | 1012.19 | 783.86 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| DigitalOcean – Regular (1 GB) | Vultr – Cloud Compute (1 GB) | |
|---|---|---|
| Transactions per second | 188,955.00 | 100,060.00 |
| Queries per second | 1,889,550.00 | 1,000,600.00 |
| Minimum Latency (ms) | 0.04 | 0.07 |
| Average Latency (ms) | 0.05 | 0.1 |
| Maximum Latency (ms) | 1.59 | 9.15 |
| 95th Percentile Latency (ms) | 0.08 | 0.15 |
MySQL SELECT (Random Points)
| DigitalOcean – Regular (1 GB) | Vultr – Cloud Compute (1 GB) | |
|---|---|---|
| Transactions per second | 5,352.00 | 4,470.00 |
| Queries per second | 53,520.00 | 44,700.00 |
| Minimum Latency (ms) | 0.55 | 0.68 |
| Average Latency (ms) | 1.87 | 2.23 |
| Maximum Latency (ms) | 6.67 | 9.2 |
| 95th Percentile Latency (ms) | 2.97 | 3.55 |
MySQL SELECT (Random Ranges)
| DigitalOcean – Regular (1 GB) | Vultr – Cloud Compute (1 GB) | |
|---|---|---|
| Transactions per second | 5,879.00 | 4,738.00 |
| Queries per second | 58,790.00 | 47,380.00 |
| Minimum Latency (ms) | 0.5 | 0.65 |
| Average Latency (ms) | 1.7 | 2.11 |
| Maximum Latency (ms) | 5.23 | 8.72 |
| 95th Percentile Latency (ms) | 3.02 | 3.68 |
MySQL UPDATE (Indexed)
| DigitalOcean – Regular (1 GB) | Vultr – Cloud Compute (1 GB) | |
|---|---|---|
| Transactions per second | 9,925.00 | 4,344.00 |
| Queries per second | 99,250.00 | 43,440.00 |
| Minimum Latency (ms) | 0.47 | 1.12 |
| Average Latency (ms) | 1.01 | 2.3 |
| Maximum Latency (ms) | 48.42 | 37 |
| 95th Percentile Latency (ms) | 1.67 | 3.96 |
MySQL UPDATE (Non-Indexed)
| DigitalOcean – Regular (1 GB) | Vultr – Cloud Compute (1 GB) | |
|---|---|---|
| Transactions per second | 9,177.00 | 5,409.00 |
| Queries per second | 91,770.00 | 54,090.00 |
| Minimum Latency (ms) | 0.46 | 1.08 |
| Average Latency (ms) | 1.09 | 1.85 |
| Maximum Latency (ms) | 103.03 | 13.01 |
| 95th Percentile Latency (ms) | 1.73 | 2.52 |
MySQL DELETE
| DigitalOcean – Regular (1 GB) | Vultr – Cloud Compute (1 GB) | |
|---|---|---|
| Transactions per second | 77,722.00 | 34,310.00 |
| Queries per second | 777,220.00 | 343,100.00 |
| Minimum Latency (ms) | 0.04 | 0.07 |
| Average Latency (ms) | 0.13 | 0.29 |
| Maximum Latency (ms) | 27.76 | 6.95 |
| 95th Percentile Latency (ms) | 0.48 | 1.82 |
Redis
| DigitalOcean – Regular (1 GB) | Vultr – Cloud Compute (1 GB) | |
|---|---|---|
| PING_INLINE per Second | 41,597.34 | 33,670.04 |
| PING_MBULK per Second | 42,826.55 | 32,948.93 |
| SET per Second | 45,516.61 | 32,829.94 |
| GET per Second | 44,923.63 | 34,411.56 |
| INCR per Second | 46,317.74 | 36,258.16 |
| LPUSH per Second | 47,348.48 | 32,435.94 |
| RPUSH per Second | 45,106.00 | 34,891.84 |
| LPOP per Second | 42,444.82 | 31,938.68 |
| RPOP per Second | 43,271.31 | 31,605.56 |
| SADD per Second | 42,087.54 | 32,679.74 |
| HSET per Second | 37,509.38 | 33,840.95 |
| SPOP per Second | 40,567.95 | 34,411.56 |
| ZADD per Second | 37,369.21 | 34,542.32 |
| ZPOPMIN per Second | 41,823.50 | 34,176.35 |
| LRANGE_100 (first 100 elements) per Second | 20,128.82 | 22,084.81 |
| LRANGE_300 (first 300 elements) per Second | 10,488.78 | 10,593.22 |
| LRANGE_500 (first 500 elements) per Second | 6,303.18 | 7,519.93 |
| LRANGE_600 (first 600 elements) per Second | 5,894.49 | 5,956.28 |
| MSET (10 keys) per Second | 38,461.54 | 29,594.55 |
Redis Average Latency (ms)
| DigitalOcean – Regular (1 GB) | Vultr – Cloud Compute (1 GB) | |
|---|---|---|
| PING_INLINE | 0.80 | 0.97 |
| PING_MBULK | 0.77 | 0.98 |
| SET | 0.74 | 0.99 |
| GET | 0.74 | 0.95 |
| INCR | 0.72 | 0.91 |
| LPUSH | 0.71 | 1.01 |
| RPUSH | 0.75 | 0.95 |
| LPOP | 0.79 | 1.04 |
| RPOP | 0.78 | 1.04 |
| SADD | 0.79 | 1.00 |
| HSET | 0.89 | 0.98 |
| SPOP | 0.81 | 0.95 |
| ZADD | 0.90 | 0.96 |
| ZPOPMIN | 0.79 | 0.96 |
| LRANGE_100 (first 100 elements) | 1.80 | 1.53 |
| LRANGE_300 (first 300 elements) | 3.47 | 3.20 |
| LRANGE_500 (first 500 elements) | 5.67 | 4.53 |
| LRANGE_600 (first 600 elements) | 6.06 | 5.63 |
| MSET (10 keys) | 0.92 | 1.17 |
Conclusion
From the friendly robots:
After analyzing the benchmark results from both DigitalOcean and Vultr's 1 GB instances, it is evident that both providers deliver strong performance suitable for various tasks, though they excel in different areas. DigitalOcean's instance shows superior Redis performance with higher RPS and slightly lower latency across most operations, reflecting its optimization for database tasks. Vultr's instance, however, stands out in terms of raw CPU event throughput and memory bandwidth, which indicates it could be more advantageous for CPU-intensive workloads and high memory operations. When it comes to file I/O and MySQL performance, Vultr edges out DigitalOcean, showcasing faster throughput and lower latency for file operations and more robust MySQL performance. Given these metrics, DigitalOcean is ideal for database-centric applications needing high Redis performance, whereas Vultr would be better suited for CPU and memory-intensive tasks along with demanding file I/O 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.