diff --git a/docs/next/performance.html b/docs/next/performance.html index 326cd5aed1f..7fb31c6db37 100644 --- a/docs/next/performance.html +++ b/docs/next/performance.html @@ -291,6 +291,9 @@ export default "--indexed-ram-bundle"] ] +
+

Note: If you are using Hermes JS Engine, you do not need RAM bundles. When loading the bytecode, mmap ensures that the entire file is not loaded.

+

Configure Preloading and Inline Requires

Now that we have a RAM bundle, there is overhead for calling require. require now needs to send a message over the bridge when it encounters a module it has not loaded yet. This will impact startup the most, because that is where the largest number of require calls are likely to take place while the app loads the initial module. Luckily we can configure a portion of the modules to be preloaded. In order to do this, you will need to implement some form of inline require.

Investigating the Loaded Modules

diff --git a/docs/next/performance/index.html b/docs/next/performance/index.html index 326cd5aed1f..7fb31c6db37 100644 --- a/docs/next/performance/index.html +++ b/docs/next/performance/index.html @@ -291,6 +291,9 @@ export default "--indexed-ram-bundle"] ] +
+

Note: If you are using Hermes JS Engine, you do not need RAM bundles. When loading the bytecode, mmap ensures that the entire file is not loaded.

+

Configure Preloading and Inline Requires

Now that we have a RAM bundle, there is overhead for calling require. require now needs to send a message over the bridge when it encounters a module it has not loaded yet. This will impact startup the most, because that is where the largest number of require calls are likely to take place while the app loads the initial module. Luckily we can configure a portion of the modules to be preloaded. In order to do this, you will need to implement some form of inline require.

Investigating the Loaded Modules