JavaScript, React Native and Performance
summary
React Native teams measure startup where JavaScript takes >80% of VM time and parsing dominates, so they push specific fixes: lazy requires and dead-code stripping to reduce work, a pre-parse cache and bytecode cache to avoid expensive AST/bytecode generation on Android, and a Random Access Bundle format that loads module code from disk on demand instead of parsing one huge bundle. Benchmarks show parallel native init and these JS caches cut perceived startup latency.
AI-written summary · about
chapters (10)
- 0:00JAVASCRIPT, REACT NATIVE & Performance
- 0:49React Native Startup OVERVIEW
- 1:49React Native's GOALS
- 2:25Hybrid APPS
- 3:21Native OPTIMISATIONS
- 4:07LAZY Module Initialisation
- 4:39Smarter BATCHING
- 5:56JavaScript OPTIMISATIONS
- 8:58We shape our code IN TERMS OF THE VM
- 17:10Bytecode CACHE
related talks
30mMaking React Native Fast & Lean
26mOptimizing React Native Performance
39mPerformance Does Matter - Making Your React-Native App Fast
24mThe Performance Myths of React Native apps
31mThe performance myths of React Native
39mPerformance issues: the usual suspects
24mOptimising React Native "Tools and Tips"
23mPractical Performance for React Native