How much does Vultr Cloud Compute (2 GB, 2 Cores) cost per month?

Vultr Cloud Compute (2 GB, 2 Cores) is $15.00/mo and includes 2 vCPU, 2 GB RAM, 65 GB SSD of storage, and 3 TB of transfer.

How much does Vultr Cloud Compute (4 GB, 2 Cores) cost per month?

Vultr Cloud Compute (4 GB, 2 Cores) is $20.00/mo and includes 2 vCPU, 4 GB RAM, 80 GB SSD of storage, and 3 TB of transfer.

What are the specs of Vultr Cloud Compute (2 GB, 2 Cores)?

Vultr Cloud Compute (2 GB, 2 Cores) has 2 vCPU, 2 GB RAM, 65 GB SSD of storage, and 3 TB of monthly transfer for $15.00/mo.

Vultr Cloud Compute 2 GB, 2 Cores ($15/mo) vs. Vultr Cloud Compute 4 GB, 2 Cores ($20/mo) Benchmarks

Fresh benchmarks coming at ya. Today I've spun up some brand new instance from Vultr and did some benchmarking. All instances were spun up with Ubuntu 24.04 LTS x64 and all resided in or around the New York / New Jersey area. Without further ado, here's the results.

Overview

	Vultr – Cloud Compute (2 GB, 2 Cores)	Vultr – Cloud Compute (4 GB, 2 Cores)
Last Benchmarked	Mon, 11 May 2026 04:00:52 GMT	Mon, 11 May 2026 14: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	$20.00
RAM (GB)	2	4
CPU Cores	2	2
Storage (TB)	65	80
Storage Type	SSD	SSD
Transfer (TB)	3	3

CPU

	Vultr – Cloud Compute (2 GB, 2 Cores)	Vultr – Cloud Compute (4 GB, 2 Cores)
Vendor	GenuineIntel	GenuineIntel
Model Name	Intel Core Processor (Skylake, IBRS, no TSX)	Intel Core Processor (Skylake, IBRS, no TSX)
Clock Speed (MHz)	3,792.00	3,792.06
CPU Cache Size (KB)	16,384.00	16,384.00
BogoMips	7,583.99	7,584.11
Events per Second	1,481.60	1,499.48
Minimum Latency (ms)	0.63	0.62
Average Latency (ms)	0.67	0.67
Maximum Latency (ms)	1.95	2.83
95th Percentile Latency (ms)	0.77	0.74

Memory Read

	Vultr – Cloud Compute (2 GB, 2 Cores)	Vultr – Cloud Compute (4 GB, 2 Cores)
Operations per second	6,401,389.08	6,934,927.69
Mebibytes per second	6,251.36	6,772.39
Minimum Latency (ms)	0	0
Average Latency (ms)	0	0
Maximum Latency (ms)	0.23	0.29
95th Percentile Latency (ms)	0	0

Memory Write

	Vultr – Cloud Compute (2 GB, 2 Cores)	Vultr – Cloud Compute (4 GB, 2 Cores)
Operations per second	6,411,085.35	6,985,095.21
Mebibytes per second	6,260.83	6,821.38
Minimum Latency (ms)	0	0
Average Latency (ms)	0	0
Maximum Latency (ms)	0.18	0.35
95th Percentile Latency (ms)	0	0

File I/O

	Vultr – Cloud Compute (2 GB, 2 Cores)	Vultr – Cloud Compute (4 GB, 2 Cores)
Reads per Second	4,345.71	7,963.30
Writes per Second	2,897.07	5,308.87
Fsyncs per Second	9,273.19	16,991.77
Read Mebibytes per Second	67.90	124.43
Written Mebibytes per Second	45.27	82.95
Minimum Latency (ms)	0	0
Average Latency (ms)	0.06	0.03
Maximum Latency (ms)	2.92	4.6
95th Percentile Latency (ms)	0.17	0.12

Mutex

	Vultr – Cloud Compute (2 GB, 2 Cores)	Vultr – Cloud Compute (4 GB, 2 Cores)
Minimum Latency (ms)	214.63	584.40
Average Latency (ms)	569.72	590.17
Maximum Latency (ms)	636.55	596.53
95th Percentile Latency (ms)	634.66	601.29

MySQL Read-only

	Vultr – Cloud Compute (2 GB, 2 Cores)	Vultr – Cloud Compute (4 GB, 2 Cores)
Transactions per second	8,015.00	9,520.00
Queries per second	80,150.00	95,200.00
Minimum Latency (ms)	0.92	0.89
Average Latency (ms)	1.25	1.05
Maximum Latency (ms)	5.5	2.89
95th Percentile Latency (ms)	1.86	1.34

MySQL Write-only

	Vultr – Cloud Compute (2 GB, 2 Cores)	Vultr – Cloud Compute (4 GB, 2 Cores)
Transactions per second	8,497.00	9,609.00
Queries per second	84,970.00	96,090.00
Minimum Latency (ms)	0.76	0.67
Average Latency (ms)	1.17	1.04
Maximum Latency (ms)	3.04	3.83
95th Percentile Latency (ms)	1.55	1.34

MySQL Read/Write

	Vultr – Cloud Compute (2 GB, 2 Cores)	Vultr – Cloud Compute (4 GB, 2 Cores)
Transactions per second	3,726.00	4,403.00
Queries per second	37,260.00	44,030.00
Minimum Latency (ms)	1.78	1.68
Average Latency (ms)	2.68	2.27
Maximum Latency (ms)	5.82	16.08
95th Percentile Latency (ms)	3.43	2.86

MySQL INSERT

	Vultr – Cloud Compute (2 GB, 2 Cores)	Vultr – Cloud Compute (4 GB, 2 Cores)
Transactions per second	15,028.00	16,748.00
Queries per second	150,280.00	167,480.00
Minimum Latency (ms)	0.41	0.4
Average Latency (ms)	0.66	0.6
Maximum Latency (ms)	2.42	2.24
95th Percentile Latency (ms)	0.86	0.78

MySQL Bulk INSERT

	Vultr – Cloud Compute (2 GB, 2 Cores)	Vultr – Cloud Compute (4 GB, 2 Cores)
Transactions per second	1,696,217.00	2,103,967.00
Queries per second	16,962,170.00	21,039,670.00
Minimum Latency (ms)	0	0
Average Latency (ms)	0.01	0
Maximum Latency (ms)	283.37	219.72
95th Percentile Latency (ms)	0	0

MySQL SELECT

	Vultr – Cloud Compute (2 GB, 2 Cores)	Vultr – Cloud Compute (4 GB, 2 Cores)
Transactions per second	201,989.00	213,392.00
Queries per second	2,019,890.00	2,133,920.00
Minimum Latency (ms)	0.03	0.03
Average Latency (ms)	0.05	0.05
Maximum Latency (ms)	0.51	0.67
95th Percentile Latency (ms)	0.07	0.06

MySQL SELECT (Random Points)

	Vultr – Cloud Compute (2 GB, 2 Cores)	Vultr – Cloud Compute (4 GB, 2 Cores)
Transactions per second	8,025.00	9,584.00
Queries per second	80,250.00	95,840.00
Minimum Latency (ms)	0.35	0.32
Average Latency (ms)	1.24	1.04
Maximum Latency (ms)	3.55	2.86
95th Percentile Latency (ms)	2.07	1.73

MySQL SELECT (Random Ranges)

	Vultr – Cloud Compute (2 GB, 2 Cores)	Vultr – Cloud Compute (4 GB, 2 Cores)
Transactions per second	8,336.00	8,392.00
Queries per second	83,360.00	83,920.00
Minimum Latency (ms)	0.4	0.42
Average Latency (ms)	1.2	1.19
Maximum Latency (ms)	4.25	5.16
95th Percentile Latency (ms)	2.22	2.48

MySQL UPDATE (Indexed)

	Vultr – Cloud Compute (2 GB, 2 Cores)	Vultr – Cloud Compute (4 GB, 2 Cores)
Transactions per second	13,858.00	15,380.00
Queries per second	138,580.00	153,800.00
Minimum Latency (ms)	0.42	0.4
Average Latency (ms)	0.72	0.65
Maximum Latency (ms)	6.33	2.85
95th Percentile Latency (ms)	0.95	0.89

MySQL UPDATE (Non-Indexed)

	Vultr – Cloud Compute (2 GB, 2 Cores)	Vultr – Cloud Compute (4 GB, 2 Cores)
Transactions per second	14,587.00	15,844.00
Queries per second	145,870.00	158,440.00
Minimum Latency (ms)	0.4	0.39
Average Latency (ms)	0.68	0.63
Maximum Latency (ms)	11.69	2.35
95th Percentile Latency (ms)	0.9	0.87

MySQL DELETE

	Vultr – Cloud Compute (2 GB, 2 Cores)	Vultr – Cloud Compute (4 GB, 2 Cores)
Transactions per second	129,013.00	145,838.00
Queries per second	1,290,130.00	1,458,380.00
Minimum Latency (ms)	0.03	0.03
Average Latency (ms)	0.08	0.07
Maximum Latency (ms)	2.61	1.4
95th Percentile Latency (ms)	0.09	0.08

Redis

	Vultr – Cloud Compute (2 GB, 2 Cores)	Vultr – Cloud Compute (4 GB, 2 Cores)
PING_INLINE per Second	78,247.26	83,402.84
PING_MBULK per Second	74,738.41	83,612.04
SET per Second	77,041.60	83,752.09
GET per Second	83,333.33	83,472.46
INCR per Second	80,971.66	81,300.81
LPUSH per Second	79,113.92	84,602.37
RPUSH per Second	77,160.49	82,508.25
LPOP per Second	81,499.59	85,910.65
RPOP per Second	82,440.23	84,317.03
SADD per Second	80,192.46	85,397.09
HSET per Second	83,612.04	83,056.48
SPOP per Second	85,034.02	81,300.81
ZADD per Second	83,263.95	85,984.52
ZPOPMIN per Second	82,987.55	86,505.19
LRANGE_100 (first 100 elements) per Second	55,555.56	52,438.39
LRANGE_300 (first 300 elements) per Second	28,851.70	26,954.18
LRANGE_500 (first 500 elements) per Second	19,391.12	19,466.62
LRANGE_600 (first 600 elements) per Second	17,211.71	16,923.34
MSET (10 keys) per Second	80,256.82	83,542.19

Redis Average Latency (ms)

	Vultr – Cloud Compute (2 GB, 2 Cores)	Vultr – Cloud Compute (4 GB, 2 Cores)
PING_INLINE	0.34	0.31
PING_MBULK	0.35	0.31
SET	0.34	0.31
GET	0.32	0.31
INCR	0.32	0.32
LPUSH	0.34	0.31
RPUSH	0.34	0.31
LPOP	0.32	0.31
RPOP	0.32	0.32
SADD	0.32	0.30
HSET	0.31	0.32
SPOP	0.30	0.32
ZADD	0.31	0.30
ZPOPMIN	0.31	0.30
LRANGE_100 (first 100 elements)	0.54	0.51
LRANGE_300 (first 300 elements)	1.11	1.05
LRANGE_500 (first 500 elements)	1.62	1.49
LRANGE_600 (first 600 elements)	1.84	1.60
MSET (10 keys)	0.38	0.32

Conclusion

From the friendly robots:

After analyzing the benchmark results for Vultr's Cloud Compute instances, it's evident that the 4 GB, 2 Cores version outperforms the 2 GB, 2 Cores version in most metrics. The higher RAM and CPU resources allow for greater throughput and lower latency in Redis operations, CPU events, file I/O, and MySQL operations. The 4 GB instance handles Redis commands like LPUSH, LRANGE, and MSET with significantly higher request rates per second and lower latencies. CPU performance, including thread fairness and execution time, also shows marked improvement. File I/O throughput for both reads and writes is higher, and memory operations exhibit lower latencies and higher transaction rates. Therefore, the 4 GB, 2 Cores instance is ideal for workloads requiring higher performance, more memory, and better multitasking capabilities, such as high-traffic web applications, database servers, or any CPU-intensive operations.

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.

Vultr Cloud Compute (2 GB, 2 Cores) vs. Vultr Cloud Compute (4 GB, 2 Cores)