perfetto-trace-analysis

Analyze Perfetto trace files to identify Android latency, memory, or UI jank root causes.

174|8|Updated Jan 9, 2024

Search Tags:#debugging #profiling #sql #perfetto #trace analysis #ui jank #android performance

Ready to run

npx skills add https://github.com/klxiaoniu/QQVersionList --skill perfetto-trace-analysis-klxiaoniu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: perfetto-trace-analysis
Source: https://github.com/klxiaoniu/QQVersionList/tree/main/.agents/skills/perfetto-trace-analysis
Command: npx skills add https://github.com/klxiaoniu/QQVersionList --skill perfetto-trace-analysis-klxiaoniu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you pinpoint the root cause of Android latency, memory pressure, or UI jank by analyzing Perfetto trace files with evidence-backed, trace-processor SQL workflows.

Core Features & Use Cases

Root-cause trace investigation: Uses domain-hint techniques to systematically isolate CPU, graphics, I/O, IPC, memory, and power bottlenecks rather than guessing.
Evidence-first workflow: Builds a chain of evidence scratchpad by logging verified timestamps, slice/thread identity, and thread states before drawing conclusions.
Automated analysis targeting: If the app/package is not specified, it can identify the active app during broad startup/performance requests and ask the user to choose.
Perfetto SQL rigor: Follows a SQL reference execution protocol (schema discovery, correct module includes, safe handling of incomplete slices, and overlap correctness).

Quick Start

Ask for an analysis of the provided Perfetto trace file, for example: "Analyze this trace to find why the app is janky and identify the root cause."

Frequently Asked Questions about perfetto-trace-analysis

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

FAQPage Schema

How do I find the root cause of Android UI jank using a Perfetto trace?▼

You can find the root cause of UI jank by analyzing your Perfetto trace file to systematically isolate CPU, graphics, I/O, IPC, memory, and power bottlenecks using evidence-backed SQL workflows.

How do I analyze Perfetto SQL trace files for memory pressure?▼

Analyzing Perfetto SQL trace files for memory pressure involves domain-hint driven hypothesis planning and a strict SQL reference execution protocol to verify thread states and slice identity before drawing conclusions.

Can I investigate app startup latency without specifying the package name?▼

Yes, you can investigate app startup latency without specifying the package name; the analysis automatically identifies the active app during broad startup performance requests and asks you to choose.

What is the evidence-first workflow for Android performance debugging?▼

The evidence-first workflow for Android performance debugging builds a chain of evidence by logging verified timestamps, slice identity, and thread states before drawing conclusions about latency or memory issues.

Does Perfetto trace analysis support identifying graphics and IPC bottlenecks?▼

Yes, Perfetto trace analysis supports identifying graphics and IPC bottlenecks by targeting interactive debugging scenarios across CPU, I/O, memory, and power to pinpoint the root cause of latency.

What are the limitations of analyzing incomplete slices in Perfetto traces?▼

When analyzing incomplete slices in Perfetto traces, limitations are mitigated by a strict SQL reference execution protocol that ensures safe handling of incomplete slices and correct overlap analysis before reporting.