profile

Profile ExecuTorch model execution with per-operator timings and ETDump export.

Updated Apr 30, 2026
One-click install
npx skills add https://github.com/Msabih/executorch --skill profile-msabih
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: profile
Source: https://github.com/Msabih/executorch/tree/main/.claude/skills/profile
Command: npx skills add https://github.com/Msabih/executorch --skill profile-msabih

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Profiling ExecuTorch model execution to quantify on-device performance, identify bottlenecks, and guide optimizations.

Core Features & Use Cases

  • Per-run timing: Measure latency and operator-level timings to pinpoint slow components.
  • ETDump integration: Capture and save execution traces for later analysis with Inspector.
  • Use Case: Compare two model runs to determine which layer or operation contributes most to inference time.

Quick Start

To profile a model run, enable ETDump, execute the forward pass, and inspect results with Inspector.

Frequently Asked Questions about profile

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

FAQPage Schema
How do I profile ExecuTorch model execution timing on-device?

To profile ExecuTorch model execution timing on-device, enable ETDump, execute the forward pass, and inspect the captured results with Inspector to measure per-operator timings and latency.

What is ETDump used for in on-device model profiling?

ETDump is used to capture and save on-device execution traces during model profiling. It enables post-hoc analysis by allowing the Inspector tool to interpret the recorded data and pinpoint slow operators.

Can I measure per-operator timings to identify inference bottlenecks?

Yes, you can measure per-operator timings to identify inference bottlenecks. Profiling quantifies on-device performance by aggregating results across inputs to determine which layer contributes most to inference time.

Do I need the Inspector tool to analyze ETDump data?

Yes, the Inspector tool is required to analyze ETDump data. While ETDump captures the execution traces on-device, Inspector is used for the post-hoc analysis needed to interpret the profiling results and guide optimizations.

How can I compare two model runs to find slow operations?

You can compare two model runs by profiling each execution with ETDump enabled. Aggregating the per-operator timings across inputs allows you to determine which specific layer or operation contributes most to the inference time.

What on-device runtime access is required to profile model performance?

Profiling model performance requires on-device runtime access to execute the forward pass. This direct runtime interaction is necessary to capture accurate timing data and generate the ETDump traces for analysis.