Download and analyze InferenceX ML inference benchmark data — GPU performance metrics across hardware, frameworks, and models. Use when asked to analyze inference benchmarks, compare GPUs, plot pareto frontiers, or work with InferenceX data.
Download and analyze InferenceX ML inference benchmark data — GPU performance metrics across hardware, frameworks, and models. Use when asked to analyze inference benchmarks, compare GPUs, plot pareto frontiers, or work with InferenceX data.
Setup
Download the latest database dump from GitHub releases. It is xz-compressed and split into
one or more .tar.xz.part* files; reassemble them by piping cat through xz (requires xz):
run_attempt: re-runs of the same github_run_id get incrementing attempts. When computing latest results, first filter to the highest run_attempt per github_run_id.
conclusion: success, failure, or cancelled
html_url: link to the GitHub Actions run
Run Stats Fields
id, workflow_run_id, date, hardware, n_success, total
Reliability rate = n_success / total per hardware per run
Availability Fields
Denormalized table for fast date-picker lookups — one row per (model, isl, osl, precision, hardware, framework, spec_method, disagg, date) combination. Not joined by config_id; uses the raw text keys directly.
model, isl, osl, precision, hardware, framework, spec_method, disagg, date
Load data: Parse configs.json and benchmark_results.json, join on config_id, filter out rows where error is not null.
Latest per config: First filter workflow_runs to the highest run_attempt per github_run_id, then join to benchmark_results. For each unique (config_id, conc, isl, osl), keep only the row with the latest date.
Pareto frontier (chip vs chip): Fix a model/concurrency/sequence length. Plot throughput (x) vs median TTFT (y) per hardware. The pareto frontier connects points that dominate all others (higher throughput AND lower latency). Sort by descending throughput, greedily collect points with improving latency.
Pareto frontier (date vs date): Fix a hardware/model/concurrency/sequence length. Plot throughput and latency over time to see how performance evolves across benchmark dates.