argent-react-native-profiler

To identify React Native re-renders and CPU hotspots, profile Hermes CPU sampling and React render commits, then analyze the session to rank commits by total render time. This captures exactly which work is expensive and quantifies component re-render costs.

The best way to measure React Native performance optimization impact is running a before/after profiling cycle. Capture Hermes commits and CPU data prior to changes, then re-profile after to generate ranked reports comparing component and commit costs.

To profile Hermes CPU time and React commits on a device, start the React profiling tool targeting a specific device_id and port. Complete your key user interaction, stop the profilers, and generate a CPU-enriched analysis report.

Yes, you can drill down into component and function-level performance bottlenecks using component, commit, call-tree, and stack query tools. These queries pinpoint root causes by cross-correlating CPU sampling data with React commit timelines.

Yes, React Native profiling supports reproducible interaction recording through optional flow-based interaction recording. This ensures consistent measurement across before/after optimization cycles by standardizing the user interaction being profiled.