Use Flame Graphs to Find Exact Performance Bottlenecks

Access the Flame Graph View

Open Node Pulse Monitor and navigate to the Flame Graphs or Stack Traces tab. This shows a hierarchical breakdown of where CPU time is actually being spent during execution.

Read the Graph Structure

Each block represents a function or method. Wider blocks consumed more CPU time. The vertical axis shows call depth—how nested the function is. Scan for unusually wide blocks, as these are your bottlenecks.

Identify the Mod Responsible

Flame graphs are color-coded by mod. Hover over or select blocks to see which mod owns that code. This pinpoints not just *which mod* is slow, but *which specific function* within that mod is the problem.

Drill Down into Hot Spots

Click on wide blocks to zoom in and see the functions they call. This reveals whether a mod's slowness comes from rendering, entity ticking, data processing, or something else entirely.

Share or Document Findings

Take a screenshot of the flame graph showing the bottleneck. If reporting a bug to mod authors, this visual evidence is far more useful than vague "it's laggy" reports. Include the specific function names shown in the graph.