Skip to content

Highest Output-Speed Qwen2.5 VL 72B Instruct Inference Providers

Ranks providers by their recent typical output speed in tokens per second. Providers without enough recent data remain visible after ranked rows.

Parasail currently ranks first at 30.0 tok/s via parasail/fp8.

Provider options:
2
Ranked:
2
Metric:
Output speed

Highest output speed endpoint ranking

Highest Output-Speed Qwen2.5 VL 72B Instruct Inference Providers
RankProvider / routeOutput speedSpeed measurementsEndpoint details
#1Provider / route
Parasailparasail/fp8
Output speed30.0 tok/sSpeed measurements
500-token response
17.65 s
Response starts
0.98 s
Output speed
30.0 tok/s
Endpoint details
Input price
$0.8 / 1M tokens
Output price
$1 / 1M tokens
Uptime (30 min)
99.89%
Context
128K
#2Provider / route
Nebiusnebius/fp8
Output speed19.0 tok/sSpeed measurements
500-token response
27.15 s
Response starts
0.83 s
Output speed
19.0 tok/s
Endpoint details
Input price
$0.25 / 1M tokens
Output price
$0.75 / 1M tokens
Uptime (30 min)
99.94%
Context
32K

Endpoint data fetched .

Qwen2.5 VL 72B Instruct endpoint guide

How to interpret the Highest Output-Speed Qwen2.5 VL 72B Instruct Inference Providers

2 of 2 Qwen2.5 VL 72B Instruct endpoints currently have the published data required for this ranking. Parasail leads at 30.0 tok/s via parasail/fp8. The table keeps unranked routes visible so missing measurements do not look like missing provider availability.

How generation throughput is ranked

The output-speed ranking compares recent median generated tokens per second. It favors routes that complete long generations quickly, while first-token latency remains a separate measure of how responsive the endpoint feels at the beginning.

Compare Parasail with the next option

Nebius currently ranks second at 19.0 tok/s. Compare that gap with input and output price, response-start time, output speed, 30-minute uptime, context length, and the exact route before deciding whether first place is meaningful for your workload.

Use the route, not only the provider name

Qwen2.5 VL 72B Instruct has 2 published provider options, and performance data is matched to each exact OpenRouter routing tag. Different quantization, context, regional deployment, or provider configuration can change price and behavior even when the underlying model name is identical.