Vultr Optimized Cloud General Purpose AMD 96 vCPU / 256 GB benchmarks

96 dedicated vCPU, 256 GB RAM, 1280 GB NVMe

[Dedicated CPU](https://rackcensus.com/vps-categories/dedicated-cpu-vps-benchmarks)[General Purpose](https://rackcensus.com/vps-categories/general-purpose-vps-benchmarks)[NVMe Storage](https://rackcensus.com/vps-categories/nvme-storage-vps-benchmarks)

$3,840.00/mo

$5.26/hr

$3,839.80/mo at 730 hours

[Visit Vultr](https://rackcensus.com/go/vultr)

# Performance by location
[Every run of this plan](https://rackcensus.com/benchmarks?filter%5Bplan%5D=vultr-voc-g-96c-256gb-1280s-amd&filter%5Bsort%5D=location)

Medians over the last 90 days. Same plan, same provider, different datacenters. Multi per $ divides the multi-core median by each location's current monthly price, USD only.

Price position

No similar plans tracked yet

| Location | Runs | GB7 single | GB7 multi | 4K IOPS | Price | Multi per $ | Last tested |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Amsterdam, NL Amsterdam, NL | 0 | n/a | n/a | n/a | $3,840.00/mo | n/a | Not tested yet |
| Bangalore, IN Bangalore, IN | 0 | n/a | n/a | n/a | $3,840.00/mo | n/a | Not tested yet |
| Dallas, US Dallas, US | 0 | n/a | n/a | n/a | $3,840.00/mo | n/a | Not tested yet |
| London, GB London, GB | 0 | n/a | n/a | n/a | $3,840.00/mo | n/a | Not tested yet |
| Los Angeles, US Los Angeles, US | 0 | n/a | n/a | n/a | $3,840.00/mo | n/a | Not tested yet |
| Mexico City, MX Mexico City, MX | 0 | n/a | n/a | n/a | $3,840.00/mo | n/a | Not tested yet |
| Mumbai, IN Mumbai, IN | 0 | n/a | n/a | n/a | $3,840.00/mo | n/a | Not tested yet |
| New Jersey, US New Jersey, US | 0 | n/a | n/a | n/a | $3,840.00/mo | n/a | Not tested yet |
| Seoul, KR Seoul, KR | 0 | n/a | n/a | n/a | $3,840.00/mo | n/a | Not tested yet |
| Warsaw, PL Warsaw, PL | 0 | n/a | n/a | n/a | $3,840.00/mo | n/a | Not tested yet |

A location is highlighted only when it leads the next best by 5 percent or more. Smaller gaps are normal run-to-run variance.

Network results are not compared here. iperf3 targets are third-party servers, so distance to each target dominates the number.