You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Nikki reported that opening the app (cold start, force closed) on v9.3.20-6 took 11 seconds to reach the Settings page. Her account has fewer than 1,000 reports.
Eliran inspected the logs and BootSplash appears to be taking most of the time (~7.86s for ManualAppStartup span). Sentry profiling from Hubert showed several contributors including derived values computation, SidebarOrderedReportsContextProvider, SearchContextProvider, and an Onyx job.
Cold start P90 metric has been flat around 5.2s for multiple weeks (target: 3s). Warm start keeps improving but cold start remains stuck.
We need to investigate Nikki's traces and the BootSplash flow to identify what's blocking the cold start and find actionable improvements.
On friday and today I've checked three leads where I thought the significant delay can be found:
Today I've investigated 4 clues I had:
LHN is calling unnecessary for requiresAttentionFromCurrentUser — while rendering items for LHN application tries to calculate requiresUserAttention field via requiresAttentionFromCurrentUser(). This field is however already defined in reportAttributes derived values so same value is calculated twice. This leads to unnecessary CPU usage for large accounts
OnyxDerived reportAttributes recomputing during render — reportAttributes.ts:188/224 reduce loop keeps firing while React is mid-render, causing re-render cascades
computeReportName / getReportActionText — report name computation + markdown parsing (Parser.htmlToText) on every render cycle
Results
fix to this issue gives as little ~10ms gain for about 1200 reports. Fix to this issue is small so I'd suggesst to implement this
Sorry for no updates. I've been divided into several tasks. Unfortunately profile from this run ends after ~6seconds, so we have no knowledge about rest 5seconds.
During these 6 seconds there are common works being performed - these occurs on all high traffic accounts. I did not find anything Nikki-account-specific.
I've posted a proposal that aims to reduce getReportsToDisplayInLHN calls from 4 to 1. Automatically shouldReportBeInOptionList call count is also reduced.
changed the title [-][Due for payment 2026-03-13] Investigate slow app cold start (11s to reach Settings page)[/-][+][Due for payment 2026-03-30] [Due for payment 2026-03-13] Investigate slow app cold start (11s to reach Settings page)[/+]on Mar 23, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.41-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
changed the title [-][Due for payment 2026-03-30] [Due for payment 2026-03-13] Investigate slow app cold start (11s to reach Settings page)[/-][+][Due for payment 2026-03-31] [Due for payment 2026-03-30] [Due for payment 2026-03-13] Investigate slow app cold start (11s to reach Settings page)[/+]on Mar 24, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.42-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
changed the title [-][Due for payment 2026-03-31] [Due for payment 2026-03-30] [Due for payment 2026-03-13] Investigate slow app cold start (11s to reach Settings page)[/-][+]Investigate slow app cold start (11s to reach Settings page)[/+]on Mar 27, 2026
Activity
sosek108 commentedon Feb 23, 2026
Status
On friday and today I've checked three leads where I thought the significant delay can be found:
Today I've investigated 4 clues I had:
requiresAttentionFromCurrentUser— while rendering items for LHN application tries to calculaterequiresUserAttentionfield viarequiresAttentionFromCurrentUser(). This field is however already defined in reportAttributes derived values so same value is calculated twice. This leads to unnecessary CPU usage for large accountsResults
sosek108 commentedon Feb 26, 2026
Sorry for no updates. I've been divided into several tasks. Unfortunately profile from this run ends after ~6seconds, so we have no knowledge about rest 5seconds.
During these 6 seconds there are common works being performed - these occurs on all high traffic accounts. I did not find anything Nikki-account-specific.
Functions that takes a lot of miliseconds:
sosek108 commentedon Feb 26, 2026
Here I will be posting updates to my local tests, based on 1076 reports:
sosek108 commentedon Feb 26, 2026
I've posted a proposal that aims to reduce
getReportsToDisplayInLHNcalls from 4 to 1. AutomaticallyshouldReportBeInOptionListcall count is also reduced.Tomorrow I'll check other functions from the list
23 remaining items
sosek108 commentedon Mar 23, 2026
@NikkiWines Thanks! My PRs got merged so this can be merged after regression period
[-][Due for payment 2026-03-13] Investigate slow app cold start (11s to reach Settings page)[/-][+][Due for payment 2026-03-30] [Due for payment 2026-03-13] Investigate slow app cold start (11s to reach Settings page)[/+]melvin-bot commentedon Mar 23, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Mar 23, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.41-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-03-30. 🎊
For reference, here are some details about the assignees on this issue:
[-][Due for payment 2026-03-30] [Due for payment 2026-03-13] Investigate slow app cold start (11s to reach Settings page)[/-][+][Due for payment 2026-03-31] [Due for payment 2026-03-30] [Due for payment 2026-03-13] Investigate slow app cold start (11s to reach Settings page)[/+]melvin-bot commentedon Mar 24, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.42-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-03-31. 🎊
For reference, here are some details about the assignees on this issue:
[-][Due for payment 2026-03-31] [Due for payment 2026-03-30] [Due for payment 2026-03-13] Investigate slow app cold start (11s to reach Settings page)[/-][+]Investigate slow app cold start (11s to reach Settings page)[/+]Julesssss commentedon Mar 27, 2026
Resolved