Benchmarks measure models in isolation. Production teams care about the number their users see: how long the request takes end to end. That number includes upstream queueing, prefill and generation, so it is noisy — but it is the honest one.
Only models whose median prompt is under 2,000 tokens are listed, so the comparison is not distorted by prompt size (median input shown). Latency is end-to-end at the gateway.
| Model | n | median input | p50 | p90 |
|---|---|---|---|---|
| qwen-vl-ocr | 33 | 13 | 324ms | 1,052ms |
| qwen-mt-plus | 28 | 13 | 333ms | 1,156ms |
| qwen3-omni-flash | 32 | 19 | 355ms | 944ms |
| qwen3.5-ocr | 31 | 17 | 370ms | 3,870ms |
| qwen3-coder-flash | 44 | 13 | 403ms | 869ms |
| qwen3-vl-plus | 42 | 78 | 796ms | 1,811ms |
| hy-mt2-plus | 34 | 17 | 975ms | 2,500ms |
| minimax-text-01 | 80 | 559 | 1,115ms | 28,856ms |
| glm-5v-turbo | 42 | 15 | 1,174ms | 5,352ms |
| kimi-k2.7-code-highspeed | 37 | 16 | 1,359ms | 1,952ms |
| kimi-k2.8-preview | 289 | 89 | 1,624ms | 4,788ms |
| minimax-m2.5 | 317 | 44 | 1,860ms | 3,090ms |
| minimax-m2.7 | 370 | 46 | 1,911ms | 7,268ms |
| glm-5.3 | 146 | 146 | 2,156ms | 58,450ms |
| kimi-k2.6 | 47 | 48 | 2,623ms | 11,849ms |
| kimi-k2.5 | 61 | 56 | 2,963ms | 42,784ms |
| glm-5 | 128 | 17 | 1,585ms | 3,769ms |
| step-5-preview | 88 | 75 | 2,665ms | 71,785ms |
| qwen3-max | 166 | 1,774 | 6,132ms | 10,000ms |
| qwen3.7-max | 112 | 490 | 16,228ms | 43,910ms |
| doubao-seedream-5.0-pro (image) | 40 | — | 68,115ms | 110,651ms |
Qwen3.5-OCR answers in 370ms at $0.70 per 1M tokens. Hunyuan MT2-plus translates in 975ms at $0.072 per 1M. The expensive end of the catalog is not faster — it is slower, because flagship models generate longer answers and are sized for reasoning rather than turnaround. If your task is classification, extraction or translation, the cheap model is usually also the fast one.
The p90 values spread far more than p50 — from 869ms to 71s. That tail is generation: a model writing 900 tokens takes far longer than one writing 50, regardless of prompt. Streaming hides this from users but not from your request pipeline.
Image models are 10–68 seconds at p50. That is not a latency problem to optimise; it is a job to queue. Plan for async: submit, poll, webhook — not request/response.
Every model in the table is reachable through the same endpoint, so switching tiers is a per-request model id change. Prices: live feed; cost side: what real calls cost.
From 30 days of gateway traffic: OCR and translation models respond in 324-975ms at p50, mid-tier chat models in 1.1-2.6s, flagship text models in 3-16s depending on size, and image generation takes 10-68s. The median p50 across 63 models was 1.86s.
Small models are cheaper per token and need less compute per request. Qwen3.5-OCR responds in 370ms at $0.70 per 1M tokens, while a flagship 1M-context model can take 16s. Cheap and fast coincide at the small-model end.
Yes. This is end-to-end time as observed at the gateway: upstream queueing plus generation. It is not time-to-first-token, so models producing long outputs appear slower even when their prefill is fast.
Not in a simple way in this data, because prompt size correlates with which model a workload chooses. Comparing only models whose median prompt is under 2K tokens removes that confound, and there the ordering follows model class rather than prompt size.
Free tier to test latency from your region, then pay only for what you use — 0% markup on 111 models.
Get an API keyWindow: 30 days ending 2026-10-22. 63 models with at least 25 latency samples. Latency is end-to-end at the gateway (queue + prefill + generation), recorded per request; p50/p90 computed over all successful calls in the window. Prices: /china-ai-leaderboard.json.