Report amatrix benchmark status across ops and backends
Source:R/backend-calibration.R
amatrix_benchmark_report.RdReads a machine-local benchmark baseline CSV (a table of recorded per-op cold and warm timings), if one is present, together with the cached calibration in the user cache directory, and returns a structured data.frame surfacing per-op cold vs warm timings and the currently-calibrated dispatch thresholds.
Usage
amatrix_benchmark_report(baseline_path = file.path("tools", "baseline.csv"))Value
A list with two elements:
- baseline
data.frame with columns
op,size,backend,cold_ms,warm_ms,warm_vs_cold_ratio,speedup_vs_cpu. Rows with missing cold OR warm data useNAfor the missing variant. Empty when the baseline file is absent.- calibration
data.frame with columns
backend,op,threshold_elements,gpu_wins. Rows come from the cached calibration; empty when no calibration is available.
Details
This is the user-facing honesty surface for Track 4's speed contract: users can see (a) which backends are calibrated on their machine, (b) cold-start vs warm-run ratios per op, and (c) where the dispatcher will currently route.