fla-nvidia-performance

Guides NVIDIA GPU kernel profiling and performance evidence collection for FLA repository changes.

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/swiss-ai/flash-linear-attention --skill fla-nvidia-performance-swiss-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fla-nvidia-performance
Source: https://github.com/swiss-ai/flash-linear-attention/tree/main/.agents/skills/fla-nvidia-performance
Command: npx skills add https://github.com/swiss-ai/flash-linear-attention --skill fla-nvidia-performance-swiss-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Kernel changes in the FLA repository can silently regress throughput or latency, and merge requests often lack the profiling evidence reviewers need. This Skill standardizes how NVIDIA GPU performance work is done, from hardware baselines to NCU profiling and MR-ready benchmark reports. ## Core Features & Use Cases - Hardware baseline rules: Defines which GPUs count as valid performance evidence (sm_90+ datacenter cards, preferred sm_100/sm_103) and which are reference-only. - MR performance evidence checklist: Requires before/after benchmarks, NCU full and source profiles, dense and variable-length workload coverage, and an explicit conclusion on regressions. - Profiling workflow and artifact layout: Provides ready-to-use ncu and benchmark commands plus a standard profile/<run_name>/ directory structure that keeps .ncu-rep files out of git. - Use Case: After optimizing a Triton kernel in fla/ops, run the prescribed benchmark and NCU commands, then paste the summarized metrics into the MR description so reviewers can verify the improvement. ## Quick Start Ask the agent to profile the chunk_kda forward kernel with NCU and prepare before/after benchmark evidence for an MR on an H100.

Frequently Asked Questions about fla-nvidia-performance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I profile a Triton kernel with Nsight Compute?

Run ncu with --set full and --set source, filtering by kernel name regex and capturing one instance, then save the .ncu-rep under profile/<run_name>/reports/. Summarize key metrics like memory throughput, SOL, and occupancy in the MR description.

What performance evidence is required for a kernel MR in FLA?

A kernel MR needs before/after benchmark results on the same hardware and workload, an NCU profile of a representative changed kernel, at least one dense and one variable-length workload, and a stated conclusion on improvements or regressions.

Which NVIDIA GPUs are valid for FLA performance benchmarks?

Datacenter GPUs with sm_90 or newer, such as H100 and H20, are the minimum accepted baseline, with sm_100 and sm_103 preferred. A100, consumer cards, and pre-sm_80 GPUs are reference-only and cannot be the sole MR evidence.

Do I need to run NCU for every kernel change during development?

No. Quick sanity checks with benchmark_training_throughput.py or benchmark_generation.py are enough during iteration to catch large regressions. Full NCU profiling is required only before opening the MR.

Should NCU report files be committed to the repository?

No. Keep .ncu-rep, .nsys-rep, and raw logs out of git. Store them locally under profile/<run_name>/ and paste only a short metrics summary into the MR description.