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

vs.

Fresh benchmarks coming at ya. Today I've spun up some 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 or around the New York / New Jersey area. Time to see who showed up today.

Overview

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance AMD (2 GB)
Last Benchmarked Sat, 23 May 2026 11:00:52 GMT Sat, 23 May 2026 09: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 $40.00 $12.00
RAM (GB) 8 2
CPU Cores 4 1
Storage (TB) 160 50
Storage Type SSD NVMe
Transfer (TB) 4 3

CPU

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance AMD (2 GB)
Vendor GenuineIntel AuthenticAMD
Model Name Intel Xeon Processor (Skylake, IBRS) AMD EPYC-Genoa Processor
Clock Speed (MHz) 2,593.90 2,900.01
CPU Cache Size (KB) 16,384.00 1,024.00
BogoMips 5,187.80 5,800.01
Events per Second 1,100.82 4,585.16
Minimum Latency (ms) 0.88 0.21
Average Latency (ms) 0.91 0.22
Maximum Latency (ms) 1.56 3.94
95th Percentile Latency (ms) 0.97 0.23

Memory

Memory Read

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance AMD (2 GB)
Operations per second 3,685,781.23 7,434,616.41
Mebibytes per second 3,599.40 7,260.37
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 1.03 0.86
95th Percentile Latency (ms) 0 0

Memory Write

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance AMD (2 GB)
Operations per second 3,590,629.63 7,494,205.81
Mebibytes per second 3,506.47 7,318.56
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 1.16 0.73
95th Percentile Latency (ms) 0 0

File I/O

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance AMD (2 GB)
Reads per Second 4,999.39 5,294.77
Writes per Second 3,332.93 3,529.85
Fsyncs per Second 10,670.47 11,297.81
Read Mebibytes per Second 78.12 82.73
Written Mebibytes per Second 52.08 55.15
Minimum Latency (ms) 0 0
Average Latency (ms) 0.05 0.05
Maximum Latency (ms) 37.52 3.08
95th Percentile Latency (ms) 0.18 0.11

Mutex

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance AMD (2 GB)
Minimum Latency (ms) 369.37 1,235.37
Average Latency (ms) 416.22 1,244.43
Maximum Latency (ms) 441.77 1,250.23
95th Percentile Latency (ms) 442.73 1,258.08

MySQL

MySQL Read-only

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance AMD (2 GB)
Transactions per second 5,144.00 12,805.00
Queries per second 51,440.00 128,050.00
Minimum Latency (ms) 1.72 0.7
Average Latency (ms) 1.94 0.78
Maximum Latency (ms) 7.67 2.41
95th Percentile Latency (ms) 2.35 0.87

MySQL Write-only

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance AMD (2 GB)
Transactions per second 5,108.00 10,098.00
Queries per second 51,080.00 100,980.00
Minimum Latency (ms) 1.15 0.65
Average Latency (ms) 1.96 0.99
Maximum Latency (ms) 12.52 3.19
95th Percentile Latency (ms) 2.71 1.37

MySQL Read/Write

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance AMD (2 GB)
Transactions per second 2,247.00 5,003.00
Queries per second 22,470.00 50,030.00
Minimum Latency (ms) 3.08 1.57
Average Latency (ms) 4.45 2
Maximum Latency (ms) 29.7 4.8
95th Percentile Latency (ms) 5.28 2.48

MySQL INSERT

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance AMD (2 GB)
Transactions per second 7,630.00 17,395.00
Queries per second 76,300.00 173,950.00
Minimum Latency (ms) 0.71 0.43
Average Latency (ms) 1.31 0.57
Maximum Latency (ms) 29.81 2.29
95th Percentile Latency (ms) 1.55 0.7

MySQL Bulk INSERT

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance AMD (2 GB)
Transactions per second 898,571.00 2,482,592.00
Queries per second 8,985,710.00 24,825,920.00
Minimum Latency (ms) 0 0
Average Latency (ms) 0.01 0
Maximum Latency (ms) 505.86 222.92
95th Percentile Latency (ms) 0 0

MySQL SELECT

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance AMD (2 GB)
Transactions per second 149,465.00 334,403.00
Queries per second 1,494,650.00 3,344,030.00
Minimum Latency (ms) 0.05 0.02
Average Latency (ms) 0.07 0.03
Maximum Latency (ms) 1.22 0.84
95th Percentile Latency (ms) 0.09 0.04

MySQL SELECT (Random Points)

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance AMD (2 GB)
Transactions per second 4,249.00 13,826.00
Queries per second 42,490.00 138,260.00
Minimum Latency (ms) 0.83 0.24
Average Latency (ms) 2.35 0.72
Maximum Latency (ms) 6.6 3.13
95th Percentile Latency (ms) 3.02 0.92

MySQL SELECT (Random Ranges)

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance AMD (2 GB)
Transactions per second 2,637.00 14,590.00
Queries per second 26,370.00 145,900.00
Minimum Latency (ms) 0.94 0.19
Average Latency (ms) 3.79 0.68
Maximum Latency (ms) 6.3 2.25
95th Percentile Latency (ms) 5.09 0.89

MySQL UPDATE (Indexed)

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance AMD (2 GB)
Transactions per second 7,166.00 15,605.00
Queries per second 71,660.00 156,050.00
Minimum Latency (ms) 0.7 0.41
Average Latency (ms) 1.39 0.64
Maximum Latency (ms) 28.84 10.7
95th Percentile Latency (ms) 1.79 0.97

MySQL UPDATE (Non-Indexed)

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance AMD (2 GB)
Transactions per second 7,661.00 15,795.00
Queries per second 76,610.00 157,950.00
Minimum Latency (ms) 0.7 0.43
Average Latency (ms) 1.3 0.63
Maximum Latency (ms) 33.97 1.99
95th Percentile Latency (ms) 1.58 0.9

MySQL DELETE

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance AMD (2 GB)
Transactions per second 69,690.00 211,730.00
Queries per second 696,900.00 2,117,300.00
Minimum Latency (ms) 0.05 0.02
Average Latency (ms) 0.14 0.05
Maximum Latency (ms) 27.73 2.61
95th Percentile Latency (ms) 0.87 0.07

Redis

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance AMD (2 GB)
PING_INLINE per Second 54,436.58 42,607.59
PING_MBULK per Second 48,828.12 42,881.64
SET per Second 51,572.98 42,680.32
GET per Second 48,239.27 43,346.34
INCR per Second 52,328.62 43,047.79
LPUSH per Second 45,454.54 42,735.04
RPUSH per Second 49,751.24 43,047.79
LPOP per Second 53,390.28 42,535.09
RPOP per Second 53,648.07 42,625.75
SADD per Second 48,285.85 43,084.88
HSET per Second 51,493.30 43,290.04
SPOP per Second 52,910.05 38,402.46
ZADD per Second 53,504.55 43,010.75
ZPOPMIN per Second 53,590.57 43,554.01
LRANGE_100 (first 100 elements) per Second 28,645.09 33,500.84
LRANGE_300 (first 300 elements) per Second 13,131.98 22,172.95
LRANGE_500 (first 500 elements) per Second 8,529.51 16,417.67
LRANGE_600 (first 600 elements) per Second 7,479.99 14,609.20
MSET (10 keys) per Second 49,212.60 40,916.53

Redis Average Latency (ms)

Vultr – Cloud Compute (8 GB, 4 Cores) Vultr – High Performance AMD (2 GB)
PING_INLINE0.470.78
PING_MBULK0.530.77
SET0.500.79
GET0.540.78
INCR0.490.78
LPUSH0.580.78
RPUSH0.520.78
LPOP0.490.79
RPOP0.480.79
SADD0.540.78
HSET0.530.78
SPOP0.490.89
ZADD0.480.78
ZPOPMIN0.480.77
LRANGE_100 (first 100 elements)0.911.00
LRANGE_300 (first 300 elements)1.941.49
LRANGE_500 (first 500 elements)3.002.05
LRANGE_600 (first 600 elements)3.432.27
MSET (10 keys)0.770.84

Conclusion

From the friendly robots:

Both instances from Vultr show robust performance metrics but cater to different use cases based on their configuration and benchmarks. The Cloud Compute (8 GB, 4 Cores) instance excels with higher RAM and CPU cores, showcasing superior Redis performance metrics, such as higher requests per second and lower latency across various operations, alongside impressive CPU and I/O throughput. It's ideal for CPU-intensive workloads, large-scale data processing, and environments requiring high memory availability. In contrast, the High Performance AMD (2 GB) instance, while less powerful in terms of RAM and CPU cores, provides commendable benchmarks for single-core operations, making it suitable for less resource-intensive applications, particularly where cost-effectiveness and modest performance are prioritized over higher memory and multi-core processing demands. This instance is well-suited for small to medium applications, development environments, or scenarios where a single high-performing core suffices.

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.