Vultr Cloud Compute (1 GB) vs. Vultr Cloud Compute (2 GB)

vs.

Fresh benchmarks coming at ya. Today I've spun up some brand new instance from 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

Vultr – Cloud Compute (1 GB) Vultr – Cloud Compute (2 GB)
Last Benchmarked Tue, 26 Aug 2025 17:00:52 GMT Sat, 23 Aug 2025 21:00:52 GMT
Linux Distro Ubuntu 24.04 LTS x64 Ubuntu 24.04 LTS x64
Kernel Version 6.8.0-60-generic 6.8.0-60-generic
MySQL Version 8.0.43-0ubuntu0.24.04.1 8.0.43-0ubuntu0.24.04.1
Redis Version 7.0.15 7.0.15
Location Newark, NJ Newark, NJ
Monthly Price $5.00 $10.00
RAM (GB) 1 2
CPU Cores 1 1
Storage (TB) 25 50
Storage Type SSD SSD
Transfer (TB) 1 2

CPU

Vultr – Cloud Compute (1 GB) Vultr – Cloud Compute (2 GB)
Vendor GenuineIntel GenuineIntel
Model Name Intel Core Processor (Broadwell, no TSX, IBRS) Intel Xeon Processor (Skylake, IBRS)
Clock Speed (MHz) 2,394.45 2,593.90
CPU Cache Size (KB) 16,384.00 16,384.00
BogoMips 4,788.90 5,187.80
Events per Second 861.36 1,072.81
Minimum Latency (ms) 1.14 0.88
Average Latency (ms) 1.16 0.93
Maximum Latency (ms) 2.77 3.05
95th Percentile Latency (ms) 1.21 1.08

Memory

Memory Read

Vultr – Cloud Compute (1 GB) Vultr – Cloud Compute (2 GB)
Operations per second 4,189,369.10 3,661,657.63
Mebibytes per second 4,091.18 3,575.84
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 1.75 0.81
95th Percentile Latency (ms) 0 0

Memory Write

Vultr – Cloud Compute (1 GB) Vultr – Cloud Compute (2 GB)
Operations per second 4,222,451.44 3,668,576.60
Mebibytes per second 4,123.49 3,582.59
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 0.72 0.3
95th Percentile Latency (ms) 0 0

File I/O

Vultr – Cloud Compute (1 GB) Vultr – Cloud Compute (2 GB)
Reads per Second 2,500.89 1,717.49
Writes per Second 1,667.19 1,144.96
Fsyncs per Second 5,346.52 3,670.58
Read Mebibytes per Second 39.08 26.84
Written Mebibytes per Second 26.05 17.89
Minimum Latency (ms) 0 0
Average Latency (ms) 0.1 0.15
Maximum Latency (ms) 3.4 19.3
95th Percentile Latency (ms) 0.3 0.54

Mutex

Vultr – Cloud Compute (1 GB) Vultr – Cloud Compute (2 GB)
Minimum Latency (ms) 2,081.46 1,741.97
Average Latency (ms) 2,089.86 1,758.80
Maximum Latency (ms) 2,098.02 1,769.90
95th Percentile Latency (ms) 2,082.91 1,771.29

MySQL

MySQL Read-only

Vultr – Cloud Compute (1 GB) Vultr – Cloud Compute (2 GB)
Transactions per second 5,526.00 5,315.00
Queries per second 55,260.00 53,150.00
Minimum Latency (ms) 1.7 1.69
Average Latency (ms) 1.81 1.88
Maximum Latency (ms) 11.86 5.38
95th Percentile Latency (ms) 1.93 2.35

MySQL Write-only

Vultr – Cloud Compute (1 GB) Vultr – Cloud Compute (2 GB)
Transactions per second 5,084.00 4,478.00
Queries per second 50,840.00 44,780.00
Minimum Latency (ms) 1.45 1.28
Average Latency (ms) 1.96 2.23
Maximum Latency (ms) 10.63 17.36
95th Percentile Latency (ms) 2.61 3.25

MySQL Read/Write

Vultr – Cloud Compute (1 GB) Vultr – Cloud Compute (2 GB)
Transactions per second 2,327.00 2,122.00
Queries per second 23,270.00 21,220.00
Minimum Latency (ms) 3.56 3.44
Average Latency (ms) 4.3 4.71
Maximum Latency (ms) 11.69 9.92
95th Percentile Latency (ms) 5.09 5.99

MySQL INSERT

Vultr – Cloud Compute (1 GB) Vultr – Cloud Compute (2 GB)
Transactions per second 9,678.00 6,336.00
Queries per second 96,780.00 63,360.00
Minimum Latency (ms) 0.71 0.9
Average Latency (ms) 1.03 1.57
Maximum Latency (ms) 5.87 169.64
95th Percentile Latency (ms) 1.27 1.86

MySQL Bulk INSERT

Vultr – Cloud Compute (1 GB) Vultr – Cloud Compute (2 GB)
Transactions per second 964,103.00 734,741.00
Queries per second 9,641,030.00 7,347,410.00
Minimum Latency (ms) 0 0
Average Latency (ms) 0.01 0.01
Maximum Latency (ms) 555.35 656.48
95th Percentile Latency (ms) 0 0

MySQL SELECT

Vultr – Cloud Compute (1 GB) Vultr – Cloud Compute (2 GB)
Transactions per second 123,440.00 165,032.00
Queries per second 1,234,400.00 1,650,320.00
Minimum Latency (ms) 0.07 0.05
Average Latency (ms) 0.08 0.06
Maximum Latency (ms) 6.36 1.21
95th Percentile Latency (ms) 0.1 0.08

MySQL SELECT (Random Points)

Vultr – Cloud Compute (1 GB) Vultr – Cloud Compute (2 GB)
Transactions per second 5,660.00 4,109.00
Queries per second 56,600.00 41,090.00
Minimum Latency (ms) 0.7 1.08
Average Latency (ms) 1.77 2.43
Maximum Latency (ms) 5.62 6.73
95th Percentile Latency (ms) 2.3 3.19

MySQL SELECT (Random Ranges)

Vultr – Cloud Compute (1 GB) Vultr – Cloud Compute (2 GB)
Transactions per second 5,897.00 2,588.00
Queries per second 58,970.00 25,880.00
Minimum Latency (ms) 0.59 1.28
Average Latency (ms) 1.69 3.86
Maximum Latency (ms) 5.37 7.6
95th Percentile Latency (ms) 2.22 5.28

MySQL UPDATE (Indexed)

Vultr – Cloud Compute (1 GB) Vultr – Cloud Compute (2 GB)
Transactions per second 8,813.00 5,165.00
Queries per second 88,130.00 51,650.00
Minimum Latency (ms) 0.72 0.74
Average Latency (ms) 1.13 1.93
Maximum Latency (ms) 6.19 2442.39
95th Percentile Latency (ms) 1.61 2.18

MySQL UPDATE (Non-Indexed)

Vultr – Cloud Compute (1 GB) Vultr – Cloud Compute (2 GB)
Transactions per second 9,183.00 7,250.00
Queries per second 91,830.00 72,500.00
Minimum Latency (ms) 0.7 0.75
Average Latency (ms) 1.09 1.38
Maximum Latency (ms) 7.93 7.35
95th Percentile Latency (ms) 1.37 1.86

MySQL DELETE

Vultr – Cloud Compute (1 GB) Vultr – Cloud Compute (2 GB)
Transactions per second 60,278.00 48,733.00
Queries per second 602,780.00 487,330.00
Minimum Latency (ms) 0.07 0.05
Average Latency (ms) 0.16 0.2
Maximum Latency (ms) 12.23 155.64
95th Percentile Latency (ms) 0.95 1.25

Redis

Vultr – Cloud Compute (1 GB) Vultr – Cloud Compute (2 GB)
PING_INLINE per Second 37,678.97 37,369.21
PING_MBULK per Second 37,467.22 37,257.82
SET per Second 36,469.73 33,852.40
GET per Second 38,022.81 35,335.69
INCR per Second 37,907.50 36,509.68
LPUSH per Second 30,238.89 33,647.38
RPUSH per Second 35,561.88 36,075.04
LPOP per Second 37,523.45 36,576.45
RPOP per Second 37,750.09 36,523.01
SADD per Second 37,678.97 36,900.37
HSET per Second 37,313.43 36,751.20
SPOP per Second 37,850.11 38,804.81
ZADD per Second 37,369.21 35,855.14
ZPOPMIN per Second 38,986.36 37,439.16
LRANGE_100 (first 100 elements) per Second 24,125.45 16,241.68
LRANGE_300 (first 300 elements) per Second 12,500.00 6,656.02
LRANGE_500 (first 500 elements) per Second 8,862.11 4,115.23
LRANGE_600 (first 600 elements) per Second 7,744.73 3,511.36
MSET (10 keys) per Second 34,554.25 25,354.97

Redis Average Latency (ms)

Vultr – Cloud Compute (1 GB) Vultr – Cloud Compute (2 GB)
PING_INLINE0.880.87
PING_MBULK0.880.86
SET0.910.95
GET0.880.91
INCR0.880.89
LPUSH1.080.96
RPUSH0.940.90
LPOP0.900.90
RPOP0.890.90
SADD0.880.89
HSET0.900.90
SPOP0.880.85
ZADD0.900.92
ZPOPMIN0.870.87
LRANGE_100 (first 100 elements)1.412.15
LRANGE_300 (first 300 elements)2.745.13
LRANGE_500 (first 500 elements)3.907.96
LRANGE_600 (first 600 elements)4.419.35
MSET (10 keys)1.021.42

Conclusion

From the friendly robots:

The Vultr Cloud Compute (1 GB) instance shows strong performance in Redis operations, with high request rates and low latency, making it suitable for applications requiring high-speed data access and low-latency responses. However, it struggles with larger Redis commands like LRANGE, indicating potential limitations in handling more I/O-intensive tasks. In contrast, the Vultr Cloud Compute (2 GB) instance, while slightly slower in some Redis operations, demonstrates better performance in handling larger data sets and more complex MySQL operations, suggesting it is better suited for workloads that require more memory and processing power, such as database-intensive applications or tasks that involve more extensive data processing. Overall, the 1 GB instance is ideal for low-memory, high-speed data access scenarios, while the 2 GB instance is better for more demanding applications requiring greater computational and memory resources.

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.