Vultr Cloud Compute (2 GB, 2 Cores) vs. Vultr High Performance Intel (4 GB, 2 Cores)
New day, new benchmarks. Today I've spun up brand new instance from Vultr and ran my world famous suite of benchmarking scripts. Each instance was running Ubuntu 24.04 LTS x64 and all resided in or around the New York / New Jersey area. Enough talk. Here's the data.
Overview
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Last Benchmarked | Mon, 11 May 2026 04:00:52 GMT | Sun, 10 May 2026 18: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 | $24.00 |
| RAM (GB) | 2 | 4 |
| CPU Cores | 2 | 2 |
| Storage (TB) | 65 | 100 |
| Storage Type | SSD | NVMe |
| Transfer (TB) | 3 | 5 |
CPU
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Vendor | GenuineIntel | GenuineIntel |
| Model Name | Intel Core Processor (Skylake, IBRS, no TSX) | Intel Xeon Processor (Cascadelake) |
| Clock Speed (MHz) | 3,792.00 | 2,893.17 |
| CPU Cache Size (KB) | 16,384.00 | 16,384.00 |
| BogoMips | 7,583.99 | 5,786.33 |
| Events per Second | 1,481.60 | 1,132.36 |
| Minimum Latency (ms) | 0.63 | 0.83 |
| Average Latency (ms) | 0.67 | 0.88 |
| Maximum Latency (ms) | 1.95 | 1.65 |
| 95th Percentile Latency (ms) | 0.77 | 1.04 |
Memory
Memory Read
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 6,401,389.08 | 5,331,977.06 |
| Mebibytes per second | 6,251.36 | 5,207.01 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.23 | 0.73 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 6,411,085.35 | 5,164,671.77 |
| Mebibytes per second | 6,260.83 | 5,043.62 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.18 | 0.66 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Reads per Second | 4,345.71 | 6,043.23 |
| Writes per Second | 2,897.07 | 4,028.82 |
| Fsyncs per Second | 9,273.19 | 12,894.52 |
| Read Mebibytes per Second | 67.90 | 94.43 |
| Written Mebibytes per Second | 45.27 | 62.95 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.06 | 0.04 |
| Maximum Latency (ms) | 2.92 | 3.84 |
| 95th Percentile Latency (ms) | 0.17 | 0.14 |
Mutex
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 214.63 | 322.02 |
| Average Latency (ms) | 569.72 | 806.81 |
| Maximum Latency (ms) | 636.55 | 874.99 |
| 95th Percentile Latency (ms) | 634.66 | 877.61 |
MySQL
MySQL Read-only
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,015.00 | 6,312.00 |
| Queries per second | 80,150.00 | 63,120.00 |
| Minimum Latency (ms) | 0.92 | 1.13 |
| Average Latency (ms) | 1.25 | 1.58 |
| Maximum Latency (ms) | 5.5 | 10.5 |
| 95th Percentile Latency (ms) | 1.86 | 2.22 |
MySQL Write-only
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,497.00 | 7,529.00 |
| Queries per second | 84,970.00 | 75,290.00 |
| Minimum Latency (ms) | 0.76 | 0.87 |
| Average Latency (ms) | 1.17 | 1.33 |
| Maximum Latency (ms) | 3.04 | 4.16 |
| 95th Percentile Latency (ms) | 1.55 | 1.89 |
MySQL Read/Write
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 3,726.00 | 2,596.00 |
| Queries per second | 37,260.00 | 25,960.00 |
| Minimum Latency (ms) | 1.78 | 2.37 |
| Average Latency (ms) | 2.68 | 3.85 |
| Maximum Latency (ms) | 5.82 | 18 |
| 95th Percentile Latency (ms) | 3.43 | 5.37 |
MySQL INSERT
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 15,028.00 | 10,595.00 |
| Queries per second | 150,280.00 | 105,950.00 |
| Minimum Latency (ms) | 0.41 | 0.48 |
| Average Latency (ms) | 0.66 | 0.94 |
| Maximum Latency (ms) | 2.42 | 6.55 |
| 95th Percentile Latency (ms) | 0.86 | 1.34 |
MySQL Bulk INSERT
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 1,696,217.00 | 1,315,784.00 |
| Queries per second | 16,962,170.00 | 13,157,840.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0.01 |
| Maximum Latency (ms) | 283.37 | 385.72 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 201,989.00 | 172,759.00 |
| Queries per second | 2,019,890.00 | 1,727,590.00 |
| Minimum Latency (ms) | 0.03 | 0.03 |
| Average Latency (ms) | 0.05 | 0.06 |
| Maximum Latency (ms) | 0.51 | 1.93 |
| 95th Percentile Latency (ms) | 0.07 | 0.09 |
MySQL SELECT (Random Points)
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,025.00 | 5,975.00 |
| Queries per second | 80,250.00 | 59,750.00 |
| Minimum Latency (ms) | 0.35 | 0.52 |
| Average Latency (ms) | 1.24 | 1.67 |
| Maximum Latency (ms) | 3.55 | 7.14 |
| 95th Percentile Latency (ms) | 2.07 | 2.3 |
MySQL SELECT (Random Ranges)
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,336.00 | 6,837.00 |
| Queries per second | 83,360.00 | 68,370.00 |
| Minimum Latency (ms) | 0.4 | 0.52 |
| Average Latency (ms) | 1.2 | 1.46 |
| Maximum Latency (ms) | 4.25 | 3.8 |
| 95th Percentile Latency (ms) | 2.22 | 2.07 |
MySQL UPDATE (Indexed)
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 13,858.00 | 9,797.00 |
| Queries per second | 138,580.00 | 97,970.00 |
| Minimum Latency (ms) | 0.42 | 0.48 |
| Average Latency (ms) | 0.72 | 1.02 |
| Maximum Latency (ms) | 6.33 | 6.5 |
| 95th Percentile Latency (ms) | 0.95 | 1.55 |
MySQL UPDATE (Non-Indexed)
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 14,587.00 | 12,322.00 |
| Queries per second | 145,870.00 | 123,220.00 |
| Minimum Latency (ms) | 0.4 | 0.43 |
| Average Latency (ms) | 0.68 | 0.81 |
| Maximum Latency (ms) | 11.69 | 3.65 |
| 95th Percentile Latency (ms) | 0.9 | 1.12 |
MySQL DELETE
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 129,013.00 | 97,102.00 |
| Queries per second | 1,290,130.00 | 971,020.00 |
| Minimum Latency (ms) | 0.03 | 0.04 |
| Average Latency (ms) | 0.08 | 0.1 |
| Maximum Latency (ms) | 2.61 | 17.96 |
| 95th Percentile Latency (ms) | 0.09 | 0.17 |
Redis
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE per Second | 78,247.26 | 61,500.61 |
| PING_MBULK per Second | 74,738.41 | 56,274.62 |
| SET per Second | 77,041.60 | 57,736.72 |
| GET per Second | 83,333.33 | 59,031.88 |
| INCR per Second | 80,971.66 | 58,997.05 |
| LPUSH per Second | 79,113.92 | 58,038.30 |
| RPUSH per Second | 77,160.49 | 61,349.70 |
| LPOP per Second | 81,499.59 | 61,842.92 |
| RPOP per Second | 82,440.23 | 58,445.36 |
| SADD per Second | 80,192.46 | 52,219.32 |
| HSET per Second | 83,612.04 | 53,050.40 |
| SPOP per Second | 85,034.02 | 61,199.51 |
| ZADD per Second | 83,263.95 | 59,136.61 |
| ZPOPMIN per Second | 82,987.55 | 59,916.12 |
| LRANGE_100 (first 100 elements) per Second | 55,555.56 | 45,024.77 |
| LRANGE_300 (first 300 elements) per Second | 28,851.70 | 24,295.43 |
| LRANGE_500 (first 500 elements) per Second | 19,391.12 | 16,326.53 |
| LRANGE_600 (first 600 elements) per Second | 17,211.71 | 13,991.88 |
| MSET (10 keys) per Second | 80,256.82 | 58,275.06 |
Redis Average Latency (ms)
| Vultr – Cloud Compute (2 GB, 2 Cores) | Vultr – High Performance Intel (4 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE | 0.34 | 0.43 |
| PING_MBULK | 0.35 | 0.46 |
| SET | 0.34 | 0.45 |
| GET | 0.32 | 0.44 |
| INCR | 0.32 | 0.44 |
| LPUSH | 0.34 | 0.45 |
| RPUSH | 0.34 | 0.43 |
| LPOP | 0.32 | 0.43 |
| RPOP | 0.32 | 0.46 |
| SADD | 0.32 | 0.52 |
| HSET | 0.31 | 0.49 |
| SPOP | 0.30 | 0.43 |
| ZADD | 0.31 | 0.46 |
| ZPOPMIN | 0.31 | 0.44 |
| LRANGE_100 (first 100 elements) | 0.54 | 0.62 |
| LRANGE_300 (first 300 elements) | 1.11 | 1.19 |
| LRANGE_500 (first 500 elements) | 1.62 | 1.83 |
| LRANGE_600 (first 600 elements) | 1.84 | 2.23 |
| MSET (10 keys) | 0.38 | 0.51 |
Conclusion
From the friendly robots:
The Vultr Cloud Compute instance (2 GB, 2 Cores) demonstrated strong performance with high request rates and low latencies for Redis operations like PING, SET, GET, INCR, and others, excelling in memory operations and having respectable file I/O and CPU performance. The High Performance Intel (4 GB, 2 Cores) instance, while offering more RAM and faster CPU speeds, showed slightly lower request rates and higher latencies for Redis operations, but it exhibited better throughput in file I/O tasks and slightly better performance in MySQL OLTP operations. Given these metrics, the Cloud Compute instance is ideal for applications requiring high throughput and low latency for in-memory data store operations, whereas the High Performance Intel instance is better suited for workloads that benefit from higher RAM, faster CPUs, and better disk I/O performance, such as complex database operations and I/O-heavy 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.