How much does Vultr Cloud Compute (1 GB) cost per month?

Vultr Cloud Compute (1 GB) is $5.00/mo and includes 1 vCPU, 1 GB RAM, 25 GB SSD of storage, and 1 TB of transfer.

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

Vultr Cloud Compute (2 GB) is $10.00/mo and includes 1 vCPU, 2 GB RAM, 50 GB SSD of storage, and 2 TB of transfer.

What are the specs of Vultr Cloud Compute (1 GB)?

Vultr Cloud Compute (1 GB) has 1 vCPU, 1 GB RAM, 25 GB SSD of storage, and 1 TB of monthly transfer for $5.00/mo.

Vultr Cloud Compute 1 GB ($5/mo) vs. Vultr Cloud Compute 2 GB ($10/mo) Benchmarks

New day, new benchmarks. Today I've spun up brand new instance from Vultr and ran my world famous suite of benchmarking scripts. All instances were spun up with 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	Thu, 21 May 2026 23:00:52 GMT	Sun, 24 May 2026 00:00:52 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	$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 Core Processor (Skylake, IBRS, no TSX)
Clock Speed (MHz)	2,394.45	3,792.00
CPU Cache Size (KB)	16,384.00	16,384.00
BogoMips	4,788.90	7,583.99
Events per Second	859.04	1,570.19
Minimum Latency (ms)	1.14	0.62
Average Latency (ms)	1.16	0.64
Maximum Latency (ms)	2.42	2.42
95th Percentile Latency (ms)	1.25	0.68

Memory Read

	Vultr – Cloud Compute (1 GB)	Vultr – Cloud Compute (2 GB)
Operations per second	4,179,696.98	7,754,811.85
Mebibytes per second	4,081.74	7,573.06
Minimum Latency (ms)	0	0
Average Latency (ms)	0	0
Maximum Latency (ms)	0.23	0.15
95th Percentile Latency (ms)	0	0

Memory Write

	Vultr – Cloud Compute (1 GB)	Vultr – Cloud Compute (2 GB)
Operations per second	4,151,553.00	7,660,018.80
Mebibytes per second	4,054.25	7,480.49
Minimum Latency (ms)	0	0
Average Latency (ms)	0	0
Maximum Latency (ms)	0.59	0.16
95th Percentile Latency (ms)	0	0

File I/O

	Vultr – Cloud Compute (1 GB)	Vultr – Cloud Compute (2 GB)
Reads per Second	2,403.90	4,923.75
Writes per Second	1,602.60	3,282.50
Fsyncs per Second	5,132.41	10,516.60
Read Mebibytes per Second	37.56	76.93
Written Mebibytes per Second	25.04	51.29
Minimum Latency (ms)	0	0
Average Latency (ms)	0.11	0.05
Maximum Latency (ms)	3.04	1.71
95th Percentile Latency (ms)	0.32	0.17

Mutex

	Vultr – Cloud Compute (1 GB)	Vultr – Cloud Compute (2 GB)
Minimum Latency (ms)	2,066.64	1,097.77
Average Latency (ms)	2,071.43	1,106.88
Maximum Latency (ms)	2,075.26	1,113.46
95th Percentile Latency (ms)	2,082.91	1,109.09

MySQL Read-only

	Vultr – Cloud Compute (1 GB)	Vultr – Cloud Compute (2 GB)
Transactions per second	5,409.00	10,573.00
Queries per second	54,090.00	105,730.00
Minimum Latency (ms)	1.74	0.88
Average Latency (ms)	1.85	0.94
Maximum Latency (ms)	13.71	2.44
95th Percentile Latency (ms)	2	1.01

MySQL Write-only

	Vultr – Cloud Compute (1 GB)	Vultr – Cloud Compute (2 GB)
Transactions per second	4,997.00	9,479.00
Queries per second	49,970.00	94,790.00
Minimum Latency (ms)	1.47	0.68
Average Latency (ms)	2	1.05
Maximum Latency (ms)	10.54	3.67
95th Percentile Latency (ms)	2.61	1.42

MySQL Read/Write

	Vultr – Cloud Compute (1 GB)	Vultr – Cloud Compute (2 GB)
Transactions per second	2,422.00	4,345.00
Queries per second	24,220.00	43,450.00
Minimum Latency (ms)	3.55	1.81
Average Latency (ms)	4.13	2.3
Maximum Latency (ms)	12.42	16.56
95th Percentile Latency (ms)	4.82	2.81

MySQL INSERT

	Vultr – Cloud Compute (1 GB)	Vultr – Cloud Compute (2 GB)
Transactions per second	9,166.00	16,503.00
Queries per second	91,660.00	165,030.00
Minimum Latency (ms)	0.71	0.37
Average Latency (ms)	1.09	0.6
Maximum Latency (ms)	6.03	2.13
95th Percentile Latency (ms)	1.39	0.78

MySQL Bulk INSERT

	Vultr – Cloud Compute (1 GB)	Vultr – Cloud Compute (2 GB)
Transactions per second	937,763.00	2,103,967.00
Queries per second	9,377,630.00	21,039,670.00
Minimum Latency (ms)	0	0
Average Latency (ms)	0.01	0
Maximum Latency (ms)	661.15	228.8
95th Percentile Latency (ms)	0	0

MySQL SELECT

	Vultr – Cloud Compute (1 GB)	Vultr – Cloud Compute (2 GB)
Transactions per second	117,346.00	231,690.00
Queries per second	1,173,460.00	2,316,900.00
Minimum Latency (ms)	0.07	0.04
Average Latency (ms)	0.08	0.04
Maximum Latency (ms)	7.11	0.93
95th Percentile Latency (ms)	0.11	0.06

MySQL SELECT (Random Points)

	Vultr – Cloud Compute (1 GB)	Vultr – Cloud Compute (2 GB)
Transactions per second	5,731.00	10,866.00
Queries per second	57,310.00	108,660.00
Minimum Latency (ms)	0.62	0.32
Average Latency (ms)	1.74	0.92
Maximum Latency (ms)	6.81	3.21
95th Percentile Latency (ms)	2.18	1.18

MySQL SELECT (Random Ranges)

	Vultr – Cloud Compute (1 GB)	Vultr – Cloud Compute (2 GB)
Transactions per second	6,416.00	10,969.00
Queries per second	64,160.00	109,690.00
Minimum Latency (ms)	0.47	0.23
Average Latency (ms)	1.56	0.91
Maximum Latency (ms)	4.83	2.54
95th Percentile Latency (ms)	2	1.18

MySQL UPDATE (Indexed)

	Vultr – Cloud Compute (1 GB)	Vultr – Cloud Compute (2 GB)
Transactions per second	8,258.00	15,225.00
Queries per second	82,580.00	152,250.00
Minimum Latency (ms)	0.72	0.38
Average Latency (ms)	1.21	0.66
Maximum Latency (ms)	35.33	2.32
95th Percentile Latency (ms)	1.79	0.92

MySQL UPDATE (Non-Indexed)

	Vultr – Cloud Compute (1 GB)	Vultr – Cloud Compute (2 GB)
Transactions per second	8,930.00	16,166.00
Queries per second	89,300.00	161,660.00
Minimum Latency (ms)	0.71	0.38
Average Latency (ms)	1.12	0.62
Maximum Latency (ms)	20.29	2.03
95th Percentile Latency (ms)	1.39	0.81

MySQL DELETE

	Vultr – Cloud Compute (1 GB)	Vultr – Cloud Compute (2 GB)
Transactions per second	50,174.00	141,631.00
Queries per second	501,740.00	1,416,310.00
Minimum Latency (ms)	0.07	0.04
Average Latency (ms)	0.2	0.07
Maximum Latency (ms)	18.49	4.27
95th Percentile Latency (ms)	1.1	0.1

Redis

	Vultr – Cloud Compute (1 GB)	Vultr – Cloud Compute (2 GB)
PING_INLINE per Second	36,643.46	54,083.29
PING_MBULK per Second	37,230.08	54,854.64
SET per Second	36,724.20	54,734.54
GET per Second	36,982.25	55,157.20
INCR per Second	36,941.26	55,218.11
LPUSH per Second	36,483.04	54,495.91
RPUSH per Second	37,091.99	53,276.50
LPOP per Second	36,643.46	52,994.17
RPOP per Second	36,764.71	53,022.27
SADD per Second	37,523.45	53,533.19
HSET per Second	36,995.93	53,219.80
SPOP per Second	37,565.74	53,333.33
ZADD per Second	37,009.62	54,585.15
ZPOPMIN per Second	34,916.20	55,340.34
LRANGE_100 (first 100 elements) per Second	23,557.13	37,202.38
LRANGE_300 (first 300 elements) per Second	12,960.08	20,316.95
LRANGE_500 (first 500 elements) per Second	9,176.00	14,148.27
LRANGE_600 (first 600 elements) per Second	7,776.65	12,487.51
MSET (10 keys) per Second	31,017.37	51,308.36

Redis Average Latency (ms)

	Vultr – Cloud Compute (1 GB)	Vultr – Cloud Compute (2 GB)
PING_INLINE	0.89	0.61
PING_MBULK	0.88	0.59
SET	0.90	0.60
GET	0.89	0.59
INCR	0.89	0.59
LPUSH	0.91	0.60
RPUSH	0.89	0.62
LPOP	0.91	0.62
RPOP	0.90	0.62
SADD	0.88	0.61
HSET	0.89	0.62
SPOP	0.87	0.61
ZADD	0.90	0.60
ZPOPMIN	0.96	0.59
LRANGE_100 (first 100 elements)	1.40	0.92
LRANGE_300 (first 300 elements)	2.57	1.71
LRANGE_500 (first 500 elements)	3.74	2.54
LRANGE_600 (first 600 elements)	4.36	2.89
MSET (10 keys)	1.09	0.67

Conclusion

From the friendly robots:

Upon analyzing the benchmarks for both Vultr instances, the 1 GB Cloud Compute instance shows stronger performance in Redis operations, achieving higher requests per second and lower latencies for commands like PING, SET, GET, INCR, and LPUSH, though it falls behind in more complex operations such as LRANGE with larger data sets. The 2 GB instance, while slightly lagging in simple Redis operations, demonstrates better performance in CPU-intensive tasks, file I/O operations, and more complex MySQL OLTP operations. The 2 GB instance also shows improved capabilities in handling larger datasets in LRANGE commands. Therefore, the 1 GB instance is ideal for scenarios requiring high throughput and low latency for Redis operations, while the 2 GB instance is better suited for workloads that benefit from additional RAM, such as complex computations, larger file operations, or more demanding database transactions.

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 (1 GB) vs. Vultr Cloud Compute (2 GB)