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

Linode (8 GB) is $48.00/mo and includes 4 vCPU, 8 GB RAM, 160 GB SSD of storage, and 5 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 (8 GB)?

Linode (8 GB) has 4 vCPU, 8 GB RAM, 160 GB SSD of storage, and 5 TB of monthly transfer for $48.00/mo.

Linode 8 GB ($48/mo) vs. Vultr Cloud Compute 2 GB, 2 Cores ($15/mo) Benchmarks

Welcome to another round of the VPS Showdown. Today I've spun up some brand new instance from Linode and Vultr to run some benchmarks on. All instances were spun up with Ubuntu 24.04 LTS x64 and all resided in or around the New York / New Jersey area. Enough talk. Here's the data.

Overview

	Linode – (8 GB)	Vultr – Cloud Compute (2 GB, 2 Cores)
Last Benchmarked	Wed, 13 May 2026 12: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	$48.00	$15.00
RAM (GB)	8	2
CPU Cores	4	2
Storage (TB)	160	65
Storage Type	SSD	SSD
Transfer (TB)	5	3

CPU

	Linode – (8 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,600.00	7,583.99
Events per Second	1,617.18	1,481.60
Minimum Latency (ms)	0.6	0.63
Average Latency (ms)	0.62	0.67
Maximum Latency (ms)	4.03	1.95
95th Percentile Latency (ms)	0.63	0.77

Memory Read

	Linode – (8 GB)	Vultr – Cloud Compute (2 GB, 2 Cores)
Operations per second	5,413,239.64	6,401,389.08
Mebibytes per second	5,286.37	6,251.36
Minimum Latency (ms)	0	0
Average Latency (ms)	0	0
Maximum Latency (ms)	0.27	0.23
95th Percentile Latency (ms)	0	0

Memory Write

	Linode – (8 GB)	Vultr – Cloud Compute (2 GB, 2 Cores)
Operations per second	5,401,772.35	6,411,085.35
Mebibytes per second	5,275.17	6,260.83
Minimum Latency (ms)	0	0
Average Latency (ms)	0	0
Maximum Latency (ms)	3.16	0.18
95th Percentile Latency (ms)	0	0

File I/O

	Linode – (8 GB)	Vultr – Cloud Compute (2 GB, 2 Cores)
Reads per Second	5,352.26	4,345.71
Writes per Second	3,568.24	2,897.07
Fsyncs per Second	11,427.82	9,273.19
Read Mebibytes per Second	83.63	67.90
Written Mebibytes per Second	55.75	45.27
Minimum Latency (ms)	0	0
Average Latency (ms)	0.05	0.06
Maximum Latency (ms)	17.35	2.92
95th Percentile Latency (ms)	0.17	0.17

Mutex

	Linode – (8 GB)	Vultr – Cloud Compute (2 GB, 2 Cores)
Minimum Latency (ms)	348.05	214.63
Average Latency (ms)	396.31	569.72
Maximum Latency (ms)	431.69	636.55
95th Percentile Latency (ms)	434.83	634.66

MySQL Read-only

	Linode – (8 GB)	Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second	6,622.00	8,015.00
Queries per second	66,220.00	80,150.00
Minimum Latency (ms)	1.26	0.92
Average Latency (ms)	1.51	1.25
Maximum Latency (ms)	5.55	5.5
95th Percentile Latency (ms)	1.79	1.86

MySQL Write-only

	Linode – (8 GB)	Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second	6,585.00	8,497.00
Queries per second	65,850.00	84,970.00
Minimum Latency (ms)	1.08	0.76
Average Latency (ms)	1.52	1.17
Maximum Latency (ms)	13.03	3.04
95th Percentile Latency (ms)	1.89	1.55

MySQL Read/Write

	Linode – (8 GB)	Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second	3,140.00	3,726.00
Queries per second	31,400.00	37,260.00
Minimum Latency (ms)	2.42	1.78
Average Latency (ms)	3.18	2.68
Maximum Latency (ms)	20.95	5.82
95th Percentile Latency (ms)	3.62	3.43

MySQL INSERT

	Linode – (8 GB)	Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second	8,943.00	15,028.00
Queries per second	89,430.00	150,280.00
Minimum Latency (ms)	0.7	0.41
Average Latency (ms)	1.12	0.66
Maximum Latency (ms)	12.42	2.42
95th Percentile Latency (ms)	1.34	0.86

MySQL Bulk INSERT

	Linode – (8 GB)	Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second	1,608,842.00	1,696,217.00
Queries per second	16,088,420.00	16,962,170.00
Minimum Latency (ms)	0	0
Average Latency (ms)	0.01	0.01
Maximum Latency (ms)	398.1	283.37
95th Percentile Latency (ms)	0	0

MySQL SELECT

	Linode – (8 GB)	Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second	154,001.00	201,989.00
Queries per second	1,540,010.00	2,019,890.00
Minimum Latency (ms)	0.04	0.03
Average Latency (ms)	0.06	0.05
Maximum Latency (ms)	8.37	0.51
95th Percentile Latency (ms)	0.08	0.07

MySQL SELECT (Random Points)

	Linode – (8 GB)	Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second	8,666.00	8,025.00
Queries per second	86,660.00	80,250.00
Minimum Latency (ms)	0.32	0.35
Average Latency (ms)	1.15	1.24
Maximum Latency (ms)	4.6	3.55
95th Percentile Latency (ms)	1.44	2.07

MySQL SELECT (Random Ranges)

	Linode – (8 GB)	Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second	7,418.00	8,336.00
Queries per second	74,180.00	83,360.00
Minimum Latency (ms)	0.49	0.4
Average Latency (ms)	1.35	1.2
Maximum Latency (ms)	4.59	4.25
95th Percentile Latency (ms)	1.73	2.22

MySQL UPDATE (Indexed)

	Linode – (8 GB)	Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second	8,731.00	13,858.00
Queries per second	87,310.00	138,580.00
Minimum Latency (ms)	0.74	0.42
Average Latency (ms)	1.14	0.72
Maximum Latency (ms)	12.55	6.33
95th Percentile Latency (ms)	1.39	0.95

MySQL UPDATE (Non-Indexed)

	Linode – (8 GB)	Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second	9,183.00	14,587.00
Queries per second	91,830.00	145,870.00
Minimum Latency (ms)	0.71	0.4
Average Latency (ms)	1.09	0.68
Maximum Latency (ms)	19.59	11.69
95th Percentile Latency (ms)	1.25	0.9

MySQL DELETE

	Linode – (8 GB)	Vultr – Cloud Compute (2 GB, 2 Cores)
Transactions per second	90,891.00	129,013.00
Queries per second	908,910.00	1,290,130.00
Minimum Latency (ms)	0.04	0.03
Average Latency (ms)	0.11	0.08
Maximum Latency (ms)	14.78	2.61
95th Percentile Latency (ms)	0.12	0.09

Redis

	Linode – (8 GB)	Vultr – Cloud Compute (2 GB, 2 Cores)
PING_INLINE per Second	59,171.59	78,247.26
PING_MBULK per Second	58,823.53	74,738.41
SET per Second	58,173.36	77,041.60
GET per Second	59,066.75	83,333.33
INCR per Second	59,453.03	80,971.66
LPUSH per Second	60,569.35	79,113.92
RPUSH per Second	59,880.24	77,160.49
LPOP per Second	57,537.40	81,499.59
RPOP per Second	57,636.89	82,440.23
SADD per Second	56,625.14	80,192.46
HSET per Second	58,377.11	83,612.04
SPOP per Second	56,850.48	85,034.02
ZADD per Second	58,241.12	83,263.95
ZPOPMIN per Second	57,339.45	82,987.55
LRANGE_100 (first 100 elements) per Second	46,838.41	55,555.56
LRANGE_300 (first 300 elements) per Second	27,517.89	28,851.70
LRANGE_500 (first 500 elements) per Second	20,226.54	19,391.12
LRANGE_600 (first 600 elements) per Second	17,812.61	17,211.71
MSET (10 keys) per Second	59,417.71	80,256.82

Redis Average Latency (ms)

	Linode – (8 GB)	Vultr – Cloud Compute (2 GB, 2 Cores)
PING_INLINE	0.44	0.34
PING_MBULK	0.44	0.35
SET	0.45	0.34
GET	0.44	0.32
INCR	0.44	0.32
LPUSH	0.43	0.34
RPUSH	0.43	0.34
LPOP	0.45	0.32
RPOP	0.45	0.32
SADD	0.46	0.32
HSET	0.44	0.31
SPOP	0.45	0.30
ZADD	0.44	0.31
ZPOPMIN	0.45	0.31
LRANGE_100 (first 100 elements)	0.56	0.54
LRANGE_300 (first 300 elements)	0.94	1.11
LRANGE_500 (first 500 elements)	1.30	1.62
LRANGE_600 (first 600 elements)	1.46	1.84
MSET (10 keys)	0.44	0.38

Conclusion

From the friendly robots:

After analyzing the benchmark results of the Linode (8 GB) and Vultr Cloud Compute (2 GB, 2 Cores) instances, it's clear that the Linode instance offers superior performance for CPU-intensive and memory-heavy workloads, showcasing impressive Redis operations per second and lower latency across various metrics. The Linode instance also excels in file I/O operations and database performance, particularly in MySQL bulk inserts and OLTP operations. Conversely, the Vultr instance, despite having fewer CPU cores and RAM, performs remarkably well in Redis operations and has a comparable file I/O performance. The Vultr instance might be more suitable for scenarios requiring lower costs and sufficient performance for less demanding applications or those primarily relying on Redis. Therefore, the Linode instance is recommended for applications needing high computational power and memory efficiency, while the Vultr instance is ideal for cost-sensitive workloads with moderate computational requirements.

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