triton-ascend-case-reduction-sum-large

Autotune BLOCK_SIZE_M and BLOCK_SIZE_N for large-scale 2D reductions in Triton-Ascend kernels.

6|1|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/xchang1121/AutoResearch-CC-hook --skill triton-ascend-case-reduction-sum-large
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triton-ascend-case-reduction-sum-large
Source: https://github.com/xchang1121/AutoResearch-CC-hook/tree/main/skills/triton-ascend/cases/triton-ascend-case-reduction-sum-large
Command: npx skills add https://github.com/xchang1121/AutoResearch-CC-hook --skill triton-ascend-case-reduction-sum-large

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Large-scale 2D reduction workloads in Triton-Ascend kernels suffer from excessive reduction calls on small axes; this Skill reorganizes computation to maximize UB occupancy and minimize reduction steps, delivering faster performance for very large non-reduce axes.

Core Features & Use Cases

  • Autotune configurations explore different tile sizes (e.g., BLOCK_SIZE_M and BLOCK_SIZE_N) to balance compute and memory.
  • Compute-tiling optimizations that reorganize reduction to reduce the number of iterations.
  • Applicable to 2D reductions with extremely large non-reduce axes and moderate reduce axes, achieving significant latency improvements.

Quick Start

Run autotuning on the Triton Ascend kernel to discover optimal BLOCK_SIZE_M and BLOCK_SIZE_N settings for large non-reduce axes.

Frequently Asked Questions about triton-ascend-case-reduction-sum-large

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

FAQPage Schema
How do I optimize large-scale 2D reduction latency in Triton-Ascend kernels?

To optimize large-scale 2D reduction latency in Triton-Ascend kernels, apply autotuning to tile sizes like BLOCK_SIZE_M and BLOCK_SIZE_N to balance compute and memory. This reorganizes computation to maximize UB occupancy and minimize reduction steps.

When should I use autotuning for tile sizes on Ascend reduction workloads?

Use autotuning for Ascend reduction workloads when processing very large non-reduce axes alongside moderate reduce axes. This scenario benefits significantly from exploring different tile sizes to reduce iterations and improve overall kernel latency.

Can I apply compute-tiling optimizations for any 2D reduction shape?

Compute-tiling optimizations are specifically applicable to 2D reductions with extremely large non-reduce axes and moderate reduce axes. This targeted reorganization maximizes UB occupancy and delivers significant latency improvements for these specific shapes.

Why does my Triton-Ascend kernel suffer from excessive reduction calls on small axes?

Triton-Ascend kernels suffer from excessive reduction calls on small axes due to unoptimized tiling. Enforcing UB occupancy-aware tiling and autotuning BLOCK_SIZE_M and BLOCK_SIZE_N reorganizes the reduction to minimize these iterations.