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

vs.

Welcome to another round of the VPS Showdown. Today I've spun up brand new instance from Vultr and ran my world famous suite of benchmarking scripts. Each instance was 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 (4 GB, 2 Cores) Vultr – Cloud Compute (8 GB, 4 Cores)
Last Benchmarked Sat, 23 May 2026 22:00:52 GMT Sat, 23 May 2026 11: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 $20.00 $40.00
RAM (GB) 4 8
CPU Cores 2 4
Storage (TB) 80 160
Storage Type SSD SSD
Transfer (TB) 3 4

CPU

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – Cloud Compute (8 GB, 4 Cores)
Vendor GenuineIntel GenuineIntel
Model Name Intel Xeon Processor (Skylake, IBRS) Intel Xeon Processor (Skylake, IBRS)
Clock Speed (MHz) 2,593.90 2,593.90
CPU Cache Size (KB) 16,384.00 16,384.00
BogoMips 5,187.79 5,187.80
Events per Second 1,074.82 1,100.82
Minimum Latency (ms) 0.89 0.88
Average Latency (ms) 0.93 0.91
Maximum Latency (ms) 3.41 1.56
95th Percentile Latency (ms) 1.03 0.97

Memory

Memory Read

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – Cloud Compute (8 GB, 4 Cores)
Operations per second 3,392,226.37 3,685,781.23
Mebibytes per second 3,312.72 3,599.40
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 0.32 1.03
95th Percentile Latency (ms) 0 0

Memory Write

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – Cloud Compute (8 GB, 4 Cores)
Operations per second 3,266,324.29 3,590,629.63
Mebibytes per second 3,189.77 3,506.47
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 0.12 1.16
95th Percentile Latency (ms) 0 0

File I/O

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – Cloud Compute (8 GB, 4 Cores)
Reads per Second 4,885.01 4,999.39
Writes per Second 3,256.68 3,332.93
Fsyncs per Second 10,424.56 10,670.47
Read Mebibytes per Second 76.33 78.12
Written Mebibytes per Second 50.89 52.08
Minimum Latency (ms) 0 0
Average Latency (ms) 0.05 0.05
Maximum Latency (ms) 37.38 37.52
95th Percentile Latency (ms) 0.18 0.18

Mutex

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – Cloud Compute (8 GB, 4 Cores)
Minimum Latency (ms) 780.20 369.37
Average Latency (ms) 820.59 416.22
Maximum Latency (ms) 852.21 441.77
95th Percentile Latency (ms) 846.57 442.73

MySQL

MySQL Read-only

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – Cloud Compute (8 GB, 4 Cores)
Transactions per second 5,056.00 5,144.00
Queries per second 50,560.00 51,440.00
Minimum Latency (ms) 1.71 1.72
Average Latency (ms) 1.98 1.94
Maximum Latency (ms) 4.91 7.67
95th Percentile Latency (ms) 2.35 2.35

MySQL Write-only

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – Cloud Compute (8 GB, 4 Cores)
Transactions per second 5,600.00 5,108.00
Queries per second 56,000.00 51,080.00
Minimum Latency (ms) 1.16 1.15
Average Latency (ms) 1.78 1.96
Maximum Latency (ms) 24.98 12.52
95th Percentile Latency (ms) 2.3 2.71

MySQL Read/Write

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – Cloud Compute (8 GB, 4 Cores)
Transactions per second 2,588.00 2,247.00
Queries per second 25,880.00 22,470.00
Minimum Latency (ms) 2.95 3.08
Average Latency (ms) 3.86 4.45
Maximum Latency (ms) 14.05 29.7
95th Percentile Latency (ms) 4.65 5.28

MySQL INSERT

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – Cloud Compute (8 GB, 4 Cores)
Transactions per second 6,701.00 7,630.00
Queries per second 67,010.00 76,300.00
Minimum Latency (ms) 0.69 0.71
Average Latency (ms) 1.49 1.31
Maximum Latency (ms) 49.99 29.81
95th Percentile Latency (ms) 2.43 1.55

MySQL Bulk INSERT

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – Cloud Compute (8 GB, 4 Cores)
Transactions per second 931,337.00 898,571.00
Queries per second 9,313,370.00 8,985,710.00
Minimum Latency (ms) 0 0
Average Latency (ms) 0.01 0.01
Maximum Latency (ms) 546.12 505.86
95th Percentile Latency (ms) 0 0

MySQL SELECT

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – Cloud Compute (8 GB, 4 Cores)
Transactions per second 147,980.00 149,465.00
Queries per second 1,479,800.00 1,494,650.00
Minimum Latency (ms) 0.05 0.05
Average Latency (ms) 0.07 0.07
Maximum Latency (ms) 1.07 1.22
95th Percentile Latency (ms) 0.09 0.09

MySQL SELECT (Random Points)

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – Cloud Compute (8 GB, 4 Cores)
Transactions per second 4,052.00 4,249.00
Queries per second 40,520.00 42,490.00
Minimum Latency (ms) 0.9 0.83
Average Latency (ms) 2.47 2.35
Maximum Latency (ms) 7.09 6.6
95th Percentile Latency (ms) 3.36 3.02

MySQL SELECT (Random Ranges)

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – Cloud Compute (8 GB, 4 Cores)
Transactions per second 2,640.00 2,637.00
Queries per second 26,400.00 26,370.00
Minimum Latency (ms) 1.05 0.94
Average Latency (ms) 3.78 3.79
Maximum Latency (ms) 7.45 6.3
95th Percentile Latency (ms) 5 5.09

MySQL UPDATE (Indexed)

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – Cloud Compute (8 GB, 4 Cores)
Transactions per second 8,162.00 7,166.00
Queries per second 81,620.00 71,660.00
Minimum Latency (ms) 0.7 0.7
Average Latency (ms) 1.22 1.39
Maximum Latency (ms) 59.52 28.84
95th Percentile Latency (ms) 1.73 1.79

MySQL UPDATE (Non-Indexed)

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – Cloud Compute (8 GB, 4 Cores)
Transactions per second 8,372.00 7,661.00
Queries per second 83,720.00 76,610.00
Minimum Latency (ms) 0.72 0.7
Average Latency (ms) 1.19 1.3
Maximum Latency (ms) 19.85 33.97
95th Percentile Latency (ms) 1.55 1.58

MySQL DELETE

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – Cloud Compute (8 GB, 4 Cores)
Transactions per second 73,070.00 69,690.00
Queries per second 730,700.00 696,900.00
Minimum Latency (ms) 0.05 0.05
Average Latency (ms) 0.14 0.14
Maximum Latency (ms) 43.82 27.73
95th Percentile Latency (ms) 0.74 0.87

Redis

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – Cloud Compute (8 GB, 4 Cores)
PING_INLINE per Second 54,734.54 54,436.58
PING_MBULK per Second 54,259.36 48,828.12
SET per Second 55,555.56 51,572.98
GET per Second 55,370.98 48,239.27
INCR per Second 51,413.88 52,328.62
LPUSH per Second 51,626.23 45,454.54
RPUSH per Second 52,410.90 49,751.24
LPOP per Second 49,236.83 53,390.28
RPOP per Second 48,685.49 53,648.07
SADD per Second 49,309.66 48,285.85
HSET per Second 55,187.64 51,493.30
SPOP per Second 52,742.62 52,910.05
ZADD per Second 54,884.74 53,504.55
ZPOPMIN per Second 56,274.62 53,590.57
LRANGE_100 (first 100 elements) per Second 29,282.58 28,645.09
LRANGE_300 (first 300 elements) per Second 13,486.18 13,131.98
LRANGE_500 (first 500 elements) per Second 8,806.69 8,529.51
LRANGE_600 (first 600 elements) per Second 7,126.06 7,479.99
MSET (10 keys) per Second 52,631.58 49,212.60

Redis Average Latency (ms)

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – Cloud Compute (8 GB, 4 Cores)
PING_INLINE0.480.47
PING_MBULK0.480.53
SET0.470.50
GET0.470.54
INCR0.500.49
LPUSH0.500.58
RPUSH0.490.52
LPOP0.520.49
RPOP0.530.48
SADD0.530.54
HSET0.490.53
SPOP0.490.49
ZADD0.480.48
ZPOPMIN0.470.48
LRANGE_100 (first 100 elements)0.900.91
LRANGE_300 (first 300 elements)2.171.94
LRANGE_500 (first 500 elements)2.883.00
LRANGE_600 (first 600 elements)3.993.43
MSET (10 keys)0.730.77

Conclusion

From the friendly robots:

In comparing the Vultr Cloud Compute instances, the 4 GB, 2 Core configuration shows strong Redis performance with higher request per second (rps) rates for most operations, though its latency is slightly higher than that of the 8 GB, 4 Core instance. CPU performance is also robust, with comparable fairness and execution times. The 8 GB, 4 Core instance provides superior multi-threading capabilities, reflected in its higher rps rates across Redis operations and slightly lower latencies, suggesting it might be better suited for workloads that benefit from additional CPU cores and RAM, such as more complex database operations and applications with high I/O demands. While the 4 GB, 2 Core instance offers good performance at a lower cost, the 8 GB, 4 Core instance's additional resources make it more appropriate for CPU-intensive, I/O-heavy, or multi-threaded workloads. For developers seeking a balance between performance and budget, the 4 GB, 2 Core instance remains a strong option for lighter tasks, whereas the 8 GB, 4 Core instance is ideal for more demanding applications.

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.