tune

Profile TileOPs GPU kernel latency and bottlenecks with CUDA-event timings.

168|55|Updated Jun 3, 2025
One-click install
npx skills add https://github.com/tile-ai/TileOPs --skill tune
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tune
Source: https://github.com/tile-ai/TileOPs/tree/main/.claude/skills/tune
Command: npx skills add https://github.com/tile-ai/TileOPs --skill tune

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide provides a repeatable methodology to measure, analyze, and tune GPU kernel performance in TileOPs, ensuring reported metrics reflect GPU-only execution and that autotune trial runs do not contaminate profiler traces.

Core Features & Use Cases

  • Authoritative Benchmarking: Run the benchmarks/ops bench_xxx scripts to obtain median GPU-only latencies for fair comparisons between kernel variants and configs.
  • Clean Tracing Workflow: Disable autotune and fix the best config before profiling with nsys so aggregated kernel stats reflect steady-state behavior.
  • Deep Metric Analysis: Use ncu (Nsight Compute) for per-metric inspection (memory throughput, L1/L2/HBM hit rates, occupancy, stall reasons) and apply practical TMPDIR and launch-skip/launch-count workarounds.
  • Tuning SOP & PR Rules: Standardized workflow from benchmarking to profiling to PR submission, including required performance tables and autotune config disclosures.

Quick Start

Run the benchmark to collect median GPU-only latency, disable autotune to fix the config, and then run nsys or ncu to capture clean kernel traces for analysis.

Frequently Asked Questions about tune

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

FAQPage Schema
How do I profile GPU kernel performance to identify bottlenecks?▼

To profile GPU kernel performance, run benchmark scripts to measure CUDA-event median latency, disable autotune to fix the best config, and use Nsight Compute to inspect per-kernel metrics like memory throughput and stall reasons.

Why does autotune contaminate profiler traces and how do I prevent it?▼

Autotune contaminates profiler traces by running multiple trial configurations, skewing aggregated kernel stats. Prevent this by disabling autotune and fixing the best configuration before profiling with nsys to capture steady-state behavior.

What GPU performance metrics should I analyze when benchmarking TileOPs kernels?▼

When benchmarking TileOPs kernels, analyze memory throughput, L1/L2/HBM hit rates, occupancy, and stall reasons using Nsight Compute to identify GPU kernel performance bottlenecks accurately.

Can I use nsys and ncu for regression analysis on GEMV and MHA operators?▼

Yes, you can use nsys and ncu for regression analysis on GEMV, MHA/GQA, and other TileOPs operators by comparing autotuned configurations and measuring GPU-only latency through benchmark scripts.

What's the best way to ensure benchmark metrics reflect GPU-only execution?▼

To ensure benchmark metrics reflect GPU-only execution, use benchmark scripts that report CUDA-event median timings and apply practical TMPDIR and launch-skip/launch-count workarounds during Nsight Compute profiling.

Do I need to disable autotune before profiling with nsys?▼

Yes, you need to disable autotune and fix the best config before profiling with nsys so aggregated kernel stats reflect steady-state behavior without contamination from trial runs.