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

vs.

New day, new benchmarks. Today I've spun up some brand new instance from Vultr and ran my world famous suite of benchmarking scripts. All instances were spun up with Ubuntu 24.04 LTS x64 and were created in or around the New York / New Jersey area. Let's get into the numbers.

Overview

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

CPU

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (4 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.97
CPU Cache Size (KB) 16,384.00 1,024.00
BogoMips 7,583.99 5,799.93
Events per Second 1,481.60 4,658.11
Minimum Latency (ms) 0.63 0.21
Average Latency (ms) 0.67 0.21
Maximum Latency (ms) 1.95 0.53
95th Percentile Latency (ms) 0.77 0.23

Memory

Memory Read

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (4 GB, 2 Cores)
Operations per second 6,401,389.08 7,575,653.76
Mebibytes per second 6,251.36 7,398.10
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 0.23 0.11
95th Percentile Latency (ms) 0 0

Memory Write

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (4 GB, 2 Cores)
Operations per second 6,411,085.35 7,568,193.98
Mebibytes per second 6,260.83 7,390.81
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 0.18 0.12
95th Percentile Latency (ms) 0 0

File I/O

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (4 GB, 2 Cores)
Reads per Second 4,345.71 7,987.51
Writes per Second 2,897.07 5,325.00
Fsyncs per Second 9,273.19 17,048.51
Read Mebibytes per Second 67.90 124.80
Written Mebibytes per Second 45.27 83.20
Minimum Latency (ms) 0 0
Average Latency (ms) 0.06 0.03
Maximum Latency (ms) 2.92 6.39
95th Percentile Latency (ms) 0.17 0.1

Mutex

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (4 GB, 2 Cores)
Minimum Latency (ms) 214.63 486.79
Average Latency (ms) 569.72 633.21
Maximum Latency (ms) 636.55 662.57
95th Percentile Latency (ms) 634.66 657.93

MySQL

MySQL Read-only

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (4 GB, 2 Cores)
Transactions per second 8,015.00 10,078.00
Queries per second 80,150.00 100,780.00
Minimum Latency (ms) 0.92 0.73
Average Latency (ms) 1.25 0.99
Maximum Latency (ms) 5.5 2.1
95th Percentile Latency (ms) 1.86 1.04

MySQL Write-only

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (4 GB, 2 Cores)
Transactions per second 8,497.00 9,972.00
Queries per second 84,970.00 99,720.00
Minimum Latency (ms) 0.76 0.69
Average Latency (ms) 1.17 1
Maximum Latency (ms) 3.04 2.46
95th Percentile Latency (ms) 1.55 1.27

MySQL Read/Write

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (4 GB, 2 Cores)
Transactions per second 3,726.00 4,931.00
Queries per second 37,260.00 49,310.00
Minimum Latency (ms) 1.78 1.69
Average Latency (ms) 2.68 2.03
Maximum Latency (ms) 5.82 4.6
95th Percentile Latency (ms) 3.43 2.35

MySQL INSERT

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (4 GB, 2 Cores)
Transactions per second 15,028.00 16,374.00
Queries per second 150,280.00 163,740.00
Minimum Latency (ms) 0.41 0.45
Average Latency (ms) 0.66 0.61
Maximum Latency (ms) 2.42 2.27
95th Percentile Latency (ms) 0.86 0.73

MySQL Bulk INSERT

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (4 GB, 2 Cores)
Transactions per second 1,696,217.00 3,065,092.00
Queries per second 16,962,170.00 30,650,920.00
Minimum Latency (ms) 0 0
Average Latency (ms) 0.01 0
Maximum Latency (ms) 283.37 202.5
95th Percentile Latency (ms) 0 0

MySQL SELECT

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (4 GB, 2 Cores)
Transactions per second 201,989.00 228,801.00
Queries per second 2,019,890.00 2,288,010.00
Minimum Latency (ms) 0.03 0.02
Average Latency (ms) 0.05 0.04
Maximum Latency (ms) 0.51 0.76
95th Percentile Latency (ms) 0.07 0.05

MySQL SELECT (Random Points)

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (4 GB, 2 Cores)
Transactions per second 8,025.00 14,971.00
Queries per second 80,250.00 149,710.00
Minimum Latency (ms) 0.35 0.24
Average Latency (ms) 1.24 0.67
Maximum Latency (ms) 3.55 2.18
95th Percentile Latency (ms) 2.07 0.84

MySQL SELECT (Random Ranges)

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (4 GB, 2 Cores)
Transactions per second 8,336.00 14,347.00
Queries per second 83,360.00 143,470.00
Minimum Latency (ms) 0.4 0.22
Average Latency (ms) 1.2 0.7
Maximum Latency (ms) 4.25 1.42
95th Percentile Latency (ms) 2.22 0.89

MySQL UPDATE (Indexed)

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (4 GB, 2 Cores)
Transactions per second 13,858.00 15,756.00
Queries per second 138,580.00 157,560.00
Minimum Latency (ms) 0.42 0.46
Average Latency (ms) 0.72 0.63
Maximum Latency (ms) 6.33 2.03
95th Percentile Latency (ms) 0.95 0.83

MySQL UPDATE (Non-Indexed)

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (4 GB, 2 Cores)
Transactions per second 14,587.00 16,201.00
Queries per second 145,870.00 162,010.00
Minimum Latency (ms) 0.4 0.45
Average Latency (ms) 0.68 0.62
Maximum Latency (ms) 11.69 1.59
95th Percentile Latency (ms) 0.9 0.77

MySQL DELETE

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (4 GB, 2 Cores)
Transactions per second 129,013.00 163,015.00
Queries per second 1,290,130.00 1,630,150.00
Minimum Latency (ms) 0.03 0.02
Average Latency (ms) 0.08 0.06
Maximum Latency (ms) 2.61 3.17
95th Percentile Latency (ms) 0.09 0.08

Redis

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (4 GB, 2 Cores)
PING_INLINE per Second 78,247.26 57,372.34
PING_MBULK per Second 74,738.41 58,719.91
SET per Second 77,041.60 59,276.82
GET per Second 83,333.33 59,031.88
INCR per Second 80,971.66 59,136.61
LPUSH per Second 79,113.92 58,616.65
RPUSH per Second 77,160.49 58,754.41
LPOP per Second 81,499.59 58,962.27
RPOP per Second 82,440.23 59,241.71
SADD per Second 80,192.46 58,892.82
HSET per Second 83,612.04 58,616.65
SPOP per Second 85,034.02 59,206.63
ZADD per Second 83,263.95 59,031.88
ZPOPMIN per Second 82,987.55 59,311.98
LRANGE_100 (first 100 elements) per Second 55,555.56 50,479.56
LRANGE_300 (first 300 elements) per Second 28,851.70 34,164.67
LRANGE_500 (first 500 elements) per Second 19,391.12 26,364.36
LRANGE_600 (first 600 elements) per Second 17,211.71 23,952.09
MSET (10 keys) per Second 80,256.82 59,031.88

Redis Average Latency (ms)

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (4 GB, 2 Cores)
PING_INLINE0.340.46
PING_MBULK0.350.44
SET0.340.44
GET0.320.44
INCR0.320.43
LPUSH0.340.44
RPUSH0.340.44
LPOP0.320.44
RPOP0.320.43
SADD0.320.44
HSET0.310.44
SPOP0.300.43
ZADD0.310.44
ZPOPMIN0.310.43
LRANGE_100 (first 100 elements)0.540.51
LRANGE_300 (first 300 elements)1.110.75
LRANGE_500 (first 500 elements)1.620.96
LRANGE_600 (first 600 elements)1.841.06
MSET (10 keys)0.380.44

Conclusion

From the friendly robots:

After analyzing the benchmark performance of both Vultr instances, the Cloud Compute (2 GB, 2 Cores) and the High Performance AMD (4 GB, 2 Cores), it is clear that the latter significantly outperforms the former across the board in terms of both raw performance metrics and efficiency. The AMD instance shows higher rates of requests per second (rps) for Redis operations, faster average processing latencies, and superior CPU performance, as evidenced by higher events per second and better thread fairness. The High Performance AMD server also outperforms in file I/O and memory operations, demonstrating faster read and write speeds, lower latencies, and higher throughput. However, the Cloud Compute instance has better thread fairness in mutex operations and slightly better CPU fairness. In terms of use cases, the High Performance AMD server is ideal for CPU-intensive, I/O-heavy workloads, and applications that require high concurrency and quick response times, while the Cloud Compute instance could still be suitable for more moderate workloads or cost-sensitive applications where the lower RAM and CPU might suffice.

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.