Unofficial run
Also known as unofficial overlay, community run
In plain English
An unofficial run is a benchmark run that has not been ingested into the published dataset but can still be drawn on top of the charts from its URL.
Technical definition
An unofficial run is a CI benchmark run loaded into the dashboard as an overlay from its run identifier, rather than from the published database.
Engineering details
Adding a run identifier to the page URL fetches that run and draws its points, rooflines, and rows alongside the official data in distinct overlay colors. The overlay is a separate rendering path, so it can be toggled per hardware type or dismissed per run without disturbing the official selection underneath.
Why it matters
Publishing a result usually lags producing it, and a contributor tuning a recipe needs to see the new curve against the current frontier before anyone decides to ingest it. The overlay makes an in-flight run reviewable without granting it the standing of a published measurement.
How to read it in InferenceX
Overlay colors come from a run-index palette rather than the hardware palette, so an overlay is never mistaken for official data. Some views require data that is only persisted for ingested runs, and those views state that overlays are unavailable rather than silently omitting them.
Source material
See the concept in real benchmarks
InferenceMAX: Open Source Inference Benchmarking
NVIDIA GB200 NVL72, AMD MI355X, Throughput Token per GPU, Latency Tok/s/user, Perf per Dollar, Cost per Million Tokens, Tokens per Provisioned Megawatt, DeepSeek R1 670B, GPTOSS 120B, Llama3 70B
InferenceX v2: NVIDIA Blackwell Vs AMD vs Hopper - Formerly InferenceMAX
GB300 NVL72, MI355X, B200, H100, Disaggregated Serving, Wide Expert Parallelism, Large Mixture of Experts, SGLang, vLLM, TRTLLM