Vultr Optimized Cloud General Purpose AMD 64 vCPU / 192 GB benchmarks
64 dedicated vCPU, 192 GB RAM, 960 GB NVMe
Performance by location
Every run of this planMedians 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 | $1,920.00/mo | n/a | Not tested yet |
|
Bangalore, IN
Bangalore, IN
|
0 | n/a | n/a | n/a | $1,920.00/mo | n/a | Not tested yet |
|
Chicago, US
Chicago, US
|
0 | n/a | n/a | n/a | $1,920.00/mo | n/a | Not tested yet |
|
Dallas, US
Dallas, US
|
0 | n/a | n/a | n/a | $1,920.00/mo | n/a | Not tested yet |
|
Honolulu, US
Honolulu, US
|
0 | n/a | n/a | n/a | $1,920.00/mo | n/a | Not tested yet |
|
London, GB
London, GB
|
0 | n/a | n/a | n/a | $1,920.00/mo | n/a | Not tested yet |
|
Los Angeles, US
Los Angeles, US
|
0 | n/a | n/a | n/a | $1,920.00/mo | n/a | Not tested yet |
|
Melbourne, AU
Melbourne, AU
|
0 | n/a | n/a | n/a | $1,920.00/mo | n/a | Not tested yet |
|
Mexico City, MX
Mexico City, MX
|
0 | n/a | n/a | n/a | $1,920.00/mo | n/a | Not tested yet |
|
Miami, US
Miami, US
|
0 | n/a | n/a | n/a | $1,920.00/mo | n/a | Not tested yet |
|
Mumbai, IN
Mumbai, IN
|
0 | n/a | n/a | n/a | $1,920.00/mo | n/a | Not tested yet |
|
New Jersey, US
New Jersey, US
|
0 | n/a | n/a | n/a | $1,920.00/mo | n/a | Not tested yet |
|
Osaka, JP
Osaka, JP
|
0 | n/a | n/a | n/a | $1,920.00/mo | n/a | Not tested yet |
|
Seoul, KR
Seoul, KR
|
0 | n/a | n/a | n/a | $1,920.00/mo | n/a | Not tested yet |
|
Tokyo, JP
Tokyo, JP
|
0 | n/a | n/a | n/a | $1,920.00/mo | n/a | Not tested yet |
|
Warsaw, PL
Warsaw, PL
|
0 | n/a | n/a | n/a | $1,920.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.