performance-profiler-tools

Analyze Instruments trace files to identify performance bottlenecks and memory growth patterns.

2|Updated Jun 25, 2023
One-click install
npx skills add https://github.com/paleoterra/PaleoRose --skill performance-profiler-tools
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: performance-profiler-tools
Source: https://github.com/paleoterra/PaleoRose/tree/main/.claude/skills/performance-profiler-tools
Command: npx skills add https://github.com/paleoterra/PaleoRose --skill performance-profiler-tools

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill simplifies the daunting task of interpreting Instruments trace files, allowing you to quickly identify and understand performance bottlenecks in your application.

Core Features & Use Cases

  • Trace Analysis: Parse Instruments .trace files to extract Time Profiler and Allocations data.
  • Regression Detection: Compare multiple trace files to identify performance regressions introduced by new code.
  • Use Case: Analyze two Instruments trace files, one from a baseline build and one from a new feature branch, to quickly identify any performance regressions introduced by recent changes, ensuring your app remains fast.

Quick Start

Analyze the attached Instruments trace file 'app_startup.trace' and identify the top 3 hot paths.

Frequently Asked Questions about performance-profiler-tools

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

FAQPage Schema
How do I analyze Instruments trace files to find performance bottlenecks?

Analyze Instruments trace files by parsing Time Profiler and Allocations data to extract time percentages and memory metrics. This Skill generates performance reports identifying hot paths—the code consuming most CPU time—and memory growth patterns, helping pinpoint where optimization is needed.

Can I compare Instruments traces to detect performance regressions?

Yes. Compare multiple .trace files—such as baseline and feature-branch builds—to identify performance regressions introduced by recent code changes. The Skill generates side-by-side analysis showing time and memory differences between traces.

What data does this extract from Instruments .trace files?

Time Profiler and Allocations data from .trace files are extracted to generate time percentages, memory metrics, hot paths, and memory growth patterns. Results are output with clearly labeled performance reports across iOS and macOS applications.

Does this work with both iOS and macOS Instruments traces?

Yes. This Skill analyzes Instruments trace files from both iOS and macOS applications, supporting Time Profiler and Allocations data across both platforms for comprehensive performance analysis.

How do I identify the top hot paths in my app startup?

Parse your Instruments .trace file to extract Time Profiler call stacks and time percentages. The Skill ranks functions by CPU consumption, displaying top hot paths—the functions consuming most execution time during startup.

What's the difference between analyzing Time Profiler versus Allocations data?

Time Profiler identifies CPU-consuming code paths showing where execution time is spent. Allocations data reveals memory growth patterns and allocation hot spots. This Skill handles both, letting you address CPU performance or memory efficiency separately.