Skip to main content
Challenge

Build a Local Open-Weight Triton Kernel Latency and Memory Auditor

Benchmark custom open-weight attention and GEMM Triton kernels against baseline implementations on local GPUs. Quantify execution time, register pressure, and SRAM efficiency before serving deployment.

EngineeringHosted by Vera
Challenge brief

What you are building

The core problem, expected build, and operating context for this challenge.

Benchmark custom open-weight attention and GEMM Triton kernels against baseline implementations on local GPUs. Quantify execution time, register pressure, and SRAM efficiency before serving deployment.

Hardware Kernel Optimization Engineer

Ingest profiling trace outputs from local Triton kernel compilation and execution benchmarks.

Extract kernel execution times, shared memory allocations, and register spill counts.

Compare candidate fused kernels against standard unquantized PyTorch baseline operations.

Use hosted Claude API to synthesize kernel tuning recommendations and block size heuristics.

Kernel benchmark comparator dashboard with memory footprint graphs and tuning report export.

Create normalized synthetic benchmark tables representing Triton attention kernel runs across varying tile sizes. Starter examples below are synthetic. They are not downloaded records.

vLLM open-model serving Incorporate vLLM optimized attention and GEMM kernel execution references using Triton and CUTLASS.

mlflow, anthropic, pandas. mlflow tracks kernel benchmark metrics, artifacts, and parameter permutations across hardware runs. Hosted Claude API accessed over HTTPS for code commentary; kernel execution applies strictly to local open code.

Submit runnable source, pinned dependencies, setup commands, a working interface, example outputs, and a recorded end-to-end demo. Include tests and an action log.

Calculates percentage speedup or regression of candidate kernels over baseline operations.

Identifies register spilling into local memory that causes memory stall cycles.

Generates structured tuning recommendations for optimal tile and warp dimensions.

```json [ { "input": { "kernel_name": "fused_fp8_gemm", "block_m": 64, "block_n": 64, "registers_per_thread": 142, "spill_stores_bytes": 2048, "latency_us": 48.2, "baseline_us": 35.1 }, "expected_output": { "status": "REGRESSION", "spill_detected": true, "speedup_ratio": 0.73, "recommendation": "reduce_tile_size_to_32x64_to_relieve_register_pressure" } }, { "input": { "kernel_name": "fused_fp8_gemm", "block_m": 32, "block_n": 64, "registers_per_thread": 96, "spill_stores_bytes": 0, "latency_us": 22.4, "baseline_us": 35.1 }, "expected_output": { "status": "IMPROVED", "spill_detected": false, "speedup_ratio": 1.57, "recommendation": "adopt_configuration_for_production_profile" } } ] ```

Benchmarks open-source Triton code in isolated local user environments without accessing closed server systems. Use mock external writes. Require human review before any real deployment.

Rules

Participation guide

Benchmarks open-source Triton code in isolated local user environments without accessing closed server systems. Use mock external writes and human review.

Delivery guide

How work is evaluated

Evaluation

Calculates percentage speedup or regression of candidate kernels over baseline operations. Identifies register spilling into local memory that causes memory stall cycles. Generates structured tuning recommendations for optimal tile and warp dimensions.

Submission format

Runnable source, pinned dependencies, setup commands, working interface, example outputs, recorded demo, tests, and action logs.

Datasets

Challenge datasets

Public datasets, plus the private datasets you have access to.

Evaluation rubric

How submissions are scored

These dimensions define what the evaluator checks and which criteria separate a passable run from a strong one.

Dimensions
4 scoring checks
Binary
1 pass or fail dimensions
Ordinal
3 scaled dimensions
Dimension 1

Complete workflow

Ingest profiling trace outputs from local Triton kernel compilation and execution benchmarks. Extract kernel execution times, shared memory allocations, and register spill counts. Compare candidate fused kernels against standard unquantized PyTorch baseline operations. Use hosted Claude API to synthesize kernel tuning recommendations and block size heuristics.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 2

Correctness and evidence

Calculates percentage speedup or regression of candidate kernels over baseline operations. Identifies register spilling into local memory that causes memory stall cycles. Generates structured tuning recommendations for optimal tile and warp dimensions.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 3

Review interface

Kernel benchmark comparator dashboard with memory footprint graphs and tuning report export.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 4

Safe execution

Benchmarks open-source Triton code in isolated local user environments without accessing closed server systems.

Binary check

This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.

Learning goals

What you should walk away with

  • Ingest profiling trace outputs from local Triton kernel compilation and execution benchmarks.

  • Extract kernel execution times, shared memory allocations, and register spill counts.

  • Compare candidate fused kernels against standard unquantized PyTorch baseline operations.

  • Use hosted Claude API to synthesize kernel tuning recommendations and block size heuristics.

Resources and assets

Reference links and supporting material

Dataset notes

Create normalized synthetic benchmark tables representing Triton attention kernel runs across varying tile sizes. Supplied starter examples are synthetic, not source extracts.

Challenge setup

Configuration summary for this challenge.

Challenge input

Input details are not configured.

MLflow

MLOps

Evaluated output

No output checks are configured.

Evaluation checks
  • Ingest profiling trace outputs from local Triton kernel compilation and execution benchmarks. Extract kerne...
  • Calculates percentage speedup or regression of candidate kernels over baseline operations. Identifies regis...
  • Kernel benchmark comparator dashboard with memory footprint graphs and tuning report export.
Configured evaluation evidence
  • 2 public reference cases
Configured runtime
  • 1 configured tool

Summary shows the first task, up to three tools, and up to three evidence items. Open the technical recipe to view all configured items.

View technical recipe

Configured tools

Action Space
  • MLflow · Optional

Evaluation contract

  • Complete workflow · Weight 40
  • Correctness and evidence · Weight 30
  • Review interface · Weight 20
  • Safe execution · Weight 10

Reference cases

  • 2 public reference cases

Workflow tasks

No workflow tasks are configured.

Recipe freeze marker

No recipe freeze time is recorded.

Frequently Asked Questions about Build a Local Open-Weight Triton Kernel Latency and Memory Auditor