Vultr Cloud Compute (1 GB) vs. DigitalOcean Regular (1 GB)
New day, new benchmarks. Today I've spun up brand new instance from DigitalOcean and Vultr and did some benchmarking. Each instance was spun up with Ubuntu 24.04 LTS x64 and were created in the New York area (or close to it). Let's get into the numbers.
Overview
| Vultr – Cloud Compute (1 GB) | DigitalOcean – Regular (1 GB) | |
|---|---|---|
| Last Benchmarked | Thu, 21 May 2026 23:00:52 GMT | Sun, 24 May 2026 06:00:51 GMT |
| Linux Distro | Ubuntu 24.04 LTS x64 | Ubuntu 24.04 LTS x64 |
| Kernel Version | 6.8.0-117-generic | 6.8.0-71-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 | Newark, NJ | New York, NY |
| Monthly Price | $5.00 | $6.00 |
| RAM (GB) | 1 | 1 |
| CPU Cores | 1 | 1 |
| Storage (TB) | 25 | 25 |
| Storage Type | SSD | SSD |
| Transfer (TB) | 1 | 1 |
CPU
| Vultr – Cloud Compute (1 GB) | DigitalOcean – Regular (1 GB) | |
|---|---|---|
| Vendor | GenuineIntel | GenuineIntel |
| Model Name | Intel Core Processor (Broadwell, no TSX, IBRS) | DO-Regular |
| Clock Speed (MHz) | 2,394.45 | 2,494.17 |
| CPU Cache Size (KB) | 16,384.00 | 4,096.00 |
| BogoMips | 4,788.90 | 4,988.33 |
| Events per Second | 859.04 | 544.64 |
| Minimum Latency (ms) | 1.14 | 0.91 |
| Average Latency (ms) | 1.16 | 1.83 |
| Maximum Latency (ms) | 2.42 | 6.05 |
| 95th Percentile Latency (ms) | 1.25 | 3.3 |
Memory
Memory Read
| Vultr – Cloud Compute (1 GB) | DigitalOcean – Regular (1 GB) | |
|---|---|---|
| Operations per second | 4,179,696.98 | 3,884,147.58 |
| Mebibytes per second | 4,081.74 | 3,793.11 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.23 | 4.21 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – Cloud Compute (1 GB) | DigitalOcean – Regular (1 GB) | |
|---|---|---|
| Operations per second | 4,151,553.00 | 3,855,342.89 |
| Mebibytes per second | 4,054.25 | 3,764.98 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.59 | 4.09 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – Cloud Compute (1 GB) | DigitalOcean – Regular (1 GB) | |
|---|---|---|
| Reads per Second | 2,403.90 | 1,941.53 |
| Writes per Second | 1,602.60 | 1,294.36 |
| Fsyncs per Second | 5,132.41 | 4,148.23 |
| Read Mebibytes per Second | 37.56 | 30.34 |
| Written Mebibytes per Second | 25.04 | 20.22 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.11 | 0.13 |
| Maximum Latency (ms) | 3.04 | 14.04 |
| 95th Percentile Latency (ms) | 0.32 | 0.37 |
Mutex
| Vultr – Cloud Compute (1 GB) | DigitalOcean – Regular (1 GB) | |
|---|---|---|
| Minimum Latency (ms) | 2,066.64 | 2,442.65 |
| Average Latency (ms) | 2,071.43 | 2,474.33 |
| Maximum Latency (ms) | 2,075.26 | 2,494.37 |
| 95th Percentile Latency (ms) | 2,082.91 | 2,493.86 |
MySQL
MySQL Read-only
| Vultr – Cloud Compute (1 GB) | DigitalOcean – Regular (1 GB) | |
|---|---|---|
| Transactions per second | 5,409.00 | 5,075.00 |
| Queries per second | 54,090.00 | 50,750.00 |
| Minimum Latency (ms) | 1.74 | 1.28 |
| Average Latency (ms) | 1.85 | 1.97 |
| Maximum Latency (ms) | 13.71 | 7.01 |
| 95th Percentile Latency (ms) | 2 | 2.52 |
MySQL Write-only
| Vultr – Cloud Compute (1 GB) | DigitalOcean – Regular (1 GB) | |
|---|---|---|
| Transactions per second | 4,997.00 | 3,624.00 |
| Queries per second | 49,970.00 | 36,240.00 |
| Minimum Latency (ms) | 1.47 | 1.32 |
| Average Latency (ms) | 2 | 2.75 |
| Maximum Latency (ms) | 10.54 | 14.77 |
| 95th Percentile Latency (ms) | 2.61 | 4.25 |
MySQL Read/Write
| Vultr – Cloud Compute (1 GB) | DigitalOcean – Regular (1 GB) | |
|---|---|---|
| Transactions per second | 2,422.00 | 1,703.00 |
| Queries per second | 24,220.00 | 17,030.00 |
| Minimum Latency (ms) | 3.55 | 3.52 |
| Average Latency (ms) | 4.13 | 5.86 |
| Maximum Latency (ms) | 12.42 | 19.13 |
| 95th Percentile Latency (ms) | 4.82 | 7.98 |
MySQL INSERT
| Vultr – Cloud Compute (1 GB) | DigitalOcean – Regular (1 GB) | |
|---|---|---|
| Transactions per second | 9,166.00 | 6,947.00 |
| Queries per second | 91,660.00 | 69,470.00 |
| Minimum Latency (ms) | 0.71 | 0.67 |
| Average Latency (ms) | 1.09 | 1.43 |
| Maximum Latency (ms) | 6.03 | 10.58 |
| 95th Percentile Latency (ms) | 1.39 | 2.11 |
MySQL Bulk INSERT
| Vultr – Cloud Compute (1 GB) | DigitalOcean – Regular (1 GB) | |
|---|---|---|
| Transactions per second | 937,763.00 | 898,571.00 |
| Queries per second | 9,377,630.00 | 8,985,710.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0.01 |
| Maximum Latency (ms) | 661.15 | 604.32 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – Cloud Compute (1 GB) | DigitalOcean – Regular (1 GB) | |
|---|---|---|
| Transactions per second | 117,346.00 | 134,023.00 |
| Queries per second | 1,173,460.00 | 1,340,230.00 |
| Minimum Latency (ms) | 0.07 | 0.04 |
| Average Latency (ms) | 0.08 | 0.07 |
| Maximum Latency (ms) | 7.11 | 1.96 |
| 95th Percentile Latency (ms) | 0.11 | 0.12 |
MySQL SELECT (Random Points)
| Vultr – Cloud Compute (1 GB) | DigitalOcean – Regular (1 GB) | |
|---|---|---|
| Transactions per second | 5,731.00 | 3,981.00 |
| Queries per second | 57,310.00 | 39,810.00 |
| Minimum Latency (ms) | 0.62 | 0.66 |
| Average Latency (ms) | 1.74 | 2.51 |
| Maximum Latency (ms) | 6.81 | 9.61 |
| 95th Percentile Latency (ms) | 2.18 | 3.55 |
MySQL SELECT (Random Ranges)
| Vultr – Cloud Compute (1 GB) | DigitalOcean – Regular (1 GB) | |
|---|---|---|
| Transactions per second | 6,416.00 | 4,240.00 |
| Queries per second | 64,160.00 | 42,400.00 |
| Minimum Latency (ms) | 0.47 | 0.76 |
| Average Latency (ms) | 1.56 | 2.35 |
| Maximum Latency (ms) | 4.83 | 6.72 |
| 95th Percentile Latency (ms) | 2 | 3.36 |
MySQL UPDATE (Indexed)
| Vultr – Cloud Compute (1 GB) | DigitalOcean – Regular (1 GB) | |
|---|---|---|
| Transactions per second | 8,258.00 | 5,672.00 |
| Queries per second | 82,580.00 | 56,720.00 |
| Minimum Latency (ms) | 0.72 | 0.73 |
| Average Latency (ms) | 1.21 | 1.76 |
| Maximum Latency (ms) | 35.33 | 15.81 |
| 95th Percentile Latency (ms) | 1.79 | 2.97 |
MySQL UPDATE (Non-Indexed)
| Vultr – Cloud Compute (1 GB) | DigitalOcean – Regular (1 GB) | |
|---|---|---|
| Transactions per second | 8,930.00 | 6,657.00 |
| Queries per second | 89,300.00 | 66,570.00 |
| Minimum Latency (ms) | 0.71 | 0.61 |
| Average Latency (ms) | 1.12 | 1.5 |
| Maximum Latency (ms) | 20.29 | 11.94 |
| 95th Percentile Latency (ms) | 1.39 | 2.3 |
MySQL DELETE
| Vultr – Cloud Compute (1 GB) | DigitalOcean – Regular (1 GB) | |
|---|---|---|
| Transactions per second | 50,174.00 | 57,603.00 |
| Queries per second | 501,740.00 | 576,030.00 |
| Minimum Latency (ms) | 0.07 | 0.04 |
| Average Latency (ms) | 0.2 | 0.17 |
| Maximum Latency (ms) | 18.49 | 18.88 |
| 95th Percentile Latency (ms) | 1.1 | 1.04 |
Redis
| Vultr – Cloud Compute (1 GB) | DigitalOcean – Regular (1 GB) | |
|---|---|---|
| PING_INLINE per Second | 36,643.46 | 36,496.35 |
| PING_MBULK per Second | 37,230.08 | 39,447.73 |
| SET per Second | 36,724.20 | 38,804.81 |
| GET per Second | 36,982.25 | 37,835.79 |
| INCR per Second | 36,941.26 | 38,491.14 |
| LPUSH per Second | 36,483.04 | 40,617.39 |
| RPUSH per Second | 37,091.99 | 35,893.75 |
| LPOP per Second | 36,643.46 | 37,664.79 |
| RPOP per Second | 36,764.71 | 38,774.72 |
| SADD per Second | 37,523.45 | 38,182.51 |
| HSET per Second | 36,995.93 | 34,352.46 |
| SPOP per Second | 37,565.74 | 34,246.57 |
| ZADD per Second | 37,009.62 | 36,954.91 |
| ZPOPMIN per Second | 34,916.20 | 40,338.84 |
| LRANGE_100 (first 100 elements) per Second | 23,557.13 | 20,593.08 |
| LRANGE_300 (first 300 elements) per Second | 12,960.08 | 8,546.28 |
| LRANGE_500 (first 500 elements) per Second | 9,176.00 | 5,492.39 |
| LRANGE_600 (first 600 elements) per Second | 7,776.65 | 5,337.03 |
| MSET (10 keys) per Second | 31,017.37 | 32,362.46 |
Redis Average Latency (ms)
| Vultr – Cloud Compute (1 GB) | DigitalOcean – Regular (1 GB) | |
|---|---|---|
| PING_INLINE | 0.89 | 0.91 |
| PING_MBULK | 0.88 | 0.84 |
| SET | 0.90 | 0.87 |
| GET | 0.89 | 0.88 |
| INCR | 0.89 | 0.87 |
| LPUSH | 0.91 | 0.83 |
| RPUSH | 0.89 | 0.93 |
| LPOP | 0.91 | 0.90 |
| RPOP | 0.90 | 0.87 |
| SADD | 0.88 | 0.88 |
| HSET | 0.89 | 0.97 |
| SPOP | 0.87 | 0.96 |
| ZADD | 0.90 | 0.91 |
| ZPOPMIN | 0.96 | 0.83 |
| LRANGE_100 (first 100 elements) | 1.40 | 1.75 |
| LRANGE_300 (first 300 elements) | 2.57 | 4.18 |
| LRANGE_500 (first 500 elements) | 3.74 | 6.48 |
| LRANGE_600 (first 600 elements) | 4.36 | 6.65 |
| MSET (10 keys) | 1.09 | 1.09 |
Conclusion
From the friendly robots:
After analyzing the benchmark results from both DigitalOcean's Regular (1 GB) and Vultr's Cloud Compute (1 GB) instances, it's clear that DigitalOcean's instance generally performs better in Redis benchmarks, with higher requests per second (rps) and lower average latencies across various operations, while Vultr's instance has marginally higher CPU events per second but shows slower Redis performance, particularly in LRANGE operations. DigitalOcean excels in MySQL OLTP benchmarks, demonstrating faster and more consistent performance. File I/O and memory operations also favor DigitalOcean slightly, suggesting it could be a better choice for CPU-intensive or I/O-heavy workloads. In contrast, Vultr's instance provides more throughput in file operations and could be a cost-effective option for scenarios where the emphasis is on read-heavy or large file operations. Considering these metrics, DigitalOcean's instance is recommended for applications prioritizing low latency and high throughput in CPU-intensive tasks, while Vultr's instance might be preferred for budget-conscious setups focused on file-based 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.