Skip to main content
This document describes the JSON schema for a Trace. A Trace describes a benchmark result of a Solution on a Definition with a specific Workload. The collection of all Trace files forms the database of benchmark results. In a Trace object, solution and evaluation are optional. If they are not provided, it describes a workload entry in the dataset. In a Trace object, the definition and solution are externally linked through their names; workload and evaluation are embedded in the Trace object. This is because definition and solution are relatively large objects and will be used repeatedly in the dataset.

JSON Schema Description

Top-Level Object Structure

evaluation : Benchmark Statistics Summary

This object represents a single, complete benchmark result.

correctness : Correctness Summary

performance : Performance Summary

Note that it’s normal for the speedup factor to be very large since the references are torch only, unoptimized implementations.

environment: Environment Definition Object

The environment object specifies the exact execution environment for this benchmark run.

The correctness and performance Nullable Table

The correctness and performance fields are set to be nullable depending on the status.

Example: RMSNorm Trace