Skip to content

Commit 8977432

Browse files
committed
""
1 parent b4c3b0b commit 8977432

File tree

1 file changed

+5
-9
lines changed

1 file changed

+5
-9
lines changed

docs/profiling.md

Lines changed: 5 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -5,20 +5,16 @@ title: Profiling
55

66
Profiling is the process of analyzing an app's performance, resource usage, and behavior to identify potential bottlenecks or inefficiencies. It's worth making use of profiling tools to ensure your app works smoothly across different devices and conditions.
77

8-
React Native provides several modern profiling tools for different platforms and use cases:
9-
10-
- **Android**: [Android Studio Profiler](#profiling-android-ui-performance-with-system-tracing) (recommended), [Flipper](#flipper)
11-
- **iOS**: [Instruments](#ios-instruments), [Flipper](#flipper)
12-
- **JavaScript/React**: [Chrome DevTools](#chrome-devtools), [React DevTools](#react-devtools)
13-
14-
:::note Legacy Tool
15-
[Systrace](systrace.md) is deprecated as of React Native 0.82. Use Android Studio Profiler for Android profiling instead.
16-
:::
8+
For iOS, Instruments is an invaluable tool, and on Android you should learn to use the Android Studio Profiler.
179

1810
But first, [**make sure that Development Mode is OFF!**](performance.md#running-in-development-mode-devtrue).
1911

2012
## Profiling Android UI Performance with System Tracing
2113

14+
:::caution Systrace Deprecation Notice
15+
Systrace is deprecated as of React Native 0.82. For modern Android profiling, use [Android Studio Profiler](#profiling-android-ui-performance-with-system-tracing) instead.
16+
:::
17+
2218
Android supports 10k+ different phones and is generalized to support software rendering: the framework architecture and need to generalize across many hardware targets unfortunately means you get less for free relative to iOS. But sometimes, there are things you can improve -- and many times it's not native code's fault at all!
2319

2420
The first step for debugging this jank is to answer the fundamental question of where your time is being spent during each 16ms frame. For that, we'll be using the [built-in System Tracing profiler in the Android Studio](https://developer.android.com/studio/profile).

0 commit comments

Comments
 (0)