In this lesson, you will learn how to read the Unity Profiler timeline to identify the specific scripts and methods causing CPU spikes and memory bloat.
Understanding the Profiler Timeline
When you open the Profiler (Window > Analysis > Profiler), you see a vertical timeline representing your game’s performance over time. The most important area is the CPU Usage chart. When you see a tall, jagged mountain on the chart, that represents a frame where your game took significantly longer to process than usual—a "performance spike."
To investigate, click on that specific spike. The bottom pane will switch to the Hierarchy view. By setting the dropdown to Hierarchy and sorting by Time ms, you can see exactly which methods are consuming the most execution time.
Pinpointing Bottlenecks
Look for methods that appear red or orange. If you see your own script names (e.g., Update(), CalculateEnemyPath(), or SpawnObject()) taking up a large percentage of the frame time, you’ve found your bottleneck.
For example, if you have a script doing heavy calculations inside Update():
void Update() {
// Expensive logic here will cause a spike every frame
PerformComplexMath();
}
When you examine this in the Profiler, the Update row will show a high "Self Time." This tells you that the code inside that method is the culprit, rather than a method it calls. If a child method like PerformComplexMath() is high, you know exactly which specific logic to optimize—perhaps by moving it to FixedUpdate, caching values, or using time-slicing.
Memory Spikes
While CPU spikes are about time, Memory spikes (seen in the Memory Profiler module) are about allocations. If you see a "sawtooth" pattern in the Memory chart, it often indicates frequent "garbage collection" (GC). This happens when you create too many temporary objects (like strings or lists) inside Update(). The Profiler helps you identify these allocations so you can recycle objects instead of creating new ones.
Key Takeaway: Use the Profiler's Hierarchy view to isolate specific methods that hold high "Self Time" percentages, allowing you to focus your optimization efforts exactly where they will have the most impact on your game's frame rate.