Vultr Cloud Compute (4 GB, 2 Cores) vs. Vultr High Performance AMD (2 GB, 2 Cores)

vs.

Welcome to another round of the VPS Showdown. Today I've spun up brand new instance from Vultr and did some benchmarking. Each instance was running 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 – High Performance AMD (2 GB, 2 Cores)
Last Benchmarked Sat, 30 May 2026 05:00:52 GMT Sun, 31 May 2026 07: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 $18.00
RAM (GB) 4 2
CPU Cores 2 2
Storage (TB) 80 60
Storage Type SSD NVMe
Transfer (TB) 3 4

CPU

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Performance AMD (2 GB, 2 Cores)
Vendor GenuineIntel AuthenticAMD
Model Name Intel Core Processor (Skylake, IBRS, no TSX) AMD EPYC-Genoa Processor
Clock Speed (MHz) 3,792.00 2,899.99
CPU Cache Size (KB) 16,384.00 1,024.00
BogoMips 7,583.99 5,799.98
Events per Second 1,581.00 4,648.14
Minimum Latency (ms) 0.62 0.2
Average Latency (ms) 0.63 0.21
Maximum Latency (ms) 1.25 1.26
95th Percentile Latency (ms) 0.67 0.23

Memory

Memory Read

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Performance AMD (2 GB, 2 Cores)
Operations per second 7,740,670.12 7,548,502.85
Mebibytes per second 7,559.25 7,371.58
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 0.08 0.08
95th Percentile Latency (ms) 0 0

Memory Write

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Performance AMD (2 GB, 2 Cores)
Operations per second 7,498,489.66 7,544,807.09
Mebibytes per second 7,322.74 7,367.98
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 0.24 0.12
95th Percentile Latency (ms) 0 0

File I/O

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Performance AMD (2 GB, 2 Cores)
Reads per Second 7,862.01 5,114.79
Writes per Second 5,241.34 3,409.86
Fsyncs per Second 16,779.39 10,914.44
Read Mebibytes per Second 122.84 79.92
Written Mebibytes per Second 81.90 53.28
Minimum Latency (ms) 0 0
Average Latency (ms) 0.03 0.05
Maximum Latency (ms) 2.28 3.7
95th Percentile Latency (ms) 0.12 0.12

Mutex

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Performance AMD (2 GB, 2 Cores)
Minimum Latency (ms) 520.27 574.03
Average Latency (ms) 548.31 637.47
Maximum Latency (ms) 569.21 663.74
95th Percentile Latency (ms) 569.67 657.93

MySQL

MySQL Read-only

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Performance AMD (2 GB, 2 Cores)
Transactions per second 10,390.00 9,622.00
Queries per second 103,900.00 96,220.00
Minimum Latency (ms) 0.87 0.73
Average Latency (ms) 0.96 1.04
Maximum Latency (ms) 2.8 2.22
95th Percentile Latency (ms) 1.06 1.12

MySQL Write-only

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Performance AMD (2 GB, 2 Cores)
Transactions per second 10,176.00 9,585.00
Queries per second 101,760.00 95,850.00
Minimum Latency (ms) 0.66 0.8
Average Latency (ms) 0.98 1.04
Maximum Latency (ms) 2.82 2.18
95th Percentile Latency (ms) 1.27 1.32

MySQL Read/Write

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Performance AMD (2 GB, 2 Cores)
Transactions per second 4,990.00 4,686.00
Queries per second 49,900.00 46,860.00
Minimum Latency (ms) 1.6 1.57
Average Latency (ms) 2 2.13
Maximum Latency (ms) 3.19 4.26
95th Percentile Latency (ms) 2.3 2.52

MySQL INSERT

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Performance AMD (2 GB, 2 Cores)
Transactions per second 16,211.00 15,965.00
Queries per second 162,110.00 159,650.00
Minimum Latency (ms) 0.37 0.45
Average Latency (ms) 0.62 0.62
Maximum Latency (ms) 16.01 2.23
95th Percentile Latency (ms) 0.83 0.74

MySQL Bulk INSERT

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Performance AMD (2 GB, 2 Cores)
Transactions per second 2,395,217.00 3,065,092.00
Queries per second 23,952,170.00 30,650,920.00
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 207.28 208.51
95th Percentile Latency (ms) 0 0

MySQL SELECT

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Performance AMD (2 GB, 2 Cores)
Transactions per second 229,866.00 217,035.00
Queries per second 2,298,660.00 2,170,350.00
Minimum Latency (ms) 0.03 0.02
Average Latency (ms) 0.04 0.05
Maximum Latency (ms) 0.68 0.61
95th Percentile Latency (ms) 0.06 0.06

MySQL SELECT (Random Points)

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Performance AMD (2 GB, 2 Cores)
Transactions per second 11,703.00 14,818.00
Queries per second 117,030.00 148,180.00
Minimum Latency (ms) 0.26 0.24
Average Latency (ms) 0.85 0.67
Maximum Latency (ms) 2.08 1.94
95th Percentile Latency (ms) 1.1 0.86

MySQL SELECT (Random Ranges)

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Performance AMD (2 GB, 2 Cores)
Transactions per second 10,274.00 14,341.00
Queries per second 102,740.00 143,410.00
Minimum Latency (ms) 0.32 0.27
Average Latency (ms) 0.97 0.7
Maximum Latency (ms) 2.94 1.67
95th Percentile Latency (ms) 1.25 0.89

MySQL UPDATE (Indexed)

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Performance AMD (2 GB, 2 Cores)
Transactions per second 16,308.00 14,864.00
Queries per second 163,080.00 148,640.00
Minimum Latency (ms) 0.39 0.47
Average Latency (ms) 0.61 0.67
Maximum Latency (ms) 1.69 2.36
95th Percentile Latency (ms) 0.81 0.87

MySQL UPDATE (Non-Indexed)

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Performance AMD (2 GB, 2 Cores)
Transactions per second 16,200.00 15,284.00
Queries per second 162,000.00 152,840.00
Minimum Latency (ms) 0.38 0.46
Average Latency (ms) 0.62 0.65
Maximum Latency (ms) 1.95 1.65
95th Percentile Latency (ms) 0.83 0.83

MySQL DELETE

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Performance AMD (2 GB, 2 Cores)
Transactions per second 151,265.00 151,536.00
Queries per second 1,512,650.00 1,515,360.00
Minimum Latency (ms) 0.03 0.02
Average Latency (ms) 0.07 0.07
Maximum Latency (ms) 1.91 4.83
95th Percentile Latency (ms) 0.08 0.08

Redis

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Performance AMD (2 GB, 2 Cores)
PING_INLINE per Second 87,642.41 55,991.04
PING_MBULK per Second 88,105.73 57,903.88
SET per Second 89,206.06 57,703.40
GET per Second 88,028.16 57,703.40
INCR per Second 90,497.73 57,372.34
LPUSH per Second 90,909.09 57,836.90
RPUSH per Second 90,909.09 58,173.36
LPOP per Second 89,847.26 58,343.06
RPOP per Second 89,605.73 58,343.06
SADD per Second 88,809.95 58,241.12
HSET per Second 90,334.23 58,858.15
SPOP per Second 90,090.09 58,892.82
ZADD per Second 91,240.88 57,504.31
ZPOPMIN per Second 90,415.91 57,870.37
LRANGE_100 (first 100 elements) per Second 66,755.67 49,236.83
LRANGE_300 (first 300 elements) per Second 35,435.86 34,818.94
LRANGE_500 (first 500 elements) per Second 24,937.65 26,766.60
LRANGE_600 (first 600 elements) per Second 22,831.05 24,207.21
MSET (10 keys) per Second 90,991.81 58,548.01

Redis Average Latency (ms)

Vultr – Cloud Compute (4 GB, 2 Cores) Vultr – High Performance AMD (2 GB, 2 Cores)
PING_INLINE0.300.48
PING_MBULK0.290.44
SET0.290.45
GET0.290.45
INCR0.290.45
LPUSH0.290.44
RPUSH0.280.44
LPOP0.290.44
RPOP0.290.44
SADD0.290.44
HSET0.290.44
SPOP0.290.44
ZADD0.280.45
ZPOPMIN0.290.44
LRANGE_100 (first 100 elements)0.390.53
LRANGE_300 (first 300 elements)0.730.74
LRANGE_500 (first 500 elements)1.030.95
LRANGE_600 (first 600 elements)1.121.05
MSET (10 keys)0.290.44

Conclusion

From the friendly robots:

Comparing the two Vultr instances, the Cloud Compute (4 GB, 2 Cores) outperforms in most metrics with higher RPS rates, lower latencies, and better throughput across CPU, memory, file I/O, and database operations. The High Performance AMD (2 GB, 2 Cores) lags slightly behind, with fewer RAM and cores, which affects its performance in complex tasks and larger data handling scenarios. While the AMD instance excels in certain aspects like mutex operations and has NVMe support, the Cloud Compute instance's superior overall performance makes it more suitable for CPU-intensive, I/O-heavy workloads and general-purpose computing tasks where higher RAM and better throughput are beneficial. For developers needing robust and efficient performance, the Cloud Compute instance is recommended.

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.