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 (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.

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 2 GB, 2 Cores ($15/mo) Benchmarks

New day, new benchmarks. Today I've spun up some brand new instance from Linode and Vultr to run some benchmarks on. All instances were running Ubuntu 24.04 LTS x64 and were created in or around the New York / New Jersey area. Time to see who showed up today.

Overview

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

CPU

	Linode – (4 GB)	Vultr – Cloud Compute (2 GB, 2 Cores)
Vendor	AuthenticAMD	GenuineIntel
Model Name	AMD EPYC 7642 48-Core Processor	Intel Core Processor (Skylake, IBRS, no TSX)
Clock Speed (MHz)	2,300.00	3,792.00
CPU Cache Size (KB)	512.00	16,384.00
BogoMips	4,599.99	7,583.99
Events per Second	1,565.18	1,481.60
Minimum Latency (ms)	0.61	0.63
Average Latency (ms)	0.64	0.67
Maximum Latency (ms)	29.29	1.95
95th Percentile Latency (ms)	0.67	0.77

Memory Read

	Linode – (4 GB)	Vultr – Cloud Compute (2 GB, 2 Cores)
Operations per second	5,196,836.70	6,401,389.08
Mebibytes per second	5,075.04	6,251.36
Minimum Latency (ms)	0	0
Average Latency (ms)	0	0
Maximum Latency (ms)	6.67	0.23
95th Percentile Latency (ms)	0	0

Memory Write

	Linode – (4 GB)	Vultr – Cloud Compute (2 GB, 2 Cores)
Operations per second	5,265,799.25	6,411,085.35
Mebibytes per second	5,142.38	6,260.83
Minimum Latency (ms)	0	0
Average Latency (ms)	0	0
Maximum Latency (ms)	3.2	0.18
95th Percentile Latency (ms)	0	0

File I/O

	Linode – (4 GB)	Vultr – Cloud Compute (2 GB, 2 Cores)
Reads per Second	4,130.88	4,345.71
Writes per Second	2,753.92	2,897.07
Fsyncs per Second	8,824.83	9,273.19
Read Mebibytes per Second	64.54	67.90
Written Mebibytes per Second	43.03	45.27
Minimum Latency (ms)	0	0
Average Latency (ms)	0.06	0.06
Maximum Latency (ms)	13.64	2.92
95th Percentile Latency (ms)	0.2	0.17

Mutex

	Linode – (4 GB)	Vultr – Cloud Compute (2 GB, 2 Cores)
Minimum Latency (ms)	1,558.43	214.63
Average Latency (ms)	1,574.75	569.72
Maximum Latency (ms)	1,589.79	636.55
95th Percentile Latency (ms)	1,589.90	634.66

MySQL Read-only

	Linode – (4 GB)	Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second	5,967.00	8,015.00
Queries per second	59,670.00	80,150.00
Minimum Latency (ms)	1.33	0.92
Average Latency (ms)	1.67	1.25
Maximum Latency (ms)	8.89	5.5
95th Percentile Latency (ms)	1.96	1.86

MySQL Write-only

	Linode – (4 GB)	Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second	5,997.00	8,497.00
Queries per second	59,970.00	84,970.00
Minimum Latency (ms)	1.09	0.76
Average Latency (ms)	1.67	1.17
Maximum Latency (ms)	6.64	3.04
95th Percentile Latency (ms)	2.22	1.55

MySQL Read/Write

	Linode – (4 GB)	Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second	2,949.00	3,726.00
Queries per second	29,490.00	37,260.00
Minimum Latency (ms)	2.51	1.78
Average Latency (ms)	3.39	2.68
Maximum Latency (ms)	13.89	5.82
95th Percentile Latency (ms)	4.25	3.43

MySQL INSERT

	Linode – (4 GB)	Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second	7,651.00	15,028.00
Queries per second	76,510.00	150,280.00
Minimum Latency (ms)	0.87	0.41
Average Latency (ms)	1.3	0.66
Maximum Latency (ms)	10.4	2.42
95th Percentile Latency (ms)	1.67	0.86

MySQL Bulk INSERT

	Linode – (4 GB)	Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second	1,463,217.00	1,696,217.00
Queries per second	14,632,170.00	16,962,170.00
Minimum Latency (ms)	0	0
Average Latency (ms)	0.01	0.01
Maximum Latency (ms)	458.31	283.37
95th Percentile Latency (ms)	0	0

MySQL SELECT

	Linode – (4 GB)	Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second	132,624.00	201,989.00
Queries per second	1,326,240.00	2,019,890.00
Minimum Latency (ms)	0.05	0.03
Average Latency (ms)	0.08	0.05
Maximum Latency (ms)	5.29	0.51
95th Percentile Latency (ms)	0.1	0.07

MySQL SELECT (Random Points)

	Linode – (4 GB)	Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second	8,339.00	8,025.00
Queries per second	83,390.00	80,250.00
Minimum Latency (ms)	0.4	0.35
Average Latency (ms)	1.2	1.24
Maximum Latency (ms)	8.39	3.55
95th Percentile Latency (ms)	1.58	2.07

MySQL SELECT (Random Ranges)

	Linode – (4 GB)	Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second	6,885.00	8,336.00
Queries per second	68,850.00	83,360.00
Minimum Latency (ms)	0.38	0.4
Average Latency (ms)	1.45	1.2
Maximum Latency (ms)	10.66	4.25
95th Percentile Latency (ms)	1.89	2.22

MySQL UPDATE (Indexed)

	Linode – (4 GB)	Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second	6,026.00	13,858.00
Queries per second	60,260.00	138,580.00
Minimum Latency (ms)	0.74	0.42
Average Latency (ms)	1.66	0.72
Maximum Latency (ms)	83.52	6.33
95th Percentile Latency (ms)	2.22	0.95

MySQL UPDATE (Non-Indexed)

	Linode – (4 GB)	Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second	7,626.00	14,587.00
Queries per second	76,260.00	145,870.00
Minimum Latency (ms)	0.74	0.4
Average Latency (ms)	1.31	0.68
Maximum Latency (ms)	8.03	11.69
95th Percentile Latency (ms)	1.86	0.9

MySQL DELETE

	Linode – (4 GB)	Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second	39,987.00	129,013.00
Queries per second	399,870.00	1,290,130.00
Minimum Latency (ms)	0.04	0.03
Average Latency (ms)	0.25	0.08
Maximum Latency (ms)	117.36	2.61
95th Percentile Latency (ms)	1.23	0.09

Redis

	Linode – (4 GB)	Vultr – Cloud Compute (2 GB, 2 Cores)
PING_INLINE per Second	53,447.35	78,247.26
PING_MBULK per Second	52,192.07	74,738.41
SET per Second	52,273.91	77,041.60
GET per Second	53,475.94	83,333.33
INCR per Second	53,879.31	80,971.66
LPUSH per Second	54,406.96	79,113.92
RPUSH per Second	55,035.77	77,160.49
LPOP per Second	54,794.52	81,499.59
RPOP per Second	54,734.54	82,440.23
SADD per Second	55,991.04	80,192.46
HSET per Second	51,975.05	83,612.04
SPOP per Second	53,219.80	85,034.02
ZADD per Second	50,175.61	83,263.95
ZPOPMIN per Second	53,937.43	82,987.55
LRANGE_100 (first 100 elements) per Second	43,252.59	55,555.56
LRANGE_300 (first 300 elements) per Second	26,021.34	28,851.70
LRANGE_500 (first 500 elements) per Second	18,214.94	19,391.12
LRANGE_600 (first 600 elements) per Second	16,469.04	17,211.71
MSET (10 keys) per Second	55,679.29	80,256.82

Redis Average Latency (ms)

	Linode – (4 GB)	Vultr – Cloud Compute (2 GB, 2 Cores)
PING_INLINE	0.49	0.34
PING_MBULK	0.51	0.35
SET	0.50	0.34
GET	0.49	0.32
INCR	0.48	0.32
LPUSH	0.48	0.34
RPUSH	0.47	0.34
LPOP	0.47	0.32
RPOP	0.47	0.32
SADD	0.46	0.32
HSET	0.50	0.31
SPOP	0.49	0.30
ZADD	0.51	0.31
ZPOPMIN	0.48	0.31
LRANGE_100 (first 100 elements)	0.61	0.54
LRANGE_300 (first 300 elements)	1.04	1.11
LRANGE_500 (first 500 elements)	1.48	1.62
LRANGE_600 (first 600 elements)	1.59	1.84
MSET (10 keys)	0.49	0.38

Conclusion

From the friendly robots:

The Linode instance (4 GB) provides higher performance metrics across the board compared to the Vultr instance (2 GB, 2 cores), especially in CPU-intensive tasks, memory operations, and file I/O performance, evidenced by its faster Redis and MySQL benchmarks, lower latency, higher throughput, and better thread fairness. The Linode instance's more powerful AMD EPYC processor and higher RAM contribute to its superior benchmark results. On the other hand, the Vultr instance, while still competent, lags behind in most metrics, especially in CPU and memory benchmarks, making it suitable for less demanding applications. Ideal use cases for the Linode instance include high-performance computing, database-intensive workloads, and tasks requiring substantial memory and CPU resources, whereas the Vultr instance would be more appropriate for smaller, less resource-intensive applications or development environments where cost is a primary concern.

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 (2 GB, 2 Cores)