How much does Linode (4 GB) cost per month?

Linode (4 GB) is $24.00/mo and includes 2 vCPU, 4 GB RAM, 80 GB SSD of storage, and 4 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 Linode (4 GB)?

Linode (4 GB) has 2 vCPU, 4 GB RAM, 80 GB SSD of storage, and 4 TB of monthly transfer for $24.00/mo.

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

My friend, I'm so glad you're here! Today I've spun up some brand new instance from Linode and Vultr to run some benchmarks on. Each instance was spun up with Ubuntu 24.04 LTS x64 and were created in or around the New York / New Jersey area. Enough talk. Here's the data.

Overview

	Linode – (4 GB)	Vultr – Cloud Compute (4 GB, 2 Cores)
Last Benchmarked	Mon, 01 Jun 2026 00:00:52 GMT	Sat, 30 May 2026 05: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-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	$24.00	$20.00
RAM (GB)	4	4
CPU Cores	2	2
Storage (TB)	80	80
Storage Type	SSD	SSD
Transfer (TB)	4	3

CPU

	Linode – (4 GB)	Vultr – Cloud Compute (4 GB, 2 Cores)
Vendor	AuthenticAMD	GenuineIntel
Model Name	AMD EPYC 7713 64-Core Processor	Intel Core Processor (Skylake, IBRS, no TSX)
Clock Speed (MHz)	2,000.00	3,792.00
CPU Cache Size (KB)	512.00	16,384.00
BogoMips	3,999.99	7,583.99
Events per Second	3,444.02	1,581.00
Minimum Latency (ms)	0.28	0.62
Average Latency (ms)	0.29	0.63
Maximum Latency (ms)	4.83	1.25
95th Percentile Latency (ms)	0.3	0.67

Memory Read

	Linode – (4 GB)	Vultr – Cloud Compute (4 GB, 2 Cores)
Operations per second	5,349,213.60	7,740,670.12
Mebibytes per second	5,223.84	7,559.25
Minimum Latency (ms)	0	0
Average Latency (ms)	0	0
Maximum Latency (ms)	3.16	0.08
95th Percentile Latency (ms)	0	0

Memory Write

	Linode – (4 GB)	Vultr – Cloud Compute (4 GB, 2 Cores)
Operations per second	5,332,401.09	7,498,489.66
Mebibytes per second	5,207.42	7,322.74
Minimum Latency (ms)	0	0
Average Latency (ms)	0	0
Maximum Latency (ms)	3.25	0.24
95th Percentile Latency (ms)	0	0

File I/O

	Linode – (4 GB)	Vultr – Cloud Compute (4 GB, 2 Cores)
Reads per Second	3,325.24	7,862.01
Writes per Second	2,216.89	5,241.34
Fsyncs per Second	7,095.98	16,779.39
Read Mebibytes per Second	51.96	122.84
Written Mebibytes per Second	34.64	81.90
Minimum Latency (ms)	0	0
Average Latency (ms)	0.08	0.03
Maximum Latency (ms)	13.12	2.28
95th Percentile Latency (ms)	0.22	0.12

Mutex

	Linode – (4 GB)	Vultr – Cloud Compute (4 GB, 2 Cores)
Minimum Latency (ms)	864.93	520.27
Average Latency (ms)	931.61	548.31
Maximum Latency (ms)	968.34	569.21
95th Percentile Latency (ms)	960.30	569.67

MySQL Read-only

	Linode – (4 GB)	Vultr – Cloud Compute (4 GB, 2 Cores)
Transactions per second	5,919.00	10,390.00
Queries per second	59,190.00	103,900.00
Minimum Latency (ms)	1.29	0.87
Average Latency (ms)	1.69	0.96
Maximum Latency (ms)	8	2.8
95th Percentile Latency (ms)	2.03	1.06

MySQL Write-only

	Linode – (4 GB)	Vultr – Cloud Compute (4 GB, 2 Cores)
Transactions per second	5,152.00	10,176.00
Queries per second	51,520.00	101,760.00
Minimum Latency (ms)	1.22	0.66
Average Latency (ms)	1.94	0.98
Maximum Latency (ms)	24.88	2.82
95th Percentile Latency (ms)	2.52	1.27

MySQL Read/Write

	Linode – (4 GB)	Vultr – Cloud Compute (4 GB, 2 Cores)
Transactions per second	2,609.00	4,990.00
Queries per second	26,090.00	49,900.00
Minimum Latency (ms)	2.83	1.6
Average Latency (ms)	3.83	2
Maximum Latency (ms)	8.83	3.19
95th Percentile Latency (ms)	4.74	2.3

MySQL INSERT

	Linode – (4 GB)	Vultr – Cloud Compute (4 GB, 2 Cores)
Transactions per second	7,493.00	16,211.00
Queries per second	74,930.00	162,110.00
Minimum Latency (ms)	0.73	0.37
Average Latency (ms)	1.33	0.62
Maximum Latency (ms)	15.06	16.01
95th Percentile Latency (ms)	1.86	0.83

MySQL Bulk INSERT

	Linode – (4 GB)	Vultr – Cloud Compute (4 GB, 2 Cores)
Transactions per second	1,754,467.00	2,395,217.00
Queries per second	17,544,670.00	23,952,170.00
Minimum Latency (ms)	0	0
Average Latency (ms)	0.01	0
Maximum Latency (ms)	418.75	207.28
95th Percentile Latency (ms)	0	0

MySQL SELECT

	Linode – (4 GB)	Vultr – Cloud Compute (4 GB, 2 Cores)
Transactions per second	130,180.00	229,866.00
Queries per second	1,301,800.00	2,298,660.00
Minimum Latency (ms)	0.05	0.03
Average Latency (ms)	0.08	0.04
Maximum Latency (ms)	4.63	0.68
95th Percentile Latency (ms)	0.1	0.06

MySQL SELECT (Random Points)

	Linode – (4 GB)	Vultr – Cloud Compute (4 GB, 2 Cores)
Transactions per second	8,212.00	11,703.00
Queries per second	82,120.00	117,030.00
Minimum Latency (ms)	0.33	0.26
Average Latency (ms)	1.22	0.85
Maximum Latency (ms)	11.27	2.08
95th Percentile Latency (ms)	2.3	1.1

MySQL SELECT (Random Ranges)

	Linode – (4 GB)	Vultr – Cloud Compute (4 GB, 2 Cores)
Transactions per second	8,956.00	10,274.00
Queries per second	89,560.00	102,740.00
Minimum Latency (ms)	0.42	0.32
Average Latency (ms)	1.12	0.97
Maximum Latency (ms)	4.66	2.94
95th Percentile Latency (ms)	1.44	1.25

MySQL UPDATE (Indexed)

	Linode – (4 GB)	Vultr – Cloud Compute (4 GB, 2 Cores)
Transactions per second	7,381.00	16,308.00
Queries per second	73,810.00	163,080.00
Minimum Latency (ms)	0.81	0.39
Average Latency (ms)	1.35	0.61
Maximum Latency (ms)	8.43	1.69
95th Percentile Latency (ms)	1.76	0.81

MySQL UPDATE (Non-Indexed)

	Linode – (4 GB)	Vultr – Cloud Compute (4 GB, 2 Cores)
Transactions per second	7,379.00	16,200.00
Queries per second	73,790.00	162,000.00
Minimum Latency (ms)	0.82	0.38
Average Latency (ms)	1.35	0.62
Maximum Latency (ms)	7.2	1.95
95th Percentile Latency (ms)	1.73	0.83

MySQL DELETE

	Linode – (4 GB)	Vultr – Cloud Compute (4 GB, 2 Cores)
Transactions per second	58,502.00	151,265.00
Queries per second	585,020.00	1,512,650.00
Minimum Latency (ms)	0.04	0.03
Average Latency (ms)	0.17	0.07
Maximum Latency (ms)	8.26	1.91
95th Percentile Latency (ms)	1.14	0.08

Redis

	Linode – (4 GB)	Vultr – Cloud Compute (4 GB, 2 Cores)
PING_INLINE per Second	44,444.45	87,642.41
PING_MBULK per Second	42,158.52	88,105.73
SET per Second	43,725.41	89,206.06
GET per Second	43,084.88	88,028.16
INCR per Second	43,917.44	90,497.73
LPUSH per Second	44,169.61	90,909.09
RPUSH per Second	42,918.46	90,909.09
LPOP per Second	43,630.02	89,847.26
RPOP per Second	42,900.04	89,605.73
SADD per Second	43,066.32	88,809.95
HSET per Second	42,826.55	90,334.23
SPOP per Second	43,821.21	90,090.09
ZADD per Second	43,706.29	91,240.88
ZPOPMIN per Second	46,554.93	90,415.91
LRANGE_100 (first 100 elements) per Second	30,084.24	66,755.67
LRANGE_300 (first 300 elements) per Second	21,141.65	35,435.86
LRANGE_500 (first 500 elements) per Second	17,825.31	24,937.65
LRANGE_600 (first 600 elements) per Second	15,969.34	22,831.05
MSET (10 keys) per Second	45,578.85	90,991.81

Redis Average Latency (ms)

	Linode – (4 GB)	Vultr – Cloud Compute (4 GB, 2 Cores)
PING_INLINE	0.58	0.30
PING_MBULK	0.61	0.29
SET	0.59	0.29
GET	0.60	0.29
INCR	0.59	0.29
LPUSH	0.58	0.29
RPUSH	0.60	0.28
LPOP	0.59	0.29
RPOP	0.60	0.29
SADD	0.60	0.29
HSET	0.60	0.29
SPOP	0.59	0.29
ZADD	0.59	0.28
ZPOPMIN	0.55	0.29
LRANGE_100 (first 100 elements)	0.89	0.39
LRANGE_300 (first 300 elements)	1.25	0.73
LRANGE_500 (first 500 elements)	1.50	1.03
LRANGE_600 (first 600 elements)	1.59	1.12
MSET (10 keys)	0.57	0.29

Conclusion

From the friendly robots:

Comparing the benchmark results of the Linode (4 GB) and Vultr (Cloud Compute, 4 GB, 2 Cores) instances, the Vultr instance shows superior performance in Redis operations, with significantly higher requests per second (rps) and lower latencies for most commands, although performance diminishes with larger list range operations. Linode excels in handling MySQL OLTP operations and file I/O tasks with better throughput and lower latencies. Both instances offer competitive RAM handling and CPU performance, with Vultr having a slight edge in raw CPU benchmarks. Linode's higher RAM and CPU fairness scores suggest better performance consistency. For applications prioritizing Redis performance, especially with smaller dataset operations, Vultr is preferable. Conversely, for workloads involving extensive MySQL transactions and file I/O operations, Linode's superior performance makes it the better choice.

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 links for Linode and Vultr.

You can also support me directly by buying me a coffee.

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