Fast only means something inside a defined slice.

Systems are primary

MLPerf publishes results for submitted systems. The primary metric displayed here is that official system result. It reflects the submitted topology, software and accelerator count—not a universal property of a chip.

The index may show a clearly labeled per-accelerator value only when both accelerators_per_node and number_of_nodes are explicit positive integers in the pinned system JSON. It divides official tokens/s by their product. It never infers a count from strings such as x8 or NVL72.

Stable identity, immutable versions

An accelerator, submitted system and benchmark result are separate entities. A logical result ID remains stable for the same exact slice and system. A content-version ID changes when normalized content changes.

Every record carries repository, commit, path, immutable GitHub URL and SHA-256. The dataset manifest hashes the ordered accelerators, systems, results and slices, so an auditor can detect any altered snapshot.

Validity before rank

V1 admits only base performance/run_1/mlperf_log_summary.txt records whose summary states Result is : VALID and contains a recognized positive throughput metric. TEST07 and TEST09 branches are not mixed with official-default rows.

Identity and family names come from a reviewed alias registry applied to the accelerator model declared in the system JSON. Missing system evidence, unreviewed identity, ambiguous counts, invalid summaries, scenario conflicts, unknown units and parser failures enter the quarantine report.

Ranking and ties

Tokens per second is higher-is-better. Rows are sorted by the selected metric, then by stable result ID. Equal numeric values receive the same rank, and the next position skips accordingly. Ranking occurs across the full filtered set before pagination.

Best per accelerator retains the best submitted system for each exact accelerator identity. All systems keeps every qualifying submission. Derived per-accelerator values are never selected by default.

Interactive convention

Some official paths classify a result as Interactive while the LoadGen summary reports Server. The importer preserves the official path scenario and accepts this specific observed convention; any other path/summary mismatch is quarantined. The raw summary remains linked beside the row.

This is a normalization decision, not a claim that Interactive and Server are interchangeable. They remain separate slices.