MCP HubMCP Hub
SKILL·D3BB1C

analyze-kernel-bottleneck

pjt222
Actualizado 1 month ago
9 vistas
26
3
26
Ver en GitHub
Otrogeneral

Acerca de

Esta habilidad de Claude analiza núcleos de GPU para clasificarlos como limitados por cálculo, memoria o latencia mediante análisis de techo de rendimiento, cálculos de ocupación e inspección de instrucciones SASS. Proporciona una matriz de decisión para recomendar estrategias de optimización específicas como cp.async o tiling. Úsela para perfiles avanzados de rendimiento de núcleos CUDA y para guiar optimizaciones específicas de GPU.

Instalación rápida

Claude Code

Recomendado
Principal
npx skills add pjt222/agent-almanac -a claude-code
Comando PluginAlternativo
/plugin add https://github.com/pjt222/agent-almanac
Git CloneAlternativo
git clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/analyze-kernel-bottleneck

Copia y pega este comando en Claude Code para instalar esta habilidad

Documentación

Analyze Kernel Bottleneck

Identify GPU kernel = compute-bound, memory-bound, latency-bound. Baseline perf → roofline classify → occupancy + compute/load ratio/tile → SASS instr mix + stall codes → smem cliff → decision matrix → right opt strategy.

Use When

  • Pre-opt any CUDA kernel → baseline + classify
  • After 1st working ver → ID opt path
  • Underperforms vs theoretical peak
  • Deciding cp.async vs larger tiles vs algorithmic restructure

In

  • Required: Compiled kernel (.cubin or .cu + build cmd)
  • Required: Bench harness launching via CUDA event timing
  • Required: Problem dims (M, N, K for GEMM; seq_len, heads, head_dim for attention)
  • Optional: Target GPU arch (default: GA104 / sm_86 / RTX 3070 Ti)
  • Optional: Expected peak util % for compare
  • Optional: Prior profiling data (Nsight Compute)

Do

Step 1: Baseline Perf

Run kernel w/ CUDA events (BenchTimer), record ms. Calc effective throughput:

  1. Compile if not built:
    nvcc --cubin -arch=sm_86 -O2 -o kernel.sm_86.cubin kernel.cu
    nvcc -arch=sm_86 -O2 -o bench bench.cu -lcuda -I../../phase2/common
    
  2. Run representative sizes, warmup pre-measurement:
    ./bench 4096 4096 4096
    
  3. Record kernel ms from CUDA events (not wall-clock).
  4. Calc effective GFLOPS + BW:
    • GEMM: effective_gflops = (2 * M * N * K) / (time_ms / 1000) / 1e9
    • BW-limited: effective_bw = total_bytes / (time_ms / 1000) / 1e9
    • Flash Attention: effective_gflops = (4 * batch * heads * seq_len^2 * head_dim) / (time_ms / 1000) / 1e9

Baseline: kernel ms, effective GFLOPS, effective BW.

If err: Check launches no err (CHECK_CU). Warmup pre-measurement. Dims large enough saturate GPU (small → launch overhead bottleneck).

Step 2: Roofline Classify

Arithmetic intensity vs machine balance → classify:

  1. Calc AI: AI = FLOPs / bytes_loaded_from_global_memory. Count only unique bytes from DRAM (not shared mem or register reuse).
  2. Lookup balance: balance = peak_compute / peak_bandwidth.
  3. Classify: AI < balance → memory-bound. AI > balance → compute-bound.

GA104 (RTX 3070 Ti) Reference:

ResourcePeakUnit
FP32 FFMA21.7TFLOPS
FP16 Tensor Core (HMMA)174TFLOPS
INT8 Tensor Core (IMMA)696TOPS
DRAM Bandwidth608GB/s
L2 Cache4MB
SMs48

Derived Balance Points:

PrecisionBalance Point (FLOP/byte)
FP32 FFMA21700 / 608 = 35.7
FP16 TC174000 / 608 = 286.2
INT8 TC696000 / 608 = 1144.7
  1. Compute attained: attained = effective_throughput / peak_throughput. Memory-bound → compare effective BW to 608 GB/s. Compute-bound → compare effective GFLOPS to relevant peak.

Classification: compute-bound, memory-bound, latency-bound (low occupancy → neither saturated) + numerical justification.

If err: Recheck byte counting. Watch redundant re-reads (e.g., 9x in direct conv2d no im2col). Neither saturated → latency-bound (Step 3).

Step 3: Occupancy

Active warps/SM from launch config + resource usage:

  1. Extract resource usage:
    nvcc --cubin -arch=sm_86 -O2 --resource-usage -o kernel.sm_86.cubin kernel.cu 2>&1 | grep -E 'registers|smem'
    
  2. Launch config: warps_per_block = threads_per_block / 32.
  3. Blocks/SM per limiting factor:
    • Register: floor(65536 / (registers_per_thread * threads_per_block))
    • Smem: floor(available_smem_per_SM / smem_per_block) → see Step 6 cliff
    • Warp: floor(48 / warps_per_block) (GA104 max: 48 warps/SM)
    • Block: 16 blocks/SM max GA104
  4. Actual blocks/SM = min(register_limit, smem_limit, warp_limit, block_limit).
  5. Active warps/SM = blocks_per_SM * warps_per_block.
  6. Key threshold: 8 warps/SM enough latency hiding GA104. <8 = structural → latency-bound.

Occupancy table: blocks/SM, active warps/SM, limiting factor (registers, smem, warps).

If err: Check cuFuncSetAttribute for dynamic smem. Verify --resource-usage matches actual launch config. High register → --maxrregcount=N (trade spills for occupancy).

Step 4: Compute/Load Ratio/Tile

Count compute instrs + load bytes/K-tile from SASS (not src):

  1. Disassemble:
    cuobjdump -sass kernel.sm_86.cubin > kernel.sass
    
  2. Count compute/tile (inner K-tile loop):
    • grep -c 'HMMA' kernel.sass → FP16 TC ops
    • grep -c 'IMMA' kernel.sass → INT8 TC ops
    • grep -c 'FFMA' kernel.sass → FP32 FMA
  3. Count global loads/tile:
    • grep -c 'LDG' kernel.sass → global mem loads
    • Multiply bytes/load (typically 16 bytes for LDG.128)
  4. Ratio: compute_ops / load_ops per tile.
  5. Classify (cp.async threshold, gpu_reflections.md Insight 2):
    • High (>20:1): cp.async net-neg; warp interleaving already hides DRAM latency. Focus algorithmic. Ref: Flash Attention 64 HMMA/tile = high, cp.async -5%.
    • Medium (5-20:1): cp.async may help, benchmark both paths.
    • Low (<5:1): cp.async strongly beneficial; loads dominate, async copy hides latency. Ref: IGEMM 8 IMMA/tile = low, cp.async +35%.

Compute/load ratio + classification (high/medium/low) + cp.async rec.

If err: Count from SASS not src — compiler may fuse, eliminate, reorder. Inner loop only (K-tile iter) not entire kernel.

Step 5: SASS Instr Inspect

Full SASS instr mix + stall codes:

  1. Disassemble (if not Step 4):
    cuobjdump -sass kernel.sm_86.cubin > kernel.sass
    
  2. Count instr types:
    grep -c 'HMMA.16816' kernel.sass      # FP16 Tensor Core
    grep -c 'IMMA.16816' kernel.sass      # INT8 Tensor Core
    grep -c 'FFMA' kernel.sass            # FP32 fused multiply-add
    grep -c 'LDGSTS' kernel.sass          # cp.async (global->shared)
    grep -c 'LDG' kernel.sass             # Global load
    grep -c 'STS' kernel.sass             # Shared store
    grep -c 'LDS' kernel.sass             # Shared load
    grep -c 'BAR.SYNC' kernel.sass        # Barrier synchronization
    grep -c 'SHFL' kernel.sass            # Warp shuffle (reductions)
    grep -c 'MUFU' kernel.sass            # Special function unit
    
  3. Stall codes critical instrs:
    grep 'HMMA' kernel.sass | head -5     # Expect S08 minimum (hardware constraint)
    grep 'IMMA' kernel.sass | head -5     # Compiler emits S04, reducible to S02 via CuAssembler
    grep 'FFMA' kernel.sass | head -5     # Check for S04 (reducible to S01 on independent FFMAs)
    
  4. ID opt targets:
    • HMMA S08: hardware min Ampere, no reduce. Focus elsewhere.
    • IMMA S04: compiler conservative. CuAssembler → S02 (15-20% gain).
    • FFMA S04: independent → S01 via CuAssembler.
    • Excessive BAR.SYNC: over-sync between pipeline stages.

Instr count table + stall code summary + ID'd opt targets.

If err: cuobjdump arch matches kernel compile target (both sm_86). SASS out empty → cubin corrupt → recompile.

Step 6: Smem Cliff

Smem usage crosses arch-specific occupancy cliff?

  1. Read smem/block from --resource-usage (Step 3) or cuobjdump --res-usage kernel.sm_86.cubin.
  2. Vs cliff:
    • GA104 (sm_86): 100 KB max smem/SM. Cliff at 50 KB/block.
    • Confirmed: 48 KB/block → 2 blocks/SM (good), 56 KB/block → 1 block/SM (2x regression).
  3. Above cliff (smem >50 KB/block):
    • Blocks/SM drops to 1, active warps drop to warps_per_block (typically 4).
    • 2x regression from exposed DRAM stalls.
  4. Double-buffering impact: Doubles smem. 30 KB current → 60 KB double-buf → crosses cliff. Eval async benefit vs occupancy loss.
  5. Record smem/block, blocks/SM, cliff crossed?

Smem/block + blocks/SM + explicit statement cliff crossed.

If err: Above cliff + occupancy bottleneck → change strategy: reduce tile → smem <50 KB, or accept 1 block/SM + compensate higher compute/load ratio (more register reuse, longer K-tiles).

Step 7: Decision Matrix

Synthesize Steps 2-6 → opt strategy:

ConditionStrategy
Memory-bound + low compute/load (<5:1) + smem under cliffSW pipelining cp.async (LDGSTS). Overlap global loads w/ compute.
Memory-bound + high compute/load (>20:1) + 8+ warpsWarp interleaving already hides. Focus algorithmic: implicit GEMM, split-Q, im2col.
Compute-bound + FFMA-heavyCuAssembler stall tighten: S04 → S01 on independent FFMAs.
Compute-bound + HMMA-heavyS08 hardware min, no reduce. Increase tile reuse (larger M/N, longer K-loop).
Compute-bound + IMMA-heavyCuAssembler: S04 → S02 on IMMA (compiler conservative).
Latency-bound (low occupancy)Reduce smem/registers → more blocks/SM. >8 warps/SM.
Smem above cliffReduce tile or restructure → smem/block <50 KB (GA104).
  1. Rank strategies by expected gain, via compute/load + occupancy data.
  2. Estimate gain range per strategy, how far from relevant ceiling.
  3. Flag conflicts: cp.async doubles smem (may cross cliff), larger tiles → register pressure (may reduce occupancy).

Ranked list recommended opts + predicted gain + conflicts.

If err: No clear winner → micro-benchmarks isolate each (cp.async alone, reduced tile alone) → measure actual pre-combine.

Step 8: Doc Findings

Structured bottleneck report:

  1. Baseline: kernel ms, effective GFLOPS + BW, problem dims.
  2. Roofline: AI, classification, attained fraction.
  3. Occupancy: blocks/SM, active warps/SM, limiting factor.
  4. Compute/load: ratio, classification, cp.async rec.
  5. SASS summary: instr counts, stall findings, CuAssembler targets.
  6. Smem cliff: smem/block, blocks/SM, status.
  7. Rec: ranked opt strategies + gain estimates.
## Bottleneck Analysis Report: [kernel_name]

### Baseline
- Problem: [dimensions]
- Kernel time: [X] ms
- Effective GFLOPS: [Y] | Effective BW: [Z] GB/s

### Roofline Classification
- Arithmetic intensity: [AI] FLOP/byte
- Balance point: [BP] FLOP/byte ([precision])
- Classification: **[compute|memory|latency]-bound**
- Attained fraction: [X]% of peak

### Occupancy
| Resource | Per Block | Limit/SM | Blocks/SM |
|----------|-----------|----------|-----------|
| Registers | [N]/thread | 65536 | [B] |
| Shared mem | [X] KB | 100 KB (cliff: 50 KB) | [B] |
| Warps | [W] | 48 | [B] |
| **Limiting** | | | **[min(B)]** |
- Active warps/SM: [W] ([sufficient|insufficient] for latency hiding)

### Compute/Load Ratio
- Compute ops/tile: [N] [HMMA|IMMA|FFMA]
- Load bytes/tile: [N] bytes ([N] LDG x [N] bytes)
- Ratio: [X]:1 — **[high|medium|low]**
- cp.async recommendation: [beneficial|neutral|detrimental]

### SASS Instruction Mix
| Instruction | Count | Notes |
|-------------|-------|-------|
| HMMA.16816 | [N] | Stall: S08 (hardware min) |
| IMMA.16816 | [N] | Stall: S04 (reducible to S02) |
| FFMA | [N] | Stall: S04 (reducible to S01) |
| LDG | [N] | |
| LDGSTS | [N] | cp.async |
| BAR.SYNC | [N] | |

### Smem Cliff
- Smem/block: [X] KB — [under|over] 50 KB cliff
- Blocks/SM: [B] — [no occupancy loss|occupancy halved]

### Recommended Optimizations (ranked)
1. [Strategy] — estimated [X-Y]% gain
2. [Strategy] — estimated [X-Y]% gain
3. [Strategy] — estimated [X-Y]% gain

Complete MD report consumable by kernel-optimizer agent or dev.

If err: Re-run different sizes (1024, 2048, 4096, 8192) → confirm not size-specific. Small may appear latency-bound when real bottleneck at scale is BW.

Check

  • Baseline via CUDA events (not wall-clock)
  • Roofline classification (compute/memory/latency bound)
  • Occupancy + limiting factor
  • Compute/load ratio/tile from SASS
  • SASS instr mix + stall codes documented
  • Smem cliff vs arch threshold
  • Decision matrix + strategy rec
  • Findings in structured report

Traps

  • Re-read multiply: Direct conv2d reads weight 9x no im2col → byte count inflated 9x. Use actual unique bytes from DRAM, not total load instrs, for AI.
  • Confuse FP16 TC peak w/ FP32: FP16 TC peak 174 TFLOPS, FP32 FFMA 21.7 TFLOPS — 8x diff. Wrong peak → roofline meaningless.
  • Using 64 KB cliff not 50 KB GA104: GA104 (sm_86) 100 KB max smem/SM. Cliff 100/2 = 50 KB/block, not 64 KB. Arch-specific; other GPUs differ.
  • Ignore warp interleaving when eval cp.async: 8 warps long compute (high compute/load) already hide DRAM via warp sched. cp.async → smem pressure + barrier overhead no benefit (Flash Attention -5%).
  • Count instrs from src not SASS: Compiler may fuse, eliminate dead, unroll differently, reorder. Always from cuobjdump -sass.
  • No warmup iters: 1st launch → JIT compile overhead + cold cache. 2-5 warmup pre-measured run.

  • pipeline-gpu-kernel — impl SW pipelining cp.async when memory-bound + low compute/load
  • simulate-cpu-architecture — complementary arch analysis CPU-side bottlenecks in host-device workflows

Repositorio GitHub

pjt222/agent-almanac
Ruta: i18n/caveman-ultra/skills/analyze-kernel-bottleneck
0
agentsagentskillsai-assisted-developmentclaude-codeskillsteams
FAQ

Frequently asked questions

What is the analyze-kernel-bottleneck skill?

analyze-kernel-bottleneck is a Claude Skill by pjt222. Skills package instructions and resources that Claude loads on demand, so Claude can perform analyze-kernel-bottleneck-related tasks without extra prompting.

How do I install analyze-kernel-bottleneck?

Use the install commands on this page: add analyze-kernel-bottleneck to Claude Code as a plugin, or clone its repository into your skills directory, then restart Claude so it picks up the skill.

What category does analyze-kernel-bottleneck belong to?

analyze-kernel-bottleneck is in the Other category, tagged general.

Is analyze-kernel-bottleneck free to use?

Yes. analyze-kernel-bottleneck is listed on AIMCP and free to install. It runs inside Claude, so no separate service account is required to use the skill itself.

Habilidades relacionadas

llamaguard
Otro

LlamaGuard es el modelo de Meta de 7-8B parámetros para moderar las entradas y salidas de LLM en seis categorías de seguridad como violencia y discurso de odio. Ofrece una precisión del 94-95% y puede implementarse usando vLLM, Hugging Face o Amazon SageMaker. Utiliza esta skill para integrar fácilmente filtrado de contenido y barreras de seguridad en tus aplicaciones de IA.

Ver habilidad
cost-optimization
Otro

Esta Skill de Claude ayuda a los desarrolladores a optimizar los costes en la nube mediante el ajuste de tamaño de recursos, estrategias de etiquetado y análisis de gastos. Proporciona un marco para reducir los gastos en la nube e implementar una gobernanza de costes en AWS, Azure y GCP. Úsala cuando necesites analizar los costes de infraestructura, ajustar el tamaño de los recursos o cumplir con restricciones presupuestarias.

Ver habilidad
sports-betting-analyzer
Otro

Esta habilidad de Claude analiza los mercados de apuestas deportivas, incluyendo spreads, over/unders y apuestas de propuestas, mediante el examen de tendencias históricas y estadísticas situacionales para identificar apuestas de valor. Proporciona una salida en markdown estructurado con recomendaciones accionables con fines educativos. Los desarrolladores deben utilizar esto para herramientas de análisis de apuestas deportivas, teniendo en cuenta que está diseñado únicamente para entretenimiento/educación.

Ver habilidad
quantizing-models-bitsandbytes
Otro

Esta habilidad cuantiza LLMs a precisión de 8 o 4 bits utilizando bitsandbytes, logrando una reducción de memoria del 50-75% con pérdida mínima de precisión. Es ideal para ejecutar modelos más grandes en memoria GPU limitada o para acelerar la inferencia, admitiendo formatos como INT8, NF4 y FP4. La habilidad se integra con HuggingFace Transformers y permite entrenamiento QLoRA y optimizadores de 8 bits.

Ver habilidad