Latitude.sh vm.large benchmarks

16 shared vCPU, 64 GB RAM, 640 GB

[Shared CPU](https://rackcensus.com/vps-categories/shared-cpu-vps-benchmarks)

$237.00/mo

$0.65/hr

$474.50/mo at 730 hours

$1,991.00/yr

$165.92/mo effective, 30% less than monthly

[Visit Latitude.sh](https://rackcensus.com/go/latitude)

# Performance by location
[Every run of this plan](https://rackcensus.com/benchmarks?filter%5Bplan%5D=latitude-vm-large&filter%5Bsort%5D=location)

Medians over the last 90 days. Multi per $ is the multi-core median divided by the current monthly price, USD only.

Price position

Cheaper than 72% of 18 similar plans

Same vCPU count and CPU type, 48 to 85 GB RAM, median $384

[Compare these side by side](https://rackcensus.com/vps-geekbench-scores?filter%5Bc%5D%5B%5D=o_l3jjbt&filter%5Bc%5D%5B%5D=o_96qgod&filter%5Bc%5D%5B%5D=o_onzskm)

| Location | Runs | GB7 single | GB7 multi | 4K IOPS | Price | Multi per $ | Last tested |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [Frankfurt, Germany](https://rackcensus.com/locations/frankfurt-vps-benchmarks "Every provider in Frankfurt") Frankfurt | 1 | 1,690 | 14,134 | 27,616 | $237.00/mo | 60 | [Oct 4, 2026](https://rackcensus.com/benchmarks/hnam9w-latitude-plan-jv6m5j18nlpee-fra-benchmark) |
| [Tokyo, Japan](https://rackcensus.com/locations/tokyo-vps-benchmarks "Every provider in Tokyo") Tokyo | 1 | 1,662 | 11,866 | 28,314 | $237.00/mo | 50 | [Oct 5, 2026](https://rackcensus.com/benchmarks/vx6s9r-latitude-vm-large-tyo3-benchmark) |
| [Ashburn, United States](https://rackcensus.com/locations/ashburn-vps-benchmarks "Every provider in Ashburn") Ashburn | 2 | 1,470 | 10,985 | 18,051 | $237.00/mo | 46 | [Oct 5, 2026](https://rackcensus.com/benchmarks/z2chpm-latitude-vm-large-ash-benchmark) |

## Geekbench 7 single-core

Per location, medians over the last 90 days

Loading...

## Disk 4K mixed IOPS

Per location, medians over the last 90 days

Loading...

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.