argent-react-native-profiler

To find React Native Hermes performance bottlenecks, profile React commit timings and CPU hotspots during the problematic interaction. This captures render timings alongside native CPU data to identify slow components and trace them to the hottest JS functions causing the issue.

Diagnosing excessive re-renders in React Native requires capturing React commit render timings using profiler tools. By sorting CPU-enriched reports by the slowest renders, you can investigate function, commit, and component-level causes to pinpoint the exact root issue.

To correlate React commit timing with iOS Instruments data, run the React profiler and a native profiler in parallel during the interaction. This captures both JavaScript render timings and native CPU stack information end-to-end for comprehensive analysis.

Yes, you can compare React Native CPU performance before and after changes by recording and replaying specific interaction flows. Profiling these reproducible workflows creates ranked issue reports that make before and after performance comparisons meaningful.

To run Hermes CPU hotspot analysis, you need to start and stop the React profiler during the problematic sequence, optionally running a native profiler in parallel. Then, analyze the session and use query tools to investigate CPU, commit, and stack data for root causes.