Skip to main content

Overview

This document describes the JSON schema for a Workload. A Workload defines a concrete, executable instance of a Definition by binding specific values to all variable axes and specifying the data source for all inputs. It represents the exact configuration under which a Solution is benchmarked. Storage Format: In the FlashInfer-Bench dataset, a standalone Workload is stored using the Trace data structure with only the definition and workload fields populated, while solution and evaluation are set to null. In FlashInfer Trace dataset, all workloads of the same definition are stored in a single JSONL file where each line is a Workload object.

JSON Schema Description

Top-Level Object Structure

inputs : Input Descriptor Objects

This object maps input names (e.g., "A", "weight", "mask") to input descriptors that explain where the data comes from and (when necessary) how it should be generated or loaded. Each descriptor must contain at least the type field. Additional fields become required or optional depending on the chosen type. Additional fields for type scalar: Additional fields for type safetensors:

Example: RMSNorm Workload

Example: GEMM Workload with Random Inputs