Skip to main content

Reading results on the Reporting page

The Reporting page (/dashboard/reporting) is the unified results explorer, accessible from the Dashboard subnav. The page subtitle reads "Full results across all benchmark runs. Filter, compare, and analyse performance." To save a chosen set of runs as a View that you can read, share, and download, use Pulse instead.

The filter bar​

Above the results table. The live UI exposes a Filters dropdown panel and a My runs toggle pill. The panel surfaces the standard slicing dimensions:

  • Status: completed: exclude in-progress and failed jobs.
  • My runs: toggle on when you just want yours.
  • Model + Framework: for cross-comparison studies.
  • Date range: recent only, or a specific period.

Filter state is preserved as you navigate; deep-link to a filtered view via the URL.

The results table​

Paginated, sortable. Click any row to expand its detailed metrics.

Columns you'll use most:

  • Job name: your scenario identifier (for example c8-isl512-osl256).
  • Model + Framework + Quant: the workload config.
  • Throughput: tokens/sec.
  • TTFT P50 / P99: Time To First Token, median and tail.
  • TPOT: Time Per Output Token, steady-state generation speed.
  • Status: completed, failed, etc.

The chart panel​

Below the table. The live chart sub-tabs are Model, Framework, Quantization, Concurrency, Cost, and Hardware:

  • Model: same framework, vary model. Useful for picking a model for a use case.
  • Framework: same model, vary framework. Useful for picking a backend.
  • Quantization: same model + framework, vary quantization. Useful for quality-vs-throughput tradeoffs.
  • Concurrency: throughput and latency as concurrency rises. Finds the saturation point.
  • Cost: tokens per dollar and tokens per hour, when cost data is available.
  • Hardware: GPU power, util, memory, CPU, RAM. Diagnoses underutilized hardware.

Exporting​

CSV export of the filtered view is planned: the explicit Export -> CSV button is not yet exposed in v4.0.

Pagination notes​

The Reporting page uses range-based pagination: page jumps stay fast even on large result sets. The page indicator shows "X-Y of Z" where Z is the total filtered count.