Vultr Cloud Compute (2 GB, 2 Cores) vs. Vultr High Performance Intel (1 GB)
My friend, I'm so glad you're here! Today I've spun up brand new instance from Vultr and ran some benchmarks. All instances were running Ubuntu 24.04 LTS x64 and were created in or around the New York / New Jersey area. Time to see who showed up today.
Overview
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Last Benchmarked | Mon, 11 May 2026 04:00:52 GMT | Tue, 12 May 2026 02: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 | Newark, NJ | Newark, NJ |
| Monthly Price | $15.00 | $6.00 |
| RAM (GB) | 2 | 1 |
| CPU Cores | 2 | 1 |
| Storage (TB) | 65 | 25 |
| Storage Type | SSD | NVMe |
| Transfer (TB) | 3 | 2 |
CPU
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Vendor | GenuineIntel | GenuineIntel |
| Model Name | Intel Core Processor (Skylake, IBRS, no TSX) | Intel Xeon Processor (Cascadelake) |
| Clock Speed (MHz) | 3,792.00 | 2,992.97 |
| CPU Cache Size (KB) | 16,384.00 | 16,384.00 |
| BogoMips | 7,583.99 | 5,985.94 |
| Events per Second | 1,481.60 | 1,189.15 |
| Minimum Latency (ms) | 0.63 | 0.81 |
| Average Latency (ms) | 0.67 | 0.84 |
| Maximum Latency (ms) | 1.95 | 2.47 |
| 95th Percentile Latency (ms) | 0.77 | 0.95 |
Memory
Memory Read
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Operations per second | 6,401,389.08 | 5,526,233.85 |
| Mebibytes per second | 6,251.36 | 5,396.71 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.23 | 1.06 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Operations per second | 6,411,085.35 | 5,497,468.92 |
| Mebibytes per second | 6,260.83 | 5,368.62 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.18 | 0.88 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Reads per Second | 4,345.71 | 4,359.61 |
| Writes per Second | 2,897.07 | 2,906.41 |
| Fsyncs per Second | 9,273.19 | 9,311.70 |
| Read Mebibytes per Second | 67.90 | 68.12 |
| Written Mebibytes per Second | 45.27 | 45.41 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.06 | 0.06 |
| Maximum Latency (ms) | 2.92 | 18.46 |
| 95th Percentile Latency (ms) | 0.17 | 0.18 |
Mutex
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Minimum Latency (ms) | 214.63 | 1,494.72 |
| Average Latency (ms) | 569.72 | 1,505.74 |
| Maximum Latency (ms) | 636.55 | 1,513.45 |
| 95th Percentile Latency (ms) | 634.66 | 1,506.29 |
MySQL
MySQL Read-only
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 8,015.00 | 8,686.00 |
| Queries per second | 80,150.00 | 86,860.00 |
| Minimum Latency (ms) | 0.92 | 1.05 |
| Average Latency (ms) | 1.25 | 1.15 |
| Maximum Latency (ms) | 5.5 | 8.54 |
| 95th Percentile Latency (ms) | 1.86 | 1.32 |
MySQL Write-only
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 8,497.00 | 9,029.00 |
| Queries per second | 84,970.00 | 90,290.00 |
| Minimum Latency (ms) | 0.76 | 0.75 |
| Average Latency (ms) | 1.17 | 1.11 |
| Maximum Latency (ms) | 3.04 | 6.01 |
| 95th Percentile Latency (ms) | 1.55 | 1.55 |
MySQL Read/Write
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 3,726.00 | 3,603.00 |
| Queries per second | 37,260.00 | 36,030.00 |
| Minimum Latency (ms) | 1.78 | 2.16 |
| Average Latency (ms) | 2.68 | 2.77 |
| Maximum Latency (ms) | 5.82 | 8.09 |
| 95th Percentile Latency (ms) | 3.43 | 3.43 |
MySQL INSERT
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 15,028.00 | 17,017.00 |
| Queries per second | 150,280.00 | 170,170.00 |
| Minimum Latency (ms) | 0.41 | 0.41 |
| Average Latency (ms) | 0.66 | 0.58 |
| Maximum Latency (ms) | 2.42 | 2.87 |
| 95th Percentile Latency (ms) | 0.86 | 0.75 |
MySQL Bulk INSERT
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 1,696,217.00 | 1,317,592.00 |
| Queries per second | 16,962,170.00 | 13,175,920.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0.01 |
| Maximum Latency (ms) | 283.37 | 398.08 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 201,989.00 | 229,474.00 |
| Queries per second | 2,019,890.00 | 2,294,740.00 |
| Minimum Latency (ms) | 0.03 | 0.04 |
| Average Latency (ms) | 0.05 | 0.04 |
| Maximum Latency (ms) | 0.51 | 5.67 |
| 95th Percentile Latency (ms) | 0.07 | 0.06 |
MySQL SELECT (Random Points)
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 8,025.00 | 6,884.00 |
| Queries per second | 80,250.00 | 68,840.00 |
| Minimum Latency (ms) | 0.35 | 0.46 |
| Average Latency (ms) | 1.24 | 1.45 |
| Maximum Latency (ms) | 3.55 | 5.12 |
| 95th Percentile Latency (ms) | 2.07 | 1.89 |
MySQL SELECT (Random Ranges)
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 8,336.00 | 8,214.00 |
| Queries per second | 83,360.00 | 82,140.00 |
| Minimum Latency (ms) | 0.4 | 0.43 |
| Average Latency (ms) | 1.2 | 1.22 |
| Maximum Latency (ms) | 4.25 | 3.8 |
| 95th Percentile Latency (ms) | 2.22 | 1.58 |
MySQL UPDATE (Indexed)
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 13,858.00 | 15,965.00 |
| Queries per second | 138,580.00 | 159,650.00 |
| Minimum Latency (ms) | 0.42 | 0.42 |
| Average Latency (ms) | 0.72 | 0.62 |
| Maximum Latency (ms) | 6.33 | 3.1 |
| 95th Percentile Latency (ms) | 0.95 | 0.94 |
MySQL UPDATE (Non-Indexed)
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 14,587.00 | 16,573.00 |
| Queries per second | 145,870.00 | 165,730.00 |
| Minimum Latency (ms) | 0.4 | 0.41 |
| Average Latency (ms) | 0.68 | 0.6 |
| Maximum Latency (ms) | 11.69 | 7.54 |
| 95th Percentile Latency (ms) | 0.9 | 0.81 |
MySQL DELETE
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| Transactions per second | 129,013.00 | 138,973.00 |
| Queries per second | 1,290,130.00 | 1,389,730.00 |
| Minimum Latency (ms) | 0.03 | 0.04 |
| Average Latency (ms) | 0.08 | 0.07 |
| Maximum Latency (ms) | 2.61 | 4.78 |
| 95th Percentile Latency (ms) | 0.09 | 0.12 |
Redis
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| PING_INLINE per Second | 78,247.26 | 50,403.23 |
| PING_MBULK per Second | 74,738.41 | 50,530.57 |
| SET per Second | 77,041.60 | 48,947.62 |
| GET per Second | 83,333.33 | 48,638.13 |
| INCR per Second | 80,971.66 | 48,899.75 |
| LPUSH per Second | 79,113.92 | 49,529.47 |
| RPUSH per Second | 77,160.49 | 48,923.68 |
| LPOP per Second | 81,499.59 | 48,192.77 |
| RPOP per Second | 82,440.23 | 47,505.94 |
| SADD per Second | 80,192.46 | 49,701.79 |
| HSET per Second | 83,612.04 | 49,043.65 |
| SPOP per Second | 85,034.02 | 49,925.11 |
| ZADD per Second | 83,263.95 | 49,504.95 |
| ZPOPMIN per Second | 82,987.55 | 50,075.11 |
| LRANGE_100 (first 100 elements) per Second | 55,555.56 | 31,250.00 |
| LRANGE_300 (first 300 elements) per Second | 28,851.70 | 16,220.60 |
| LRANGE_500 (first 500 elements) per Second | 19,391.12 | 10,592.10 |
| LRANGE_600 (first 600 elements) per Second | 17,211.71 | 9,463.42 |
| MSET (10 keys) per Second | 80,256.82 | 45,330.91 |
Redis Average Latency (ms)
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (1 GB) | |
|---|---|---|
| PING_INLINE | 0.34 | 0.66 |
| PING_MBULK | 0.35 | 0.66 |
| SET | 0.34 | 0.68 |
| GET | 0.32 | 0.68 |
| INCR | 0.32 | 0.68 |
| LPUSH | 0.34 | 0.68 |
| RPUSH | 0.34 | 0.68 |
| LPOP | 0.32 | 0.70 |
| RPOP | 0.32 | 0.71 |
| SADD | 0.32 | 0.67 |
| HSET | 0.31 | 0.69 |
| SPOP | 0.30 | 0.67 |
| ZADD | 0.31 | 0.69 |
| ZPOPMIN | 0.31 | 0.67 |
| LRANGE_100 (first 100 elements) | 0.54 | 1.11 |
| LRANGE_300 (first 300 elements) | 1.11 | 2.22 |
| LRANGE_500 (first 500 elements) | 1.62 | 3.36 |
| LRANGE_600 (first 600 elements) | 1.84 | 3.75 |
| MSET (10 keys) | 0.38 | 0.76 |
Conclusion
From the friendly robots:
Both VPS instances from Vultr showcase solid performance but cater to different needs based on their benchmark results. The "Cloud Compute (2 GB, 2 Cores)" instance excels in handling a broader range of operations, including CPU-intensive tasks, memory operations, and I/O tasks, with notably high RPS rates in Redis benchmarks and efficient file I/O operations. Conversely, the "High Performance Intel (1 GB)" instance, despite having fewer resources, leverages its more powerful Intel Xeon processor to achieve high Redis throughput and low latency, making it an excellent choice for workloads that benefit from higher CPU performance per core. Thus, the former is better for general-purpose, moderately demanding applications, while the latter shines in scenarios requiring top-tier CPU performance, such as high-end web servers or specialized compute tasks.
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 link for Vultr.
You can also support me directly by buying me a coffee.