Measure CPU startup time locally
Oxygen deployments can sometimes fail due to the app startup time exceeding the limit of the platform. This guide shows you how to measure the startup time of your app locally and find out ways to optimize it.
Step 1: Run the CPU profilerAnchor link to section titled "Step 1: Run the CPU profiler"
To measure the startup time of your app, run the CPU profiler with following command in your terminal:
This command builds your app and runs the generated bundle code once. It then watches for changes and rebuilds the app when necessary.
Every time you save a file, an updated startup time measure is logged to the terminal. You can use this information to observe trends when making changes in your app.
Step 2: View the startup time reportAnchor link to section titled "Step 2: View the startup time report"
The CPU profiler displays your app's startup time in the terminal. It also generates a more comprehensive startup time report and saves it to
Step 3: Optimize your startup timeAnchor link to section titled "Step 3: Optimize your startup time"
After you find the parts of your app that contribute to the startup time, you can start optimizing them. Some common scenarios that can cause slow startup times include the following:
- Using dependencies that perform unnecessary computations during import. For example, a dependency might establish a connection with a third-party API during import.
- Calling functions or template literals that perform computation outside of a request cycle, such as at the top-level of a module. For example, a common scenario is using
graphql-tagto parse GraphQL queries at the top level of a route file, which internally transforms strings into AST objects. This can be avoided by using a
#graphqlcomment instead, which turns on syntax highlighting for GraphQL queries without parsing them.