ios-ettrace-performance

Capture and interpret iOS Simulator ETTrace profiles to identify performance hotspots.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/harshav167/build-ios-apps --skill ios-ettrace-performance-harshav167
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ios-ettrace-performance
Source: https://github.com/harshav167/build-ios-apps/tree/main/skills/ios-ettrace-performance
Command: npx skills add https://github.com/harshav167/build-ios-apps --skill ios-ettrace-performance-harshav167

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Capture and interpret iOS Simulator ETTrace profiles to identify startup and runtime performance hotspots.

Core Features & Use Cases

  • Symbolicated flamegraph profiling for iOS Simulator apps.
  • Focused launch and runtime tracing with symbolication via dSYMs.
  • Use case: Compare traces across app versions to locate CPU-heavy stacks and latency sources.

Quick Start

Run the ETTrace workflow on your simulator app to capture a focused launch or runtime trace using the provided scripts.

Frequently Asked Questions about ios-ettrace-performance

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

FAQPage Schema
How do I profile iOS Simulator performance bottlenecks using ETTrace?

This Skill profiles iOS Simulator performance by capturing ETTrace data and using symbolicated dSYMs to generate flamegraphs. It identifies startup and runtime bottlenecks by exposing CPU-heavy stacks and latency sources during focused tracing workflows.

What is ETTrace flamegraph analysis used for in iOS apps?

ETTrace flamegraph analysis is used to pinpoint startup and runtime performance hotspots in iOS Simulator apps. By symbolicking traces with dSYMs, developers visually locate CPU-heavy stacks and compare traces across app versions to resolve latency sources.

Do I need dSYMs to symbolicate ETTrace profiles for iOS Simulator?

Yes, dSYMs are required to symbolicate ETTrace profiles. The Skill utilizes the collect_ios_dsyms.sh helper to gather necessary debug symbols, ensuring generated flamegraphs accurately map trace data to specific source code bottlenecks.

Can I compare iOS app launch traces across different versions?

Yes, you can compare traces across app versions to locate CPU-heavy stacks and latency sources. By capturing focused launch or runtime ETTrace profiles, the Skill highlights performance hotspots and bottlenecks appearing between different builds.

What output directory setup is required for ETTrace profiling workflows?

ETTrace profiling workflows require a writable output directory for run artifacts. You must provide this directory to store captured traces, symbolicated dSYM data, and generated flamegraphs used for analyzing runtime performance hotspots.