profile

Profile ExecuTorch model execution to collect latency and operator timing metrics.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/huahai2022/execu-xnnpack --skill profile-huahai2022
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: profile
Source: https://github.com/huahai2022/execu-xnnpack/tree/main/.claude/skills/profile
Command: npx skills add https://github.com/huahai2022/execu-xnnpack --skill profile-huahai2022

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Profile ExecuTorch model execution to collect performance metrics, helping you measure latency and operator timing for on-device inference.

Core Features & Use Cases

  • Enable ETDump during model load to collect detailed timing data.
  • Run a forward pass and capture per-layer execution times for performance debugging.
  • Use Inspector to visualize and compare timing results across runs and devices.

Quick Start

Run the profile tool on a loaded model to start collecting etdump and timing data.

Frequently Asked Questions about profile

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

FAQPage Schema
How do I measure on-device model latency and operator timing for ExecuTorch?

To profile on-device performance, you enable ETDump during model load and run a forward pass to capture per-layer execution times and structured operator timing metrics for ExecuTorch.

What is ETDump and how does it help with performance debugging?

ETDump is a data collection mechanism enabled during model load to gather deterministic profiling data. It captures detailed timing data during execution, allowing you to debug slow models and measure precise latency across devices.

Can I visualize and compare timing results across different devices?

Yes, you can use the Inspector to visualize and compare timing results across runs and devices. This helps analyze collected ETDump metrics for performance optimization and benchmarking during on-device inference.

When do I need to profile on-device model execution?

You need to profile on-device model execution when benchmarking inference speed, debugging slow models, or optimizing performance across devices. It provides precise latency measurements and operator timing data for structured analysis.