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

vs.

New day, new benchmarks. Today I've spun up some brand new instance from Vultr to run some benchmarks on. 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 (2 GB, 2 Cores) Vultr – High Performance AMD (8 GB, 4 Cores)
Last Benchmarked Mon, 11 May 2026 04:00:52 GMT Tue, 12 May 2026 03: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 $48.00
RAM (GB) 2 8
CPU Cores 2 4
Storage (TB) 65 180
Storage Type SSD NVMe
Transfer (TB) 3 6

CPU

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (8 GB, 4 Cores)
Vendor GenuineIntel AuthenticAMD
Model Name Intel Core Processor (Skylake, IBRS, no TSX) AMD EPYC-Genoa Processor
Clock Speed (MHz) 3,792.00 2,900.01
CPU Cache Size (KB) 16,384.00 1,024.00
BogoMips 7,583.99 5,800.01
Events per Second 1,481.60 4,660.86
Minimum Latency (ms) 0.63 0.21
Average Latency (ms) 0.67 0.21
Maximum Latency (ms) 1.95 0.52
95th Percentile Latency (ms) 0.77 0.22

Memory

Memory Read

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (8 GB, 4 Cores)
Operations per second 6,401,389.08 7,566,222.56
Mebibytes per second 6,251.36 7,388.89
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 0.23 0.05
95th Percentile Latency (ms) 0 0

Memory Write

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (8 GB, 4 Cores)
Operations per second 6,411,085.35 7,552,490.67
Mebibytes per second 6,260.83 7,375.48
Minimum Latency (ms) 0 0
Average Latency (ms) 0 0
Maximum Latency (ms) 0.18 0.6
95th Percentile Latency (ms) 0 0

File I/O

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (8 GB, 4 Cores)
Reads per Second 4,345.71 8,517.51
Writes per Second 2,897.07 5,678.37
Fsyncs per Second 9,273.19 18,177.50
Read Mebibytes per Second 67.90 133.09
Written Mebibytes per Second 45.27 88.72
Minimum Latency (ms) 0 0
Average Latency (ms) 0.06 0.03
Maximum Latency (ms) 2.92 0.61
95th Percentile Latency (ms) 0.17 0.1

Mutex

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (8 GB, 4 Cores)
Minimum Latency (ms) 214.63 165.23
Average Latency (ms) 569.72 285.68
Maximum Latency (ms) 636.55 342.72
95th Percentile Latency (ms) 634.66 344.08

MySQL

MySQL Read-only

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (8 GB, 4 Cores)
Transactions per second 8,015.00 10,922.00
Queries per second 80,150.00 109,220.00
Minimum Latency (ms) 0.92 0.75
Average Latency (ms) 1.25 0.92
Maximum Latency (ms) 5.5 1.51
95th Percentile Latency (ms) 1.86 1.03

MySQL Write-only

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (8 GB, 4 Cores)
Transactions per second 8,497.00 9,482.00
Queries per second 84,970.00 94,820.00
Minimum Latency (ms) 0.76 0.73
Average Latency (ms) 1.17 1.05
Maximum Latency (ms) 3.04 2.45
95th Percentile Latency (ms) 1.55 1.23

MySQL Read/Write

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (8 GB, 4 Cores)
Transactions per second 3,726.00 4,832.00
Queries per second 37,260.00 48,320.00
Minimum Latency (ms) 1.78 1.55
Average Latency (ms) 2.68 2.07
Maximum Latency (ms) 5.82 3.55
95th Percentile Latency (ms) 3.43 2.35

MySQL INSERT

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (8 GB, 4 Cores)
Transactions per second 15,028.00 15,179.00
Queries per second 150,280.00 151,790.00
Minimum Latency (ms) 0.41 0.45
Average Latency (ms) 0.66 0.66
Maximum Latency (ms) 2.42 13.61
95th Percentile Latency (ms) 0.86 0.81

MySQL Bulk INSERT

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (8 GB, 4 Cores)
Transactions per second 1,696,217.00 3,006,842.00
Queries per second 16,962,170.00 30,068,420.00
Minimum Latency (ms) 0 0
Average Latency (ms) 0.01 0
Maximum Latency (ms) 283.37 190.09
95th Percentile Latency (ms) 0 0

MySQL SELECT

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (8 GB, 4 Cores)
Transactions per second 201,989.00 235,314.00
Queries per second 2,019,890.00 2,353,140.00
Minimum Latency (ms) 0.03 0.02
Average Latency (ms) 0.05 0.04
Maximum Latency (ms) 0.51 0.31
95th Percentile Latency (ms) 0.07 0.05

MySQL SELECT (Random Points)

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (8 GB, 4 Cores)
Transactions per second 8,025.00 15,165.00
Queries per second 80,250.00 151,650.00
Minimum Latency (ms) 0.35 0.24
Average Latency (ms) 1.24 0.66
Maximum Latency (ms) 3.55 2.07
95th Percentile Latency (ms) 2.07 0.84

MySQL SELECT (Random Ranges)

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (8 GB, 4 Cores)
Transactions per second 8,336.00 14,400.00
Queries per second 83,360.00 144,000.00
Minimum Latency (ms) 0.4 0.17
Average Latency (ms) 1.2 0.69
Maximum Latency (ms) 4.25 1.68
95th Percentile Latency (ms) 2.22 0.9

MySQL UPDATE (Indexed)

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (8 GB, 4 Cores)
Transactions per second 13,858.00 14,535.00
Queries per second 138,580.00 145,350.00
Minimum Latency (ms) 0.42 0.47
Average Latency (ms) 0.72 0.69
Maximum Latency (ms) 6.33 2.07
95th Percentile Latency (ms) 0.95 0.86

MySQL UPDATE (Non-Indexed)

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (8 GB, 4 Cores)
Transactions per second 14,587.00 14,543.00
Queries per second 145,870.00 145,430.00
Minimum Latency (ms) 0.4 0.44
Average Latency (ms) 0.68 0.69
Maximum Latency (ms) 11.69 1.81
95th Percentile Latency (ms) 0.9 0.84

MySQL DELETE

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (8 GB, 4 Cores)
Transactions per second 129,013.00 154,046.00
Queries per second 1,290,130.00 1,540,460.00
Minimum Latency (ms) 0.03 0.02
Average Latency (ms) 0.08 0.06
Maximum Latency (ms) 2.61 3.82
95th Percentile Latency (ms) 0.09 0.08

Redis

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (8 GB, 4 Cores)
PING_INLINE per Second 78,247.26 62,695.92
PING_MBULK per Second 74,738.41 65,274.15
SET per Second 77,041.60 58,343.06
GET per Second 83,333.33 58,616.65
INCR per Second 80,971.66 57,803.47
LPUSH per Second 79,113.92 57,636.89
RPUSH per Second 77,160.49 58,616.65
LPOP per Second 81,499.59 57,504.31
RPOP per Second 82,440.23 57,670.13
SADD per Second 80,192.46 58,173.36
HSET per Second 83,612.04 58,513.75
SPOP per Second 85,034.02 58,445.36
ZADD per Second 83,263.95 58,513.75
ZPOPMIN per Second 82,987.55 57,438.25
LRANGE_100 (first 100 elements) per Second 55,555.56 48,123.20
LRANGE_300 (first 300 elements) per Second 28,851.70 33,806.62
LRANGE_500 (first 500 elements) per Second 19,391.12 26,109.66
LRANGE_600 (first 600 elements) per Second 17,211.71 23,369.95
MSET (10 keys) per Second 80,256.82 59,488.40

Redis Average Latency (ms)

Vultr – Cloud Compute (2 GB, 2 Cores) Vultr – High Performance AMD (8 GB, 4 Cores)
PING_INLINE0.340.41
PING_MBULK0.350.39
SET0.340.44
GET0.320.44
INCR0.320.45
LPUSH0.340.45
RPUSH0.340.44
LPOP0.320.45
RPOP0.320.45
SADD0.320.44
HSET0.310.44
SPOP0.300.44
ZADD0.310.44
ZPOPMIN0.310.45
LRANGE_100 (first 100 elements)0.540.53
LRANGE_300 (first 300 elements)1.110.76
LRANGE_500 (first 500 elements)1.620.97
LRANGE_600 (first 600 elements)1.841.08
MSET (10 keys)0.380.43

Conclusion

From the friendly robots:

After analyzing the benchmark results, it's evident that the Vultr High Performance AMD (8 GB, 4 Cores) instance outperforms the Vultr Cloud Compute (2 GB, 2 Cores) in almost all metrics. The High Performance instance provides superior CPU performance, with significantly higher requests per second and lower latency for Redis commands like PING_INLINE, SET, and LPUSH. It also excels in memory operations, delivering higher throughput and lower latencies. The file I/O operations and MySQL benchmarks show marked improvements in the High Performance instance, making it better suited for I/O-heavy and database-intensive workloads. Conversely, the Cloud Compute instance, though adequate for lighter workloads, lags behind in CPU, memory, and I/O performance. Ideal use cases for the Cloud Compute instance would include basic web hosting or low-demand applications, whereas the High Performance instance is ideal for CPU-intensive, I/O-heavy, or database-heavy applications requiring high throughput and low latency.

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.