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

vs.

Fresh benchmarks coming at ya. Today I've spun up some brand new instance from Vultr and ran some benchmarks. Each instance was spun up with Ubuntu 24.04 LTS x64 and were created in or around the New York / New Jersey area. Without further ado, here's the results.

Overview

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance AMD (4 GB, 2 Cores)
Last Benchmarked Thu, 02 Apr 2026 22:00:52 GMT Fri, 03 Apr 2026 10:00:52 GMT
Linux Distro Ubuntu 24.04 LTS x64 Ubuntu 24.04 LTS x64
Kernel Version 6.8.0-107-generic 6.8.0-107-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 $40.00 $24.00
RAM (GB) 8 4
CPU Cores 4 2
Storage (TB) 160 100
Storage Type SSD NVMe
Transfer (TB) 4 5

CPU

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance AMD (4 GB, 2 Cores)
Vendor GenuineIntel AuthenticAMD
Model Name Intel Xeon Processor (Skylake, IBRS) AMD EPYC-Genoa Processor
Clock Speed (MHz) 2,593.90 3,250.02
CPU Cache Size (KB) 16,384.00 1,024.00
BogoMips 5,187.80 6,500.03
Events per Second 1,034.72 4,139.70
Minimum Latency (ms) 0.88 0.22
Average Latency (ms) 0.96 0.24
Maximum Latency (ms) 4.17 2.3
95th Percentile Latency (ms) 1.18 0.27

Memory

Memory Read

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance AMD (4 GB, 2 Cores)
Operations per second 3,899,848.11 6,384,949.59
Mebibytes per second 3,808.45 6,235.30
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 1.16 1.06
95th Percentile Latency (ms) 0 0

Memory Write

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance AMD (4 GB, 2 Cores)
Operations per second 3,892,215.48 6,463,195.23
Mebibytes per second 3,800.99 6,311.71
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 1.22 0.65
95th Percentile Latency (ms) 0 0

File I/O

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance AMD (4 GB, 2 Cores)
Reads per Second 3,639.96 6,410.78
Writes per Second 2,426.64 4,273.85
Fsyncs per Second 7,775.52 13,688.92
Read Mebibytes per Second 56.87 100.17
Written Mebibytes per Second 37.92 66.78
Minimum Latency (ms) 0 0
Average Latency (ms) 0.07 0.04
Maximum Latency (ms) 27.8 12.76
95th Percentile Latency (ms) 0.24 0.14

Mutex

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance AMD (4 GB, 2 Cores)
Minimum Latency (ms) 297.90 829.08
Average Latency (ms) 459.99 880.59
Maximum Latency (ms) 530.08 921.34
95th Percentile Latency (ms) 530.08 926.33

MySQL

MySQL Read-only

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance AMD (4 GB, 2 Cores)
Transactions per second 4,685.00 8,493.00
Queries per second 46,850.00 84,930.00
Minimum Latency (ms) 1.28 0.86
Average Latency (ms) 2.13 1.18
Maximum Latency (ms) 6.82 3.6
95th Percentile Latency (ms) 2.81 1.47

MySQL Write-only

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance AMD (4 GB, 2 Cores)
Transactions per second 4,112.00 7,390.00
Queries per second 41,120.00 73,900.00
Minimum Latency (ms) 1.29 0.85
Average Latency (ms) 2.43 1.35
Maximum Latency (ms) 11.97 7.03
95th Percentile Latency (ms) 3.25 1.86

MySQL Read/Write

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance AMD (4 GB, 2 Cores)
Transactions per second 1,644.00 3,730.00
Queries per second 16,440.00 37,300.00
Minimum Latency (ms) 3.45 1.79
Average Latency (ms) 6.08 2.68
Maximum Latency (ms) 41.14 19.46
95th Percentile Latency (ms) 8.43 3.43

MySQL INSERT

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance AMD (4 GB, 2 Cores)
Transactions per second 5,109.00 11,228.00
Queries per second 51,090.00 112,280.00
Minimum Latency (ms) 0.85 0.46
Average Latency (ms) 1.95 0.89
Maximum Latency (ms) 30.24 10.08
95th Percentile Latency (ms) 2.57 1.23

MySQL Bulk INSERT

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance AMD (4 GB, 2 Cores)
Transactions per second 964,103.00 2,133,092.00
Queries per second 9,641,030.00 21,330,920.00
Minimum Latency (ms) 0 0
Average Latency (ms) 0.01 0
Maximum Latency (ms) 571.85 269.3
95th Percentile Latency (ms) 0 0

MySQL SELECT

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance AMD (4 GB, 2 Cores)
Transactions per second 126,707.00 175,252.00
Queries per second 1,267,070.00 1,752,520.00
Minimum Latency (ms) 0.04 0.02
Average Latency (ms) 0.08 0.06
Maximum Latency (ms) 2.86 1.58
95th Percentile Latency (ms) 0.11 0.09

MySQL SELECT (Random Points)

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance AMD (4 GB, 2 Cores)
Transactions per second 4,348.00 11,692.00
Queries per second 43,480.00 116,920.00
Minimum Latency (ms) 0.57 0.26
Average Latency (ms) 2.29 0.85
Maximum Latency (ms) 8.96 4.23
95th Percentile Latency (ms) 3.36 1.27

MySQL SELECT (Random Ranges)

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance AMD (4 GB, 2 Cores)
Transactions per second 3,809.00 10,810.00
Queries per second 38,090.00 108,100.00
Minimum Latency (ms) 0.71 0.19
Average Latency (ms) 2.62 0.92
Maximum Latency (ms) 10.56 5.82
95th Percentile Latency (ms) 4.74 1.37

MySQL UPDATE (Indexed)

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance AMD (4 GB, 2 Cores)
Transactions per second 5,588.00 10,619.00
Queries per second 55,880.00 106,190.00
Minimum Latency (ms) 0.95 0.5
Average Latency (ms) 1.79 0.94
Maximum Latency (ms) 24.03 6.61
95th Percentile Latency (ms) 2.52 1.32

MySQL UPDATE (Non-Indexed)

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance AMD (4 GB, 2 Cores)
Transactions per second 5,653.00 9,811.00
Queries per second 56,530.00 98,110.00
Minimum Latency (ms) 1.03 0.5
Average Latency (ms) 1.77 1.02
Maximum Latency (ms) 14.17 14.97
95th Percentile Latency (ms) 2.52 1.52

MySQL DELETE

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance AMD (4 GB, 2 Cores)
Transactions per second 36,427.00 103,619.00
Queries per second 364,270.00 1,036,190.00
Minimum Latency (ms) 0.05 0.02
Average Latency (ms) 0.27 0.1
Maximum Latency (ms) 32.09 12.74
95th Percentile Latency (ms) 1.58 0.17

Redis

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance AMD (4 GB, 2 Cores)
PING_INLINE per Second 46,296.29 56,401.58
PING_MBULK per Second 47,281.32 66,006.60
SET per Second 47,846.89 67,980.97
GET per Second 47,483.38 67,934.78
INCR per Second 46,468.40 65,061.81
LPUSH per Second 48,638.13 65,919.58
RPUSH per Second 45,126.35 64,432.99
LPOP per Second 42,517.01 58,139.54
RPOP per Second 46,750.82 67,613.25
SADD per Second 45,977.01 55,617.35
HSET per Second 45,808.52 56,753.69
SPOP per Second 43,630.02 55,096.42
ZADD per Second 46,598.32 54,824.56
ZPOPMIN per Second 46,641.79 55,834.73
LRANGE_100 (first 100 elements) per Second 26,281.21 48,285.85
LRANGE_300 (first 300 elements) per Second 13,104.44 28,034.76
LRANGE_500 (first 500 elements) per Second 8,483.20 21,968.37
LRANGE_600 (first 600 elements) per Second 7,532.39 19,538.88
MSET (10 keys) per Second 46,253.47 56,497.18

Redis Average Latency (ms)

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance AMD (4 GB, 2 Cores)
PING_INLINE0.570.48
PING_MBULK0.550.39
SET0.550.39
GET0.550.39
INCR0.580.40
LPUSH0.550.39
RPUSH0.580.40
LPOP0.620.46
RPOP0.580.39
SADD0.570.47
HSET0.570.47
SPOP0.590.48
ZADD0.560.48
ZPOPMIN0.560.47
LRANGE_100 (first 100 elements)1.070.61
LRANGE_300 (first 300 elements)2.291.01
LRANGE_500 (first 500 elements)3.681.27
LRANGE_600 (first 600 elements)4.281.41
MSET (10 keys)0.700.48

Conclusion

From the friendly robots:

After analyzing the benchmark results for both Vultr instances, it's clear that the Cloud Compute (8 GB, 4 Cores) excels in memory operations, Redis performance, and overall CPU tasks, likely due to the higher number of cores and larger RAM. However, the High Performance AMD (4 GB, 2 Cores) instance, while having fewer resources, shines in terms of raw CPU speed, better thread fairness in file I/O operations, and superior Redis performance, probably because of its AMD EPYC processor. For developers needing high memory throughput and CPU efficiency for complex tasks, the Cloud Compute instance is optimal. Conversely, if a project prioritizes faster raw CPU performance, especially for single-threaded applications, or requires lower latency in file I/O, the High Performance AMD instance might be more suitable.

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.