Benchmark
This app benchmarks cached location read overhead between
react-native-nitro-geolocation and @react-native-community/geolocation.
📊 Benchmark Results
Test Environment:
- Device: iPhone 14 Pro
- React Native: 0.81.4
- Test: 1000 iterations × 5 runs of
getCurrentPositionwith cached location (measuring pure bridge/JSI latency)
Benchmark scope
This benchmark measures cached location reads and the JS-to-native call path. It does not measure cold GPS acquisition, permission dialogs, provider availability, or OS throttling. Nitro does not make GPS acquisition itself 22x faster; it makes cached reads and the JS-to-native path cheaper.
Results
Why is Nitro faster for cached reads?
- Zero Queue Overhead: Cached location responses return immediately without any dispatch queue overhead
- Direct JSI Calls: No JSON serialization or async bridge crossing
- Optimized Architecture: Fast path for cached responses, queue-free delegate callbacks