Published measurements use one NVIDIA GeForce RTX 5090 through NInfer's public HTTP serving route. Choose a model below for its detailed results, run conditions, output limitations, and reproduction commands. These are recorded historical measurements; a model/backend being supported does not mean every workload or concurrency has a published measurement.
Read the measurement and publication rules for workload definitions, metric formulas, statistics, comparison requirements, and the standard result-page format.
Each cell links to the relevant result section. “Not published” describes measurement coverage, not product support. C is configured request concurrency; K is the number of draft tokens.
| Model / weights | MTP0 context profile | Single-request speculative decode | Corpus makespan | MTP3 decode saturation |
|---|---|---|---|---|
Qwen3.6-27B / groupwise-int |
8K–256K | MTP3 | Not published | C=1, 2, 4, 8 |
Qwen3.6-27B / nvfp4 |
8K–256K | MTP3 | Not published | C=1, 2, 4, 8 |
Qwen3.6-35B-A3B / groupwise-int |
8K–256K | MTP3; DFlash K=7 stochastic/greedy | MTP3 C=1, 2, 4, 8; DFlash C=1 | C=1, 2, 4, 8 |
Qwen3.8-27B / groupwise-int |
8K–256K | MTP3; DFlash2 K=7 | MTP3 C=1, 2, 4, 8; DFlash2 C=1 | Not published |
Qwen3.8-27B / nvfp4 |
8K–256K | MTP3; DFlash2 K=7 | MTP3 C=1, 2, 4, 8; DFlash2 C=1 | C=1, 2, 4, 8 |
Qwen3.8 and Qwen3.6-35B-A3B C=1 corpus points also supply their single-request phase tables. The Qwen3.6-27B NVFP4 MTP3 phase table comes from a corpus C=1 point whose full makespan is not published here. The Qwen3.8 NVFP4 saturation reports retain configuration and values but no tested Git revision; the model page records that provenance limitation.
| Question | Metric to use |
|---|---|
| How fast is prompt processing or an individual decode phase? | Prefill phase, Server TTFT, Decode phase |
| How long does the full fixed request set take? | Corpus makespan, Corpus decode, Requests/s |
| What aggregate decode rate is sustained at a full batch? | Steady decode |
These rates use different time boundaries. Server TTFT is an internal phase sum; external streaming TTFT has its own benchmark contract. Stochastic runs can generate different token totals even with the same prompts and seeds. Output-limit and repetition samples remain labeled in the measured corpus; throughput alone does not establish successful task completion. See the 35B termination and anomalies and Qwen3.8 DFlash2 outcomes.
- Serving benchmark runners: usage and local report files.
- Engine and Op benchmarks: their separate measurement scopes and commands.
- Capability evaluation: evaluation workflow; published scores live in the model cards, with a README summary.
- Perplexity: offline causal-scoring measurement and comparison rules.
Model pages are the detailed result authority. README and model-card performance tables are excerpts linked to those pages; update them together when replacing an applicable measurement.