Understanding Commit Information
What you'll learn: How to interpret the commit data in React DevTools Profiler to understand what triggered each render.
What Is a Commit?
In React profiling terminology, a commit represents a single render pass—from the moment React starts calculating what needs to change through to when those changes are actually applied to the DOM. Think of it like taking a snapshot: each commit captures one complete rendering cycle.
When you record a profile session, React DevTools captures every commit that occurred during that recording. Each commit shows you which components rendered, how long they took, and critically, why they rendered.
Navigating Between Commits
After stopping a recording, you'll see multiple commits listed (often as dots or a timeline). You can click through them one by one to examine what happened during each render pass.
For each commit, the Profiler shows:
- Which components rendered (highlighted in the flame graph or ranked chart)
- Why each component rendered (props change, state change, parent rendered, hooks changed)
- How long the commit took overall
- When it occurred relative to other commits
This is invaluable for debugging performance issues. For example, if you notice a slow commit, you can inspect it to see which component took the longest. If you see unexpected commits, you can check the "why did this render?" information to discover what triggered unnecessary re-renders.
The Investigation Workflow
Click through commits sequentially to build a timeline of what happened: user clicked button → state updated → three components re-rendered → another effect triggered → one more component rendered. Each commit tells part of the story.
Key Takeaway: A commit is one complete render pass, and navigating between commits in the Profiler lets you trace the sequence of renders and identify what triggered each one.