Experiment · runtime perf

Open Kernel fused small-batch expert norm

Profile wrapper dispatch as well as kernel arithmetic: the existing fused norm kernel removed several small-batch framework launches while preserving FP32 reduction and invalid-expert masking. Retained outcome: worked with caveat.

Outcome
worked with caveat
Family
runtime perf
Evidence confidence
exact
Record
infrastructure

Evidence readout

2026-10-23 H200 scored run 20b3199ecbd847f2 passed with no flags: 1.2236x aggregate, reported 95% interval 1.2053-1.2420x. Small batches measured 1.22-1.49x versus SGLang; the 32-token case measured 0.988x. The preceding check measured 1.2201x aggregate.

What the attempt taught

Profile wrapper dispatch as well as kernel arithmetic: the existing fused norm kernel removed several small-batch framework launches while preserving FP32 reduction and invalid-expert masking.

Why it stopped or stayed bounded

The existing 32-token path retains a small measured regression, and the gain applies to the organizer workload rather than application throughput.

Method and scope

  • Experiment family: runtime perf.
  • Record kind: infrastructure.

Disposition

Experiment closed after scored run beb82b4224554523 finished at rank 283/749, outside the owner top-100 target. Retain the research artifact; no further jobs.

This retained disposition is historical evidence, not authorization to restart the experiment. A new run needs a fresh question, frozen evaluator, explicit resource budget, and scoped tracking issue.

How to read this dossier

This canonical page separates the retained repository decision from the material that informed it. A source may describe an external claim, historical measurement, local observation, or planned procedure; those evidence classes are not interchangeable. Follow the provenance links before reusing a number or method.

Status and disposition describe what PostTrainLLM retained when this record was indexed. They are not a live product promise, a newly run benchmark, or permission to restart historical work. Unknown or unmeasured fields remain unknown rather than being treated as zero.

To reuse the record, first name the exact claim you need and trace it to the linked source. Then check whether the original environment, model revision, data split, evaluator, hardware, and budget match the proposed use. If they do not, treat the record as a hypothesis or design reference and run the smallest fresh comparison that can falsify it. Preserve negative outcomes and regressions beside any improvement; a local win on one slice does not silently become a general capability claim.

Source provenance

The normalized record comes from docs/attempts.json. The links below are the tracked evidence and explanatory sources preserved with the record.