From 1142088fd8039ade6a1780469eeb0348dd699a6b Mon Sep 17 00:00:00 2001 From: Ben Date: Tue, 13 Dec 2022 11:36:47 -0500 Subject: [PATCH] Remove outdated note This log was removed via https://github.com/facebook/react-native/commit/1f25d3c4ce605fc3bd2a4deefc754bd07cfbf1cf, and referencing it can be confusing. --- docs/profiling.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/profiling.md b/docs/profiling.md index 881ec1f591a..469b1da1a10 100644 --- a/docs/profiling.md +++ b/docs/profiling.md @@ -7,7 +7,7 @@ Use the built-in profiler to get detailed information about work done in the Jav For iOS, Instruments is an invaluable tool, and on Android you should learn to use [`systrace`](profiling.md#profiling-android-ui-performance-with-systrace). -But first, [**make sure that Development Mode is OFF!**](performance.md#running-in-development-mode-devtrue) You should see `__DEV__ === false, development-level warning are OFF, performance optimizations are ON` in your application logs. +But first, [**make sure that Development Mode is OFF!**](performance.md#running-in-development-mode-devtrue). Another way to profile JavaScript is to use the Chrome profiler while debugging. This won't give you accurate results as the code is running in Chrome but will give you a general idea of where bottlenecks might be. Run the profiler under Chrome's `Performance` tab. A flame graph will appear under `User Timing`. To view more details in tabular format, click at the `Bottom Up` tab below and then select `DedicatedWorker Thread` at the top left menu.