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

vs.

My friend, I'm so glad you're here! Today I've spun up brand new instance from Vultr to run some benchmarks on. All instances were spun up with Ubuntu 24.04 LTS x64 and were created in the New York area (or close to it). Without further ado, here's the results.

Overview

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

CPU

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (2 GB)
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,615.78
Minimum Latency (ms) 0.63 0.2
Average Latency (ms) 0.67 0.22
Maximum Latency (ms) 1.95 2.45
95th Percentile Latency (ms) 0.77 0.22

Memory

Memory Read

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (2 GB)
Operations per second 6,401,389.08 7,453,432.72
Mebibytes per second 6,251.36 7,278.74
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 0.23 0.64
95th Percentile Latency (ms) 0 0

Memory Write

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (2 GB)
Operations per second 6,411,085.35 7,525,529.67
Mebibytes per second 6,260.83 7,349.15
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 0.18 2.59
95th Percentile Latency (ms) 0 0

File I/O

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (2 GB)
Reads per Second 4,345.71 5,289.54
Writes per Second 2,897.07 3,526.36
Fsyncs per Second 9,273.19 11,292.45
Read Mebibytes per Second 67.90 82.65
Written Mebibytes per Second 45.27 55.10
Minimum Latency (ms) 0 0
Average Latency (ms) 0.06 0.05
Maximum Latency (ms) 2.92 1.64
95th Percentile Latency (ms) 0.17 0.11

Mutex

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (2 GB)
Minimum Latency (ms) 214.63 1,230.79
Average Latency (ms) 569.72 1,237.29
Maximum Latency (ms) 636.55 1,243.30
95th Percentile Latency (ms) 634.66 1,235.62

MySQL

MySQL Read-only

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (2 GB)
Transactions per second 8,015.00 12,975.00
Queries per second 80,150.00 129,750.00
Minimum Latency (ms) 0.92 0.72
Average Latency (ms) 1.25 0.77
Maximum Latency (ms) 5.5 2.93
95th Percentile Latency (ms) 1.86 0.81

MySQL Write-only

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (2 GB)
Transactions per second 8,497.00 10,208.00
Queries per second 84,970.00 102,080.00
Minimum Latency (ms) 0.76 0.66
Average Latency (ms) 1.17 0.98
Maximum Latency (ms) 3.04 2.91
95th Percentile Latency (ms) 1.55 1.34

MySQL Read/Write

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (2 GB)
Transactions per second 3,726.00 5,168.00
Queries per second 37,260.00 51,680.00
Minimum Latency (ms) 1.78 1.57
Average Latency (ms) 2.68 1.93
Maximum Latency (ms) 5.82 5.05
95th Percentile Latency (ms) 3.43 2.35

MySQL INSERT

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (2 GB)
Transactions per second 15,028.00 17,481.00
Queries per second 150,280.00 174,810.00
Minimum Latency (ms) 0.41 0.43
Average Latency (ms) 0.66 0.57
Maximum Latency (ms) 2.42 2.38
95th Percentile Latency (ms) 0.86 0.69

MySQL Bulk INSERT

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (2 GB)
Transactions per second 1,696,217.00 2,657,342.00
Queries per second 16,962,170.00 26,573,420.00
Minimum Latency (ms) 0 0
Average Latency (ms) 0.01 0
Maximum Latency (ms) 283.37 213.16
95th Percentile Latency (ms) 0 0

MySQL SELECT

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (2 GB)
Transactions per second 201,989.00 341,574.00
Queries per second 2,019,890.00 3,415,740.00
Minimum Latency (ms) 0.03 0.02
Average Latency (ms) 0.05 0.03
Maximum Latency (ms) 0.51 1.05
95th Percentile Latency (ms) 0.07 0.04

MySQL SELECT (Random Points)

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (2 GB)
Transactions per second 8,025.00 14,700.00
Queries per second 80,250.00 147,000.00
Minimum Latency (ms) 0.35 0.16
Average Latency (ms) 1.24 0.68
Maximum Latency (ms) 3.55 3.58
95th Percentile Latency (ms) 2.07 0.86

MySQL SELECT (Random Ranges)

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (2 GB)
Transactions per second 8,336.00 14,474.00
Queries per second 83,360.00 144,740.00
Minimum Latency (ms) 0.4 0.23
Average Latency (ms) 1.2 0.69
Maximum Latency (ms) 4.25 1.96
95th Percentile Latency (ms) 2.22 0.89

MySQL UPDATE (Indexed)

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (2 GB)
Transactions per second 13,858.00 15,959.00
Queries per second 138,580.00 159,590.00
Minimum Latency (ms) 0.42 0.42
Average Latency (ms) 0.72 0.63
Maximum Latency (ms) 6.33 11.63
95th Percentile Latency (ms) 0.95 0.92

MySQL UPDATE (Non-Indexed)

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (2 GB)
Transactions per second 14,587.00 16,288.00
Queries per second 145,870.00 162,880.00
Minimum Latency (ms) 0.4 0.43
Average Latency (ms) 0.68 0.61
Maximum Latency (ms) 11.69 4.08
95th Percentile Latency (ms) 0.9 0.87

MySQL DELETE

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (2 GB)
Transactions per second 129,013.00 213,800.00
Queries per second 1,290,130.00 2,138,000.00
Minimum Latency (ms) 0.03 0.02
Average Latency (ms) 0.08 0.05
Maximum Latency (ms) 2.61 1.96
95th Percentile Latency (ms) 0.09 0.07

Redis

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (2 GB)
PING_INLINE per Second 78,247.26 42,992.26
PING_MBULK per Second 74,738.41 43,744.53
SET per Second 77,041.60 43,365.13
GET per Second 83,333.33 43,459.36
INCR per Second 80,971.66 43,497.17
LPUSH per Second 79,113.92 42,900.04
RPUSH per Second 77,160.49 43,308.79
LPOP per Second 81,499.59 43,029.26
RPOP per Second 82,440.23 42,900.04
SADD per Second 80,192.46 43,290.04
HSET per Second 83,612.04 43,084.88
SPOP per Second 85,034.02 43,365.13
ZADD per Second 83,263.95 42,936.88
ZPOPMIN per Second 82,987.55 38,226.30
LRANGE_100 (first 100 elements) per Second 55,555.56 33,478.41
LRANGE_300 (first 300 elements) per Second 28,851.70 21,687.27
LRANGE_500 (first 500 elements) per Second 19,391.12 16,204.83
LRANGE_600 (first 600 elements) per Second 17,211.71 14,480.16
MSET (10 keys) per Second 80,256.82 41,152.26

Redis Average Latency (ms)

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (2 GB)
PING_INLINE0.340.77
PING_MBULK0.350.76
SET0.340.77
GET0.320.77
INCR0.320.77
LPUSH0.340.78
RPUSH0.340.77
LPOP0.320.78
RPOP0.320.78
SADD0.320.77
HSET0.310.78
SPOP0.300.77
ZADD0.310.78
ZPOPMIN0.310.89
LRANGE_100 (first 100 elements)0.541.00
LRANGE_300 (first 300 elements)1.111.51
LRANGE_500 (first 500 elements)1.622.06
LRANGE_600 (first 600 elements)1.842.31
MSET (10 keys)0.380.82

Conclusion

From the friendly robots:

After analyzing the benchmark results from both Vultr instances, the Cloud Compute (2 GB, 2 Cores) generally offers better performance across a wider range of metrics, especially in CPU-intensive and memory-bound tasks, where it exhibits higher throughput and lower latency in tasks such as Redis commands and MySQL operations. The High Performance AMD (2 GB) instance, while boasting a single, higher-frequency AMD EPYC core, falls behind in overall performance for most benchmarks, particularly in throughput and latency in Redis operations and file I/O tasks. Thus, the Cloud Compute (2 GB, 2 Cores) is better suited for workloads that benefit from multiple cores and higher memory bandwidth, such as web servers, lightweight applications, and databases. The High Performance AMD (2 GB) may appeal to specific use cases that heavily benefit from a single high-frequency core, such as certain specialized compute tasks or where cost is a more significant concern than raw throughput.

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.