argent-react-native-profiler

To find React re-renders and CPU hotspots in a Hermes app, you profile the application by starting capture, reproducing the interaction causing the slowdown, and analyzing the sorted report to pinpoint expensive commits and functions.

The best way to profile a Hermes app for slow component discovery is running a complete profiling workflow: start capture, execute the exact user interaction reproducing the slowdown, then analyze the ranked hot commits report to find bottlenecks.

Yes, you can correlate iOS Instruments hangs with React commits by running optional native profiling alongside React capture, then producing a combined report that maps native performance issues directly to React commit behavior.

You trace hot functions and inspect re-render cascades in React Native by using CPU and commit queries after profiling, allowing you to drill down into specific commits, identify the slowest components, and diagnose performance bottlenecks accurately.

React Native performance profiling works without native iOS Instruments by focusing on Hermes CPU sampling and React commit capture, while native correlation remains an optional step for mapping native hangs to commits.