Vultr High Performance AMD (2 GB, 2 Cores) vs. Vultr High Performance AMD (4 GB, 2 Cores)
Fresh benchmarks coming at ya. Today I've spun up 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 – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Last Benchmarked | Sun, 31 May 2026 07:00:52 GMT | Fri, 29 May 2026 10: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 | $18.00 | $24.00 |
| RAM (GB) | 2 | 4 |
| CPU Cores | 2 | 2 |
| Storage (TB) | 60 | 100 |
| Storage Type | NVMe | NVMe |
| Transfer (TB) | 4 | 5 |
CPU
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Vendor | AuthenticAMD | AuthenticAMD |
| Model Name | AMD EPYC-Genoa Processor | AMD EPYC-Genoa Processor |
| Clock Speed (MHz) | 2,899.99 | 2,899.97 |
| CPU Cache Size (KB) | 1,024.00 | 1,024.00 |
| BogoMips | 5,799.98 | 5,799.93 |
| Events per Second | 4,648.14 | 4,654.86 |
| Minimum Latency (ms) | 0.2 | 0.2 |
| Average Latency (ms) | 0.21 | 0.21 |
| Maximum Latency (ms) | 1.26 | 0.47 |
| 95th Percentile Latency (ms) | 0.23 | 0.22 |
Memory
Memory Read
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 7,548,502.85 | 7,333,962.29 |
| Mebibytes per second | 7,371.58 | 7,162.07 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.08 | 0.08 |
| 95th Percentile Latency (ms) | 0 | 0 |
Memory Write
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Operations per second | 7,544,807.09 | 7,479,289.21 |
| Mebibytes per second | 7,367.98 | 7,303.99 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 0.12 | 12.21 |
| 95th Percentile Latency (ms) | 0 | 0 |
File I/O
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Reads per Second | 5,114.79 | 7,562.64 |
| Writes per Second | 3,409.86 | 5,041.76 |
| Fsyncs per Second | 10,914.44 | 16,143.13 |
| Read Mebibytes per Second | 79.92 | 118.17 |
| Written Mebibytes per Second | 53.28 | 78.78 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0.05 | 0.03 |
| Maximum Latency (ms) | 3.7 | 6.84 |
| 95th Percentile Latency (ms) | 0.12 | 0.1 |
Mutex
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Minimum Latency (ms) | 574.03 | 595.39 |
| Average Latency (ms) | 637.47 | 638.90 |
| Maximum Latency (ms) | 663.74 | 672.95 |
| 95th Percentile Latency (ms) | 657.93 | 669.89 |
MySQL
MySQL Read-only
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 9,622.00 | 9,985.00 |
| Queries per second | 96,220.00 | 99,850.00 |
| Minimum Latency (ms) | 0.73 | 0.74 |
| Average Latency (ms) | 1.04 | 1 |
| Maximum Latency (ms) | 2.22 | 2.48 |
| 95th Percentile Latency (ms) | 1.12 | 1.06 |
MySQL Write-only
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 9,585.00 | 9,768.00 |
| Queries per second | 95,850.00 | 97,680.00 |
| Minimum Latency (ms) | 0.8 | 0.74 |
| Average Latency (ms) | 1.04 | 1.02 |
| Maximum Latency (ms) | 2.18 | 7.74 |
| 95th Percentile Latency (ms) | 1.32 | 1.3 |
MySQL Read/Write
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 4,686.00 | 4,671.00 |
| Queries per second | 46,860.00 | 46,710.00 |
| Minimum Latency (ms) | 1.57 | 1.72 |
| Average Latency (ms) | 2.13 | 2.14 |
| Maximum Latency (ms) | 4.26 | 8.85 |
| 95th Percentile Latency (ms) | 2.52 | 2.57 |
MySQL INSERT
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 15,965.00 | 16,537.00 |
| Queries per second | 159,650.00 | 165,370.00 |
| Minimum Latency (ms) | 0.45 | 0.43 |
| Average Latency (ms) | 0.62 | 0.6 |
| Maximum Latency (ms) | 2.23 | 7.37 |
| 95th Percentile Latency (ms) | 0.74 | 0.73 |
MySQL Bulk INSERT
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 3,065,092.00 | 2,948,592.00 |
| Queries per second | 30,650,920.00 | 29,485,920.00 |
| Minimum Latency (ms) | 0 | 0 |
| Average Latency (ms) | 0 | 0 |
| Maximum Latency (ms) | 208.51 | 206.98 |
| 95th Percentile Latency (ms) | 0 | 0 |
MySQL SELECT
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 217,035.00 | 229,032.00 |
| Queries per second | 2,170,350.00 | 2,290,320.00 |
| Minimum Latency (ms) | 0.02 | 0.02 |
| Average Latency (ms) | 0.05 | 0.04 |
| Maximum Latency (ms) | 0.61 | 0.42 |
| 95th Percentile Latency (ms) | 0.06 | 0.05 |
MySQL SELECT (Random Points)
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 14,818.00 | 15,101.00 |
| Queries per second | 148,180.00 | 151,010.00 |
| Minimum Latency (ms) | 0.24 | 0.21 |
| Average Latency (ms) | 0.67 | 0.66 |
| Maximum Latency (ms) | 1.94 | 1.85 |
| 95th Percentile Latency (ms) | 0.86 | 0.83 |
MySQL SELECT (Random Ranges)
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 14,341.00 | 14,515.00 |
| Queries per second | 143,410.00 | 145,150.00 |
| Minimum Latency (ms) | 0.27 | 0.23 |
| Average Latency (ms) | 0.7 | 0.69 |
| Maximum Latency (ms) | 1.67 | 1.72 |
| 95th Percentile Latency (ms) | 0.89 | 0.89 |
MySQL UPDATE (Indexed)
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 14,864.00 | 15,565.00 |
| Queries per second | 148,640.00 | 155,650.00 |
| Minimum Latency (ms) | 0.47 | 0.45 |
| Average Latency (ms) | 0.67 | 0.64 |
| Maximum Latency (ms) | 2.36 | 7.44 |
| 95th Percentile Latency (ms) | 0.87 | 0.86 |
MySQL UPDATE (Non-Indexed)
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 15,284.00 | 16,035.00 |
| Queries per second | 152,840.00 | 160,350.00 |
| Minimum Latency (ms) | 0.46 | 0.43 |
| Average Latency (ms) | 0.65 | 0.62 |
| Maximum Latency (ms) | 1.65 | 7.21 |
| 95th Percentile Latency (ms) | 0.83 | 0.8 |
MySQL DELETE
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| Transactions per second | 151,536.00 | 160,573.00 |
| Queries per second | 1,515,360.00 | 1,605,730.00 |
| Minimum Latency (ms) | 0.02 | 0.02 |
| Average Latency (ms) | 0.07 | 0.06 |
| Maximum Latency (ms) | 4.83 | 7.8 |
| 95th Percentile Latency (ms) | 0.08 | 0.08 |
Redis
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE per Second | 55,991.04 | 56,465.27 |
| PING_MBULK per Second | 57,903.88 | 58,105.75 |
| SET per Second | 57,703.40 | 58,651.02 |
| GET per Second | 57,703.40 | 58,651.02 |
| INCR per Second | 57,372.34 | 58,275.06 |
| LPUSH per Second | 57,836.90 | 58,445.36 |
| RPUSH per Second | 58,173.36 | 58,858.15 |
| LPOP per Second | 58,343.06 | 58,892.82 |
| RPOP per Second | 58,343.06 | 58,582.31 |
| SADD per Second | 58,241.12 | 58,788.95 |
| HSET per Second | 58,858.15 | 58,207.21 |
| SPOP per Second | 58,892.82 | 57,836.90 |
| ZADD per Second | 57,504.31 | 58,513.75 |
| ZPOPMIN per Second | 57,870.37 | 58,479.53 |
| LRANGE_100 (first 100 elements) per Second | 49,236.83 | 49,652.43 |
| LRANGE_300 (first 300 elements) per Second | 34,818.94 | 34,340.66 |
| LRANGE_500 (first 500 elements) per Second | 26,766.60 | 26,441.04 |
| LRANGE_600 (first 600 elements) per Second | 24,207.21 | 24,236.55 |
| MSET (10 keys) per Second | 58,548.01 | 58,754.41 |
Redis Average Latency (ms)
| Vultr – High Performance AMD (2 GB, 2 Cores) | Vultr – High Performance AMD (4 GB, 2 Cores) | |
|---|---|---|
| PING_INLINE | 0.48 | 0.47 |
| PING_MBULK | 0.44 | 0.44 |
| SET | 0.45 | 0.44 |
| GET | 0.45 | 0.44 |
| INCR | 0.45 | 0.44 |
| LPUSH | 0.44 | 0.44 |
| RPUSH | 0.44 | 0.44 |
| LPOP | 0.44 | 0.44 |
| RPOP | 0.44 | 0.44 |
| SADD | 0.44 | 0.44 |
| HSET | 0.44 | 0.44 |
| SPOP | 0.44 | 0.44 |
| ZADD | 0.45 | 0.44 |
| ZPOPMIN | 0.44 | 0.44 |
| LRANGE_100 (first 100 elements) | 0.53 | 0.52 |
| LRANGE_300 (first 300 elements) | 0.74 | 0.74 |
| LRANGE_500 (first 500 elements) | 0.95 | 0.96 |
| LRANGE_600 (first 600 elements) | 1.05 | 1.04 |
| MSET (10 keys) | 0.44 | 0.44 |
Conclusion
From the friendly robots:
After analyzing the benchmark results from both instances, it's clear that the Vultr High Performance AMD (4 GB, 2 Cores) configuration outperforms the Vultr High Performance AMD (2 GB, 2 Cores) in most areas, particularly in Redis operations and overall file I/O performance, which indicates better handling of memory-intensive tasks and I/O-heavy workloads. While both instances have similar CPU performance, the additional RAM in the higher specification instance allows it to handle more concurrent operations and larger datasets more efficiently. This makes the 4 GB, 2 Cores instance ideal for use cases that require more memory and can benefit from enhanced I/O performance, such as high-traffic web applications, database servers, or any application needing robust memory handling and fast data retrieval. Meanwhile, the 2 GB, 2 Cores instance remains suitable for more modest applications or environments where cost is a primary concern, and the extra RAM and improved I/O capabilities of the higher specification instance are not as critical.
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.