-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Remove Inbox from preloaded navigators to prevent CPU spike on web #84025
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
mountiny
merged 4 commits into
Expensify:main
from
callstack-internal:perf/remove-inbox-from-preloaded-screens
Mar 4, 2026
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
3c3bf8e
remove Inbox from preloaded screens
TMisiukiewicz 9e41c1a
Merge remote-tracking branch 'origin/main' into perf/remove-inbox-fro…
TMisiukiewicz a889052
Merge remote-tracking branch 'origin/main' into perf/remove-inbox-fro…
TMisiukiewicz bc5e14c
update comment
TMisiukiewicz File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can see CPU usage deceases significantly, so 💯 to this change.
But since the most heavy tab is removed from preload tab, I wonder if we really need to preload
WORKSPACESandSETTINGStabs since they're lightweight and most of their data needed for displaying the UI of these two page come fromOpenApp.I tried to remove
usePreloadFullScreenNavigatorsand I don't see different while switching between these tab. Do you have any metric for theusePreloadFullScreenNavigators? And what kind of data did you measured?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@hungvu193 while I do not see much difference on Web, I can see preloading of Workspaces and Setting screens bringing good results on mobile - results when navigating from Home to Workspaces on iOS without preloading:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@TMisiukiewicz Do you think we still need this preload logic on web at all?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@hungvu193 please check this comment. I believe keeping the preloading on web makes sense for both Settings and Workspaces