perf-profiler

Profile CPU and memory hotspots to generate flame graphs and JFR/perf evidence.

951|110|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/avifenesh/awesome-slash --skill perf-profiler-avifenesh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: perf-profiler
Source: https://github.com/avifenesh/awesome-slash/tree/main/plugins/perf/skills/perf-profiler
Command: npx skills add https://github.com/avifenesh/awesome-slash --skill perf-profiler-avifenesh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Profiling CPU and memory hotspots to identify performance bottlenecks and provide actionable evidence.

Core Features & Use Cases

  • Run profiling tools and capture hotspots.
  • Generate flame graphs and JFR/perf evidence for bottlenecks.
  • Use in long-running services, batch jobs, and benchmarks to pinpoint slow paths.

Quick Start

Profile the target application using perf-profiler to generate a flame graph for the hottest CPU path.

Frequently Asked Questions about perf-profiler

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

FAQPage Schema
How do I profile CPU and memory hotspots in a long-running service?

Profiling CPU and memory hotspots involves running tracing tools on your long-running service to capture performance bottlenecks, producing flame graphs or JFR evidence that pinpoint slow paths.

What is a flame graph and when do I need it for performance tracing?

A flame graph is a visual representation of tracing data that reveals performance bottlenecks in your application. You need it when profiling CPU and memory hotspots in long-running services or batch jobs to pinpoint slow paths.

Do I need debug symbols to generate a flame graph for my application?

Yes, generating a flame graph requires debug symbols to accurately map tracing data to source code. This evidence is necessary to precisely identify CPU and memory hotspots in your application.

Can I use perf tracing for batch jobs and benchmarking?

Yes, perf tracing is suitable for batch jobs and benchmarking to capture CPU and memory hotspots. It produces structured artifacts like JFR evidence to reveal performance bottlenecks.

What is the best way to identify performance bottlenecks in long-running services?

The best way to identify performance bottlenecks is profiling CPU and memory hotspots using tracing tools. This generates structured artifacts like flame graphs, providing actionable evidence for slow paths.