Skill

performance-profiling

CPU/memory profiling, identifying bottlenecks, flame graphs, hotspot analysis.

npx claudepluginhub sethdford/claude-skills --plugin engineer-debugging

Popularity

Parent stars

Parent forks

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/debugging:performance-profiling

User invocable

Model invocable

Inline context

Default effort

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

Finding where code spends time and memory.

SKILL.md

45 lines · ~411 tokens

Similar Skills

perf-profile

Provides a language-neutral workflow for performance analysis: flamegraph interpretation, allocation tracking, latency profiling, and regression measurement. Activates when latency, throughput, or memory budgets are missed.

odin

perf-profiler

1.7k

Profiles CPU/memory hotspots with perf/JFR, generates flame graphs, reports file:line evidence for performance investigations.

perf

profiling

Profiles apps to identify CPU/memory bottlenecks using runtime tools: clinic.js/0x for Node.js, py-spy/cProfile for Python, Chrome DevTools/Lighthouse for frontend. For slow apps, leaks, high CPU.

alfred-dev

Stats

Parent stars13

Parent forks2

MaintenanceFair

Last CommitMar 11, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Stats

Actions

Help us improve

Share bugs, ideas, or general feedback.

Performance Profiling

Finding where code spends time and memory.

Context

You are profiling code to find bottlenecks. Use CPU and memory profilers.

Domain Context

CPU Profiling: Where does code spend time? Stack sampling at regular intervals

Memory Profiling: What allocates memory? Which objects aren't freed?

Flame Graph: Visual representation; width = time, stacked = call stack

Hot Spots: Functions consuming > 1% of time

Allocation Profiling: Which code allocates the most objects?

Instructions

Start Profiler: CPU profiler (perf, pprof, Java Flight Recorder)

Run Under Load: Profile should see realistic workload

Collect Data: Run for 10-30 seconds; enough to gather signal

Analyze Output: Flame graph or profiler GUI

Identify Hot Spots: Functions consuming most time

Drill Down: Zoom into hot functions; what calls them?

Measure Impact: Change code, re-profile, compare

Anti-Patterns

Profiling single-threaded code then deploying multi-threaded; lock contention changes profiles

Optimizing without profiling; "optimization" is just guessing

Micro-optimizing non-hotspot code; spend time on the hottest functions

Not considering cache effects; CPU cache profilers show real impact

Benchmarking without warm-up; first runs hit different code paths