ascend-profiling-anomaly

Analyze Huawei Ascend NPU profiling traces to detect performance anomalies and bottlenecks.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/dongg622/china-ai-chip-skill --skill ascend-profiling-anomaly-dongg622
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ascend-profiling-anomaly
Source: https://github.com/dongg622/china-ai-chip-skill/tree/main/Ascend/external/gitcode-ascend/ascend-profiling-anomaly
Command: npx skills add https://github.com/dongg622/china-ai-chip-skill --skill ascend-profiling-anomaly-dongg622

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill identifies hidden performance issues and bottlenecks in Huawei Ascend NPU profiling data, enabling targeted optimization efforts.

Core Features & Use Cases

  • Anomaly Detection: Analyzes profiling traces, bottlenecks, and device idle gaps to find hidden performance anomalies.
  • Model and Hardware Analysis: Examines device trace data such as kernel timings, communication patterns, and step structures to reverse-engineer model execution characteristics.
  • Use Case: Helps a performance engineer pinpoint GPU-like bottlenecks, device idle periods, or communication delays in Ascend hardware during model deployment.

Quick Start

Load the profiling data from your Ascend device trace files, and run this Skill to receive detailed anomaly reports highlighting performance hotspots and root causes.

Frequently Asked Questions about ascend-profiling-anomaly

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

FAQPage Schema
How do I detect performance anomalies in Huawei Ascend NPU profiling traces?▼

To detect performance anomalies in Huawei Ascend NPU profiling traces, load your device trace files into this analysis tool. It examines kernel timelines, communication overlaps, and device idle gaps to pinpoint hidden bottlenecks during model execution.

What causes device idle gaps and communication delays during Ascend NPU model deployment?▼

Device idle gaps and communication delays during Ascend NPU model deployment are caused by inefficient kernel timings and unoptimized communication patterns. Analyzing profiling data helps reverse-engineer execution characteristics to reveal these hidden performance hotspots.

Can I analyze kernel timelines and communication overlaps from Ascend hardware trace files?▼

Yes, you can analyze kernel timelines and communication overlaps from Ascend hardware trace files. The anomaly detection process examines device trace data to identify step structures and reverse-engineer model execution characteristics for targeted optimization.

What is the best way to find hidden bottlenecks in Ascend profiling data?▼

The best way to find hidden bottlenecks in Ascend profiling data is running automated anomaly detection on your trace files. This approach isolates performance hotspots and root causes by evaluating kernel timings and communication patterns.

Do I need specific trace file formats to identify performance anomalies on Ascend hardware?▼

You need trace files generated from Ascend hardware profiling to identify performance anomalies. Loading this device trace data allows the analysis of kernel timelines and step structures to successfully reverse-engineer model execution characteristics.