liveBook · Manning

Flame graph

A flame graph is a hierarchical visualization of call-stack data in which nested horizontal regions represent stack depth and widths indicate aggregated execution time or resource consumption.

How 3 Manning books explain it

Cloud Observability in Action

A flame graph is a hierarchical visualization of collected stack traces in which horizontal extent represents call frequency or resource consumption and vertical position represents stack depth.

How it is used
Uses stack-profile visualizations to debug code and understand runtime or resource usage.
How deep it goes
Explains axes, rectangles, colors, and resource scope with a worked pprof example, but defers detailed rendering internals.
Examples
Demonstrates a Go pprof profile where slowTask() dominates CPU time and appears beneath main().
What you can do after
Diagnose CPU, memory, or I/O bottlenecks by reading widths, stack depth, and caller relationships.

Read how Cloud Observability in Action explains flame graph →

Latency

FlameGraph profiling is a visualization-based profiling technique that represents hierarchical sampled execution costs as nested horizontal bars.

How it is used
Uses sampled execution visualization to locate dominant code paths during performance optimization.
How deep it goes
Explains proportional stack-trace visualization and a profiling workflow, without detailing flame-graph rendering internals.
Examples
Uses recursive Fibonacci, memoization, iteration, Criterion measurements, and a generated performance flame graph.
What you can do after
Diagnose costly execution paths by profiling Rust benchmarks with Criterion and pprof.

Read how Latency explains flame graph →

Troubleshooting Java: Read, debug, and optimize JVM applications

A visualization of an execution stack in which methods are arranged by call level and their widths indicate relative execution time.

How it is used
Uses a profiled execution view to help identify potential latencies and performance problems.
How deep it goes
Explains call levels and relative widths with a worked example, but does not detail the profiling process itself.
Examples
Compares ProductRepository.findById() with PurchaseRepository.findAll() beneath ProductService.getProductNamesForPurchases().
What you can do after
Diagnose potential execution latencies by comparing method widths and highlighting selected graph layers.

Read how Troubleshooting Java: Read, debug, and optimize JVM applications explains flame graph →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.