A SoAI Bench result combines score fields with the device identity, settings snapshot, runtime context, and telemetry gathered during the run.
Open and export results in the SoAI WebUI
- Open Hardware, select SoAI Bench at the top of the page, then select the GPU.
- Select History in the SoAI Bench dialog when that GPU has a run.
- Inspect the profile, status, duration, certification, score, and device details for the run.
- Select Download in the history dialog to export that GPU's history as CSV.
The Standard run dialog also exposes its terminal report and a Download action for the displayed
run. History and exports require Hardware read access (HARDWARE_READ). History appears in the SoAI Bench dialog when SoAI has any run record for the selected GPU,
including an active run. This path does not depend on a GPU controls panel.
The SoAI Bench previous runs table on the Hardware page lists runs across GPUs. Sort it by start time, profile, status, score, or duration, and use a row's actions to copy, download, share, or delete that run.
Driver identifies the physical GPU driver, separately from the OpenCL runtime version. A saved run keeps the versions recorded when it was created.
Share an eligible score
A Share action appears when a completed, certified Standard run contains all 5 measured passes and
the evidence required for publication. Sharing requires GPU tuning (HW_GPU_TUNING). New GPU scores are welcome, especially for GPU models that are not represented on the leaderboard yet.
Cancelled and incomplete runs remain in local history but cannot be shared. Complete a certified Standard run on a supported GPU before publication. A rejected run is not sent to the leaderboard.
- Open SoAI Bench on the Hardware page, select the GPU, then select History.
- Select Share beside an eligible result.
- Review the publication preview. It contains the score, 5 measured passes, public GPU and runtime details, benchmark settings, and available sensor evidence.
- Confirm the publication. If it succeeds, SoAI provides the public result link.
The publication does not include the SoAI account identity, files, configuration, analytics, or general telemetry. A result held for review does not count toward the leaderboard until the review is complete. If sharing times out, use Share again; SoAI reconciles the same publication instead of creating another submission.
To remove an eligible run from SoAI, open History and select Delete local history beside it. An active or indeterminate run cannot be deleted. A run prepared for or published to the leaderboard also remains in local history so SoAI can preserve its publication state. SoAI asks for confirmation before deleting an eligible local run.
Read the score fields
| Profile | Score composition |
|---|---|
| Standard | 40 percent compute throughput and 60 percent memory throughput. The diagnostic latency score is reported separately and does not affect overall. |
| Stress | 70 percent compute and 30 percent memory. Stress has no latency score. |
The run report can also include compute, ALU, and matrix throughput, memory throughput, latency, duration, sample count, temperature, power, throttling, and OpenCL device details. Available fields depend on the run and its telemetry.
Understand certification and status
A Standard run in certified mode becomes eligible after 120 seconds of active workload warm-up and all 5 measured passes provide valid workload, accounting, and numerical sample evidence. Each measured phase lasts at least 1 second. Optional telemetry, authoritative throttling observations, throughput variance, and signed drift remain visible descriptive evidence and do not alter the score or eligibility through an arbitrary threshold. Historical results retain their recorded eligibility and rejection reason.
Unsupported means the preflight or runtime could not use that GPU. Treat Unstable, Failed, Cancelled, Stopped, and Indeterminate as results that need their recorded reason before any comparison. The WebUI always starts certified Standard runs. History can also contain a quick Standard run created through a non-WebUI client.
Compare like with like
Compare the same profile, scoring method, GPU model, driver, OpenCL runtime, settings, cooling condition, and host load. Do not compare Stress scores with certified Standard scores. SoAI Bench uses synthetic OpenCL workloads, so its GOPS and memory figures are not model-token throughput measurements. For repeatable setup, see Running benchmarks.