Vultr Cloud Compute (1 GB) vs. Vultr High Frequency Intel (2 GB, 2 Cores)
New day, new benchmarks. Today I've spun up brand new instance from Vultr and ran some benchmarks. Each instance was running Ubuntu 24.04 LTS x64 and were created in or around the New York / New Jersey area. Let's get into the numbers.
Overview
| Vultr – Cloud Compute (1 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Last Benchmarked | Sun, 31 May 2026 04:00:52 GMT | Sun, 31 May 2026 13:00:55 GMT |
| Linux Distro | Ubuntu 24.04 LTS x64 | Ubuntu 24.04 LTS x64 |
| Kernel Version | 6.8.0-117-generic | 6.8.0-117-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 | $5.00 | $18.00 |
| RAM (GB) | 1 | 2 |
| CPU Cores | 1 | 2 |
| Storage (TB) | 25 | 80 |
| Storage Type | SSD | NVMe |
| Transfer (TB) | 1 | 3 |
CPU
| Vultr – Cloud Compute (1 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Vendor | GenuineIntel | GenuineIntel |
| Model Name | Intel Core Processor (Broadwell, no TSX, IBRS) | Intel Core Processor (Skylake, IBRS, no TSX) |
| Clock Speed (MHz) | 2,394.45 | 3,791.98 |
| CPU Cache Size (KB) | 16,384.00 | 16,384.00 |
| BogoMips | 4,788.90 | 7,583.95 |
| Events per Second | 855.89 | 1,552.05 |
| Minimum Latency (ms) | 1.14 | 0.62 |
| Average Latency (ms) | 1.17 | 0.64 |
| Maximum Latency (ms) | 3.26 | 4.61 |
| 95th Percentile Latency (ms) | 1.23 | 0.69 |
Memory
Memory Read
| Vultr – Cloud Compute (1 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 4,208,440.85 | 7,875,668.83 |
| Mebibytes per second | 4,109.81 | 7,691.08 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.66 | 0.12 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – Cloud Compute (1 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 4,198,602.47 | 7,729,812.11 |
| Mebibytes per second | 4,100.20 | 7,548.64 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.23 | 0.16 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – Cloud Compute (1 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Reads per Second | 2,511.60 | 4,671.85 |
| Writes per Second | 1,674.40 | 3,114.56 |
| Fsyncs per Second | 5,361.38 | 9,976.90 |
| Read Mebibytes per Second | 39.24 | 73.00 |
| Written Mebibytes per Second | 26.16 | 48.67 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.1 | 0.06 |
| Maximum Latency (ms) | 2.8 | 2.76 |
| 95th Percentile Latency (ms) | 0.3 | 0.17 |
Mutex
| Vultr – Cloud Compute (1 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 1,985.30 | 543.27 |
| Average Latency (ms) | 1,990.99 | 554.74 |
| Maximum Latency (ms) | 1,996.19 | 563.70 |
| 95th Percentile Latency (ms) | 2,009.23 | 559.50 |
MySQL
MySQL Read-only
| Vultr – Cloud Compute (1 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 5,210.00 | 10,621.00 |
| Queries per second | 52,100.00 | 106,210.00 |
| Minimum Latency (ms) | 1.74 | 0.86 |
| Average Latency (ms) | 1.92 | 0.94 |
| Maximum Latency (ms) | 13.29 | 2.5 |
| 95th Percentile Latency (ms) | 2 | 1.03 |
MySQL Write-only
| Vultr – Cloud Compute (1 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 5,112.00 | 10,229.00 |
| Queries per second | 51,120.00 | 102,290.00 |
| Minimum Latency (ms) | 1.46 | 0.64 |
| Average Latency (ms) | 1.95 | 0.98 |
| Maximum Latency (ms) | 7.48 | 2.08 |
| 95th Percentile Latency (ms) | 2.48 | 1.23 |
MySQL Read/Write
| Vultr – Cloud Compute (1 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 2,334.00 | 5,072.00 |
| Queries per second | 23,340.00 | 50,720.00 |
| Minimum Latency (ms) | 3.59 | 1.59 |
| Average Latency (ms) | 4.28 | 1.97 |
| Maximum Latency (ms) | 13.2 | 3.94 |
| 95th Percentile Latency (ms) | 5.09 | 2.39 |
MySQL INSERT
| Vultr – Cloud Compute (1 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 9,427.00 | 16,038.00 |
| Queries per second | 94,270.00 | 160,380.00 |
| Minimum Latency (ms) | 0.71 | 0.38 |
| Average Latency (ms) | 1.06 | 0.62 |
| Maximum Latency (ms) | 5.65 | 13.18 |
| 95th Percentile Latency (ms) | 1.3 | 0.8 |
MySQL Bulk INSERT
| Vultr – Cloud Compute (1 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 1,026,342.00 | 2,424,342.00 |
| Queries per second | 10,263,420.00 | 24,243,420.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.01 | 0 |
| Maximum Latency (ms) | 502.73 | 205.81 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – Cloud Compute (1 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 117,078.00 | 241,313.00 |
| Queries per second | 1,170,780.00 | 2,413,130.00 |
| Minimum Latency (ms) | 0.07 | 0.03 |
| Average Latency (ms) | 0.08 | 0.04 |
| Maximum Latency (ms) | 7.15 | 0.76 |
| 95th Percentile Latency (ms) | 0.12 | 0.05 |
MySQL SELECT (Random Points)
| Vultr – Cloud Compute (1 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 5,768.00 | 12,080.00 |
| Queries per second | 57,680.00 | 120,800.00 |
| Minimum Latency (ms) | 0.58 | 0.21 |
| Average Latency (ms) | 1.73 | 0.83 |
| Maximum Latency (ms) | 5.37 | 3.31 |
| 95th Percentile Latency (ms) | 2.22 | 1.04 |
MySQL SELECT (Random Ranges)
| Vultr – Cloud Compute (1 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 6,308.00 | 10,527.00 |
| Queries per second | 63,080.00 | 105,270.00 |
| Minimum Latency (ms) | 0.36 | 0.16 |
| Average Latency (ms) | 1.58 | 0.95 |
| Maximum Latency (ms) | 3.56 | 3.25 |
| 95th Percentile Latency (ms) | 2.03 | 1.23 |
MySQL UPDATE (Indexed)
| Vultr – Cloud Compute (1 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 8,507.00 | 17,123.00 |
| Queries per second | 85,070.00 | 171,230.00 |
| Minimum Latency (ms) | 0.75 | 0.38 |
| Average Latency (ms) | 1.17 | 0.58 |
| Maximum Latency (ms) | 17.31 | 2 |
| 95th Percentile Latency (ms) | 1.64 | 0.78 |
MySQL UPDATE (Non-Indexed)
| Vultr – Cloud Compute (1 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 9,044.00 | 16,979.00 |
| Queries per second | 90,440.00 | 169,790.00 |
| Minimum Latency (ms) | 0.7 | 0.38 |
| Average Latency (ms) | 1.1 | 0.59 |
| Maximum Latency (ms) | 11.45 | 4.13 |
| 95th Percentile Latency (ms) | 1.34 | 0.8 |
MySQL DELETE
| Vultr – Cloud Compute (1 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 62,368.00 | 156,424.00 |
| Queries per second | 623,680.00 | 1,564,240.00 |
| Minimum Latency (ms) | 0.07 | 0.03 |
| Average Latency (ms) | 0.16 | 0.06 |
| Maximum Latency (ms) | 8.24 | 4.87 |
| 95th Percentile Latency (ms) | 0.97 | 0.07 |
Redis
| Vultr – Cloud Compute (1 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE per Second | 34,916.20 | 88,652.48 |
| PING_MBULK per Second | 34,626.04 | 89,605.73 |
| SET per Second | 34,904.02 | 90,171.33 |
| GET per Second | 35,460.99 | 90,579.71 |
| INCR per Second | 36,603.22 | 90,744.10 |
| LPUSH per Second | 35,855.14 | 90,497.73 |
| RPUSH per Second | 35,997.12 | 90,415.91 |
| LPOP per Second | 35,587.19 | 90,909.09 |
| RPOP per Second | 36,075.04 | 90,661.83 |
| SADD per Second | 33,818.06 | 90,252.70 |
| HSET per Second | 36,127.17 | 90,415.91 |
| SPOP per Second | 36,363.64 | 89,928.05 |
| ZADD per Second | 35,842.29 | 90,415.91 |
| ZPOPMIN per Second | 36,509.68 | 90,009.01 |
| LRANGE_100 (first 100 elements) per Second | 24,348.67 | 66,533.60 |
| LRANGE_300 (first 300 elements) per Second | 13,199.58 | 36,179.45 |
| LRANGE_500 (first 500 elements) per Second | 9,087.60 | 26,239.83 |
| LRANGE_600 (first 600 elements) per Second | 8,021.18 | 22,547.91 |
| MSET (10 keys) per Second | 33,875.34 | 88,105.73 |
Redis Average Latency (ms)
| Vultr – Cloud Compute (1 GB) | Vultr – High Frequency Intel (2 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE | 0.93 | 0.30 |
| PING_MBULK | 0.94 | 0.29 |
| SET | 0.94 | 0.29 |
| GET | 0.92 | 0.29 |
| INCR | 0.90 | 0.28 |
| LPUSH | 0.92 | 0.29 |
| RPUSH | 0.91 | 0.29 |
| LPOP | 0.93 | 0.28 |
| RPOP | 0.92 | 0.28 |
| SADD | 0.99 | 0.29 |
| HSET | 0.91 | 0.29 |
| SPOP | 0.90 | 0.29 |
| ZADD | 0.92 | 0.29 |
| ZPOPMIN | 0.90 | 0.29 |
| LRANGE_100 (first 100 elements) | 1.38 | 0.39 |
| LRANGE_300 (first 300 elements) | 2.55 | 0.71 |
| LRANGE_500 (first 500 elements) | 3.78 | 0.97 |
| LRANGE_600 (first 600 elements) | 4.25 | 1.14 |
| MSET (10 keys) | 1.02 | 0.30 |
Conclusion
From the friendly robots:
Based on the provided benchmarks, Vultr's Cloud Compute (1 GB) instance shows respectable performance with strong Redis throughput and low latency in most operations, though it struggles with more complex Redis commands and larger data sets. In contrast, the High Frequency Intel (2 GB, 2 Cores) instance offers significantly higher performance across the board, especially in CPU-intensive tasks, complex Redis operations, and large data sets. It handles bulk inserts and large LRANGE operations much faster, providing better performance for high-concurrency environments and demanding workloads. The High Frequency instance is ideal for applications requiring substantial computational power and multi-core processing, while the Cloud Compute instance might be more suitable for lighter workloads or cost-sensitive use cases.
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.