UpCloud Balanced (1 GB) vs. Vultr Cloud Compute (2 GB, 2 Cores)
New day, new benchmarks. Today I've spun up brand new instance from UpCloud and Vultr to run some benchmarks on. All instances were running Ubuntu 24.04 LTS x64 and all resided in or around the New York / New Jersey area. Time to see who showed up today.
Overview
| UpCloud – Balanced (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Last Benchmarked | Sun, 10 May 2026 01:00:52 GMT | Mon, 11 May 2026 04:00:52 GMT |
| Linux Distro | Ubuntu 24.04 LTS x64 | Ubuntu 24.04 LTS x64 |
| Kernel Version | 6.8.0-111-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 | €7.00 | $15.00 |
| RAM (GB) | 1 | 2 |
| CPU Cores | 1 | 2 |
| Storage (TB) | 25 | 65 |
| Storage Type | SSD | SSD |
| Transfer (TB) | 1 | 3 |
CPU
| UpCloud – Balanced (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Vendor | AuthenticAMD | GenuineIntel |
| Model Name | AMD EPYC 9575F 64-Core Processor | Intel Core Processor (Skylake, IBRS, no TSX) |
| Clock Speed (MHz) | 3,295.48 | 3,792.00 |
| CPU Cache Size (KB) | 512.00 | 16,384.00 |
| BogoMips | 6,590.95 | 7,583.99 |
| Events per Second | 5,808.89 | 1,481.60 |
| Minimum Latency (ms) | 0.16 | 0.63 |
| Average Latency (ms) | 0.17 | 0.67 |
| Maximum Latency (ms) | 0.91 | 1.95 |
| 95th Percentile Latency (ms) | 0.19 | 0.77 |
Memory
Memory Read
| UpCloud – Balanced (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 8,147,464.61 | 6,401,389.08 |
| Mebibytes per second | 7,956.51 | 6,251.36 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.25 | 0.23 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| UpCloud – Balanced (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 8,246,922.71 | 6,411,085.35 |
| Mebibytes per second | 8,053.64 | 6,260.83 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.24 | 0.18 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| UpCloud – Balanced (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Reads per Second | 5,159.90 | 4,345.71 |
| Writes per Second | 3,439.93 | 2,897.07 |
| Fsyncs per Second | 11,013.54 | 9,273.19 |
| Read Mebibytes per Second | 80.62 | 67.90 |
| Written Mebibytes per Second | 53.75 | 45.27 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.05 | 0.06 |
| Maximum Latency (ms) | 52.17 | 2.92 |
| 95th Percentile Latency (ms) | 0.18 | 0.17 |
Mutex
| UpCloud – Balanced (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 1,201.12 | 214.63 |
| Average Latency (ms) | 1,206.08 | 569.72 |
| Maximum Latency (ms) | 1,210.41 | 636.55 |
| 95th Percentile Latency (ms) | 1,213.57 | 634.66 |
MySQL
MySQL Read-only
| UpCloud – Balanced (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 28,978.00 | 8,015.00 |
| Queries per second | 289,780.00 | 80,150.00 |
| Minimum Latency (ms) | 0.27 | 0.92 |
| Average Latency (ms) | 0.34 | 1.25 |
| Maximum Latency (ms) | 6.69 | 5.5 |
| 95th Percentile Latency (ms) | 0.48 | 1.86 |
MySQL Write-only
| UpCloud – Balanced (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 10,035.00 | 8,497.00 |
| Queries per second | 100,350.00 | 84,970.00 |
| Minimum Latency (ms) | 0.47 | 0.76 |
| Average Latency (ms) | 1 | 1.17 |
| Maximum Latency (ms) | 30.82 | 3.04 |
| 95th Percentile Latency (ms) | 1.44 | 1.55 |
MySQL Read/Write
| UpCloud – Balanced (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 6,060.00 | 3,726.00 |
| Queries per second | 60,600.00 | 37,260.00 |
| Minimum Latency (ms) | 0.99 | 1.78 |
| Average Latency (ms) | 1.65 | 2.68 |
| Maximum Latency (ms) | 39.94 | 5.82 |
| 95th Percentile Latency (ms) | 2.48 | 3.43 |
MySQL INSERT
| UpCloud – Balanced (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 13,060.00 | 15,028.00 |
| Queries per second | 130,600.00 | 150,280.00 |
| Minimum Latency (ms) | 0.34 | 0.41 |
| Average Latency (ms) | 0.76 | 0.66 |
| Maximum Latency (ms) | 25.82 | 2.42 |
| 95th Percentile Latency (ms) | 1.04 | 0.86 |
MySQL Bulk INSERT
| UpCloud – Balanced (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 3,521,146.00 | 1,696,217.00 |
| Queries per second | 35,211,460.00 | 16,962,170.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0.01 |
| Maximum Latency (ms) | 160.29 | 283.37 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| UpCloud – Balanced (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 976,863.00 | 201,989.00 |
| Queries per second | 9,768,630.00 | 2,019,890.00 |
| Minimum Latency (ms) | 0.01 | 0.03 |
| Average Latency (ms) | 0.01 | 0.05 |
| Maximum Latency (ms) | 4.28 | 0.51 |
| 95th Percentile Latency (ms) | 0.01 | 0.07 |
MySQL SELECT (Random Points)
| UpCloud – Balanced (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 19,152.00 | 8,025.00 |
| Queries per second | 191,520.00 | 80,250.00 |
| Minimum Latency (ms) | 0.15 | 0.35 |
| Average Latency (ms) | 0.52 | 1.24 |
| Maximum Latency (ms) | 6.07 | 3.55 |
| 95th Percentile Latency (ms) | 0.75 | 2.07 |
MySQL SELECT (Random Ranges)
| UpCloud – Balanced (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 19,009.00 | 8,336.00 |
| Queries per second | 190,090.00 | 83,360.00 |
| Minimum Latency (ms) | 0.14 | 0.4 |
| Average Latency (ms) | 0.53 | 1.2 |
| Maximum Latency (ms) | 5.22 | 4.25 |
| 95th Percentile Latency (ms) | 0.87 | 2.22 |
MySQL UPDATE (Indexed)
| UpCloud – Balanced (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 12,488.00 | 13,858.00 |
| Queries per second | 124,880.00 | 138,580.00 |
| Minimum Latency (ms) | 0.35 | 0.42 |
| Average Latency (ms) | 0.8 | 0.72 |
| Maximum Latency (ms) | 21.25 | 6.33 |
| 95th Percentile Latency (ms) | 1.25 | 0.95 |
MySQL UPDATE (Non-Indexed)
| UpCloud – Balanced (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 13,276.00 | 14,587.00 |
| Queries per second | 132,760.00 | 145,870.00 |
| Minimum Latency (ms) | 0.36 | 0.4 |
| Average Latency (ms) | 0.75 | 0.68 |
| Maximum Latency (ms) | 19.77 | 11.69 |
| 95th Percentile Latency (ms) | 1.04 | 0.9 |
MySQL DELETE
| UpCloud – Balanced (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 506,633.00 | 129,013.00 |
| Queries per second | 5,066,330.00 | 1,290,130.00 |
| Minimum Latency (ms) | 0.01 | 0.03 |
| Average Latency (ms) | 0.02 | 0.08 |
| Maximum Latency (ms) | 18.52 | 2.61 |
| 95th Percentile Latency (ms) | 0.02 | 0.09 |
Redis
| UpCloud – Balanced (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE per Second | 180,831.83 | 78,247.26 |
| PING_MBULK per Second | 192,307.70 | 74,738.41 |
| SET per Second | 181,818.17 | 77,041.60 |
| GET per Second | 189,035.92 | 83,333.33 |
| INCR per Second | 182,815.36 | 80,971.66 |
| LPUSH per Second | 185,185.17 | 79,113.92 |
| RPUSH per Second | 175,131.36 | 77,160.49 |
| LPOP per Second | 188,323.91 | 81,499.59 |
| RPOP per Second | 180,505.41 | 82,440.23 |
| SADD per Second | 187,617.27 | 80,192.46 |
| HSET per Second | 184,162.06 | 83,612.04 |
| SPOP per Second | 184,842.88 | 85,034.02 |
| ZADD per Second | 176,056.33 | 83,263.95 |
| ZPOPMIN per Second | 176,991.16 | 82,987.55 |
| LRANGE_100 (first 100 elements) per Second | 98,135.42 | 55,555.56 |
| LRANGE_300 (first 300 elements) per Second | 47,641.73 | 28,851.70 |
| LRANGE_500 (first 500 elements) per Second | 31,938.68 | 19,391.12 |
| LRANGE_600 (first 600 elements) per Second | 24,875.62 | 17,211.71 |
| MSET (10 keys) per Second | 163,934.42 | 80,256.82 |
Redis Average Latency (ms)
| UpCloud – Balanced (1 GB) | Vultr – Cloud Compute (2 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE | 0.18 | 0.34 |
| PING_MBULK | 0.17 | 0.35 |
| SET | 0.18 | 0.34 |
| GET | 0.17 | 0.32 |
| INCR | 0.18 | 0.32 |
| LPUSH | 0.18 | 0.34 |
| RPUSH | 0.19 | 0.34 |
| LPOP | 0.18 | 0.32 |
| RPOP | 0.19 | 0.32 |
| SADD | 0.18 | 0.32 |
| HSET | 0.18 | 0.31 |
| SPOP | 0.18 | 0.30 |
| ZADD | 0.19 | 0.31 |
| ZPOPMIN | 0.19 | 0.31 |
| LRANGE_100 (first 100 elements) | 0.37 | 0.54 |
| LRANGE_300 (first 300 elements) | 0.76 | 1.11 |
| LRANGE_500 (first 500 elements) | 1.13 | 1.62 |
| LRANGE_600 (first 600 elements) | 1.39 | 1.84 |
| MSET (10 keys) | 0.22 | 0.38 |
Conclusion
From the friendly robots:
Comparing the benchmarks of the two instances, UpCloud's Balanced (1 GB) instance demonstrates higher Redis throughput and lower latency across various operations, suggesting superior performance for memory-intensive and latency-sensitive applications such as real-time analytics and caching services. The Vultr Cloud Compute (2 GB, 2 Cores) instance, while having lower average latency in Redis operations, shows more variability and higher maximum latency, which might be acceptable for less demanding applications. The Vultr instance also excels in CPU-intensive tasks with more cores and slightly higher CPU MHz, making it suitable for workloads that benefit from parallel processing, such as batch processing and virtual machine hosting. Additionally, the file I/O performance of the Vultr instance is also slightly better in terms of throughput, which is beneficial for applications involving frequent read/write operations. Therefore, UpCloud's instance is ideal for applications requiring low-latency, high-throughput memory operations, while Vultr's instance is better for CPU-intensive and high-throughput I/O workloads.
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.