cpu-profile-analysis

Analyze CPU profiles and DevTools trace files to identify performance bottlenecks.

Updated Aug 23, 2026

Search Tags:#rendering #bottleneck detection #performance analysis #cpu profiling #v8 #devtools trace #input latency

Ready to run

npx skills add https://github.com/THRISHAL12345/Project_X --skill cpu-profile-analysis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cpu-profile-analysis
Source: https://github.com/THRISHAL12345/Project_X/tree/main/apps/vscode-fork/.github/skills/cpu-profile-analysis
Command: npx skills add https://github.com/THRISHAL12345/Project_X --skill cpu-profile-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you understand why an application or editor feels slow by turning CPU profiles and DevTools traces into clear performance findings instead of raw sampling data.

Core Features & Use Cases

CPU profile analysis: Inspect .cpuprofile sampling data to identify hot functions, self time, total time, and call stack patterns.
Trace analysis: Read Trace-*.json files to examine long tasks, function calls, layout and paint work, input latency, and VS Code user timing marks.
Cross-comparison: Compare two code paths or implementations to see which one spends more time in CPU work, rendering, or garbage collection.
Use case: Use it when a VS Code feature is slow, when you need to explain a performance regression, or when you want to pinpoint layout thrashing and blocking handlers.

Quick Start

Provide a .cpuprofile or Trace-*.json file and ask for the main bottlenecks, top hot functions, and any long tasks or rendering delays.

Frequently Asked Questions about cpu-profile-analysis

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

FAQPage Schema

How do I find performance bottlenecks in a V8 CPU profile?▼

To find performance bottlenecks in a V8 CPU profile, analyze .cpuprofile sampling data to identify hot functions, self time, total time, and call stack patterns. This process isolates slow code paths and blocking tasks causing application latency.

How do I investigate input latency and long tasks in a DevTools trace?▼

Investigate input latency and long tasks in a DevTools trace by reading Trace-*.json event streams. Examine function calls, layout and paint work, and VS Code user timing marks to pinpoint blocking handlers and rendering delays.

Can I compare two code implementations to see which causes more garbage collection?▼

Yes, you can compare two code paths or implementations using cross-comparison analysis. This identifies which implementation spends more time in CPU work, rendering, or garbage collection to explain performance regressions.

What is the best way to identify layout thrashing in a desktop editor workflow?▼

Identify layout thrashing in a desktop editor workflow by analyzing DevTools trace files. Examine timing-based stack reconstruction and trace event streams to pinpoint excessive layout, paint work, and blocking handlers.

Does CPU profile analysis work with raw V8 sampling data or only DevTools traces?▼

CPU profile analysis works with both raw V8 .cpuprofile sampling data and DevTools Trace-*.json event streams. It applies timing-based stack reconstruction to inspect hot functions, long tasks, and GC events across both formats.