React Native Performance In Marketplace
Article Summary
Facebook cut React Native Time to Interaction in half on low-end Android devices. The secret? They stopped trusting their testing tools and went straight to production data.
Facebook's engineering teams collaborated to dramatically improve Marketplace performance in 2017. They discovered that traditional profiling tools like Systrace and CTScan were wildly inaccurate for production scenarios, sometimes off by thousands of milliseconds. So they built a meticulous production instrumentation system based on millions of real user samples.
Key Takeaways
- Removed thread blockages by eliminating AsyncTask dependencies, reducing startup by 25%
- Stopped pre-loading unnecessary JavaScript modules, making bundle execution 75% faster
- Production data revealed testing tools were not representative of real-world performance
- Lazy injection of native module dependencies cut initialization cost by 98%
- Bridge startup cost reduced by 80% through targeted architectural improvements
Facebook halved Marketplace TTI on low-end Android devices by ditching synthetic benchmarks for production instrumentation and systematically eliminating thread contention.
Continue reading
What This Article Covers
Facebook's Marketplace team found that threads jumping to busy threads created expensive blockages when React Native started up. Their initial instrumentation didn't catch these stalls across millions of production samples.
The team removed AsyncTask dependencies and stopped forcing ReactContext initialization on the UI thread. They also eliminated ReactRootView measurement at startup to reduce thread contention.
These fixes cut Marketplace startup time by over 25%. It shows that changes to React Native's architecture can improve performance in ways that JavaScript optimization alone cannot.
This page summarizes “React Native Performance In Marketplace” by React Native Blog, published Aug 7, 2017. All credit for the original work goes to the authors.
