Vultr Cloud Compute (1 GB) vs. UpCloud Balanced (1 GB)
Fresh benchmarks coming at ya. Today I've spun up brand new instance from UpCloud and Vultr and did some benchmarking. All instances were spun up with Ubuntu 24.04 LTS x64 and were created in the New York area (or close to it). Time to see who showed up today.
Overview
| Vultr – Cloud Compute (1 GB) | UpCloud – Balanced (1 GB) | |
|---|---|---|
| Last Benchmarked | Tue, 28 Oct 2025 11:00:51 GMT | Fri, 31 Oct 2025 00:00:52 GMT |
| Linux Distro | Ubuntu 24.04 LTS x64 | Ubuntu 24.04 LTS x64 |
| Kernel Version | 6.8.0-79-generic | 6.8.0-63-generic |
| MySQL Version | 8.0.43-0ubuntu0.24.04.2 | 8.0.43-0ubuntu0.24.04.2 |
| Redis Version | 7.0.15 | 7.0.15 |
| Location | Newark, NJ | New York, NY |
| Monthly Price | $5.00 | €7.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) | UpCloud – Balanced (1 GB) | |
|---|---|---|
| Vendor | GenuineIntel | AuthenticAMD |
| Model Name | Intel Core Processor (Broadwell, no TSX, IBRS) | AMD EPYC 9575F 64-Core Processor |
| Clock Speed (MHz) | 2,394.45 | 3,295.42 |
| CPU Cache Size (KB) | 16,384.00 | 512.00 |
| BogoMips | 4,788.90 | 6,590.83 |
| Events per Second | 615.53 | 5,707.06 |
| Minimum Latency (ms) | 0.88 | 0.16 |
| Average Latency (ms) | 1.62 | 0.17 |
| Maximum Latency (ms) | 5.49 | 0.64 |
| 95th Percentile Latency (ms) | 2.61 | 0.19 |
Memory
Memory Read
| Vultr – Cloud Compute (1 GB) | UpCloud – Balanced (1 GB) | |
|---|---|---|
| Operations per second | 3,650,861.12 | 7,834,164.30 |
| Mebibytes per second | 3,565.29 | 7,650.55 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.86 | 0.23 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – Cloud Compute (1 GB) | UpCloud – Balanced (1 GB) | |
|---|---|---|
| Operations per second | 3,964,071.36 | 7,903,681.50 |
| Mebibytes per second | 3,871.16 | 7,718.44 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.65 | 0.36 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – Cloud Compute (1 GB) | UpCloud – Balanced (1 GB) | |
|---|---|---|
| Reads per Second | 1,335.03 | 3,730.38 |
| Writes per Second | 890.02 | 2,486.92 |
| Fsyncs per Second | 2,849.25 | 7,967.13 |
| Read Mebibytes per Second | 20.86 | 58.29 |
| Written Mebibytes per Second | 13.91 | 38.86 |
| Minimum Latency (ms) | 0.01 | 0 |
| Average Latency (ms) | 0.2 | 0.07 |
| Maximum Latency (ms) | 12 | 39.97 |
| 95th Percentile Latency (ms) | 0.51 | 0.23 |
Mutex
| Vultr – Cloud Compute (1 GB) | UpCloud – Balanced (1 GB) | |
|---|---|---|
| Minimum Latency (ms) | 2,016.43 | 1,153.85 |
| Average Latency (ms) | 2,026.59 | 1,162.70 |
| Maximum Latency (ms) | 2,036.58 | 1,168.80 |
| 95th Percentile Latency (ms) | 2,045.74 | 1,170.65 |
MySQL
MySQL Read-only
| Vultr – Cloud Compute (1 GB) | UpCloud – Balanced (1 GB) | |
|---|---|---|
| Transactions per second | 4,681.00 | 24,839.00 |
| Queries per second | 46,810.00 | 248,390.00 |
| Minimum Latency (ms) | 1.57 | 0.29 |
| Average Latency (ms) | 2.13 | 0.4 |
| Maximum Latency (ms) | 22.59 | 7.06 |
| 95th Percentile Latency (ms) | 3.75 | 0.56 |
MySQL Write-only
| Vultr – Cloud Compute (1 GB) | UpCloud – Balanced (1 GB) | |
|---|---|---|
| Transactions per second | 2,680.00 | 5,931.00 |
| Queries per second | 26,800.00 | 59,310.00 |
| Minimum Latency (ms) | 1.66 | 0.63 |
| Average Latency (ms) | 3.73 | 1.68 |
| Maximum Latency (ms) | 34.94 | 36.65 |
| 95th Percentile Latency (ms) | 6.67 | 3.25 |
MySQL Read/Write
| Vultr – Cloud Compute (1 GB) | UpCloud – Balanced (1 GB) | |
|---|---|---|
| Transactions per second | 1,752.00 | 4,502.00 |
| Queries per second | 17,520.00 | 45,020.00 |
| Minimum Latency (ms) | 4.22 | 1.09 |
| Average Latency (ms) | 5.71 | 2.22 |
| Maximum Latency (ms) | 16.45 | 49.58 |
| 95th Percentile Latency (ms) | 8.28 | 3.07 |
MySQL INSERT
| Vultr – Cloud Compute (1 GB) | UpCloud – Balanced (1 GB) | |
|---|---|---|
| Transactions per second | 4,351.00 | 7,380.00 |
| Queries per second | 43,510.00 | 73,800.00 |
| Minimum Latency (ms) | 1.34 | 0.5 |
| Average Latency (ms) | 2.29 | 1.35 |
| Maximum Latency (ms) | 26.21 | 119.93 |
| 95th Percentile Latency (ms) | 3.36 | 2.22 |
MySQL Bulk INSERT
| Vultr – Cloud Compute (1 GB) | UpCloud – Balanced (1 GB) | |
|---|---|---|
| Transactions per second | 865,805.00 | 2,977,717.00 |
| Queries per second | 8,658,050.00 | 29,777,170.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0 |
| Maximum Latency (ms) | 955.84 | 173.9 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – Cloud Compute (1 GB) | UpCloud – Balanced (1 GB) | |
|---|---|---|
| Transactions per second | 105,481.00 | 846,852.00 |
| Queries per second | 1,054,810.00 | 8,468,520.00 |
| Minimum Latency (ms) | 0.06 | 0.01 |
| Average Latency (ms) | 0.09 | 0.01 |
| Maximum Latency (ms) | 9.22 | 1.33 |
| 95th Percentile Latency (ms) | 0.16 | 0.02 |
MySQL SELECT (Random Points)
| Vultr – Cloud Compute (1 GB) | UpCloud – Balanced (1 GB) | |
|---|---|---|
| Transactions per second | 3,665.00 | 14,803.00 |
| Queries per second | 36,650.00 | 148,030.00 |
| Minimum Latency (ms) | 0.5 | 0.17 |
| Average Latency (ms) | 2.73 | 0.67 |
| Maximum Latency (ms) | 13.84 | 6.04 |
| 95th Percentile Latency (ms) | 5 | 0.97 |
MySQL SELECT (Random Ranges)
| Vultr – Cloud Compute (1 GB) | UpCloud – Balanced (1 GB) | |
|---|---|---|
| Transactions per second | 5,236.00 | 16,381.00 |
| Queries per second | 52,360.00 | 163,810.00 |
| Minimum Latency (ms) | 0.72 | 0.16 |
| Average Latency (ms) | 1.91 | 0.61 |
| Maximum Latency (ms) | 10.33 | 2.58 |
| 95th Percentile Latency (ms) | 2.76 | 0.97 |
MySQL UPDATE (Indexed)
| Vultr – Cloud Compute (1 GB) | UpCloud – Balanced (1 GB) | |
|---|---|---|
| Transactions per second | 4,511.00 | 8,491.00 |
| Queries per second | 45,110.00 | 84,910.00 |
| Minimum Latency (ms) | 1.26 | 0.47 |
| Average Latency (ms) | 2.21 | 1.18 |
| Maximum Latency (ms) | 14.93 | 44.18 |
| 95th Percentile Latency (ms) | 3.55 | 1.67 |
MySQL UPDATE (Non-Indexed)
| Vultr – Cloud Compute (1 GB) | UpCloud – Balanced (1 GB) | |
|---|---|---|
| Transactions per second | 5,148.00 | 8,500.00 |
| Queries per second | 51,480.00 | 85,000.00 |
| Minimum Latency (ms) | 1.25 | 0.46 |
| Average Latency (ms) | 1.94 | 1.18 |
| Maximum Latency (ms) | 19.95 | 35.43 |
| 95th Percentile Latency (ms) | 2.81 | 1.7 |
MySQL DELETE
| Vultr – Cloud Compute (1 GB) | UpCloud – Balanced (1 GB) | |
|---|---|---|
| Transactions per second | 19,636.00 | 289,704.00 |
| Queries per second | 196,360.00 | 2,897,040.00 |
| Minimum Latency (ms) | 0.08 | 0.01 |
| Average Latency (ms) | 0.51 | 0.03 |
| Maximum Latency (ms) | 33.94 | 56.6 |
| 95th Percentile Latency (ms) | 2.48 | 0.03 |
Redis
| Vultr – Cloud Compute (1 GB) | UpCloud – Balanced (1 GB) | |
|---|---|---|
| PING_INLINE per Second | 34,270.05 | 163,398.70 |
| PING_MBULK per Second | 34,638.03 | 170,357.75 |
| SET per Second | 35,211.27 | 163,666.12 |
| GET per Second | 34,977.27 | 154,559.50 |
| INCR per Second | 34,965.04 | 143,884.89 |
| LPUSH per Second | 36,443.15 | 154,083.20 |
| RPUSH per Second | 33,898.30 | 164,473.69 |
| LPOP per Second | 35,855.14 | 166,666.66 |
| RPOP per Second | 34,831.07 | 162,074.56 |
| SADD per Second | 35,829.45 | 171,232.88 |
| HSET per Second | 34,977.27 | 150,829.56 |
| SPOP per Second | 34,423.41 | 170,357.75 |
| ZADD per Second | 35,174.11 | 149,700.61 |
| ZPOPMIN per Second | 35,410.77 | 170,940.17 |
| LRANGE_100 (first 100 elements) per Second | 23,364.48 | 87,719.30 |
| LRANGE_300 (first 300 elements) per Second | 12,325.90 | 41,459.37 |
| LRANGE_500 (first 500 elements) per Second | 8,369.60 | 26,997.84 |
| LRANGE_600 (first 600 elements) per Second | 7,555.15 | 23,299.16 |
| MSET (10 keys) per Second | 33,123.55 | 138,696.25 |
Redis Average Latency (ms)
| Vultr – Cloud Compute (1 GB) | UpCloud – Balanced (1 GB) | |
|---|---|---|
| PING_INLINE | 0.96 | 0.20 |
| PING_MBULK | 0.92 | 0.19 |
| SET | 0.93 | 0.20 |
| GET | 0.94 | 0.22 |
| INCR | 0.92 | 0.23 |
| LPUSH | 0.92 | 0.22 |
| RPUSH | 0.95 | 0.21 |
| LPOP | 0.93 | 0.21 |
| RPOP | 0.93 | 0.21 |
| SADD | 0.92 | 0.20 |
| HSET | 0.93 | 0.22 |
| SPOP | 0.94 | 0.20 |
| ZADD | 0.93 | 0.23 |
| ZPOPMIN | 0.92 | 0.20 |
| LRANGE_100 (first 100 elements) | 1.43 | 0.41 |
| LRANGE_300 (first 300 elements) | 2.77 | 0.86 |
| LRANGE_500 (first 500 elements) | 4.07 | 1.33 |
| LRANGE_600 (first 600 elements) | 4.48 | 1.53 |
| MSET (10 keys) | 1.03 | 0.26 |
Conclusion
From the friendly robots:
After analyzing the benchmark results for both UpCloud's Balanced (1 GB) and Vultr's Cloud Compute (1 GB), it's clear that UpCloud's instance offers superior performance in most metrics, particularly in Redis operations where it achieves higher requests per second and lower latencies across various commands. UpCloud's CPU and memory benchmarks also show better performance with lower latencies and higher throughput. Vultr's instance, while competitive, lags behind in several benchmarks, especially in Redis LRANGE operations and MySQL OLTP tasks. Given these results, UpCloud's instance is better suited for CPU-intensive and I/O-heavy workloads, making it ideal for applications requiring high throughput and low latency, such as real-time data processing and high-performance databases. Vultr's instance, while still capable, may be better for more budget-conscious users or less demanding applications.
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 UpCloud and Vultr.
You can also support me directly by buying me a coffee.