Investigate the cause of the Performance Regression for 'Open Search Page TTI'

[yuwenmemon]

Recently, we've seen a slew of Performance Regressions getting red-flagged for the 'Open Search Page TTI' flow.

We first saw the uptick in time occur somewhere around the merging of these PRs:

• Keyboard is visible for a brief moment on request/send money page after getting back from currency search page #15205 🟢 - no regression
• Fix miss-matched SMS email suffix on sign in page #15351 🟡 - some regression
• replace onModalHide with onDismiss for the web #15298 🔴 - DeployBlocker triggering regression.

We tried reverting Fix miss-matched SMS email suffix on sign in page #15351 (PR) to no avail. And we DID revert replace onModalHide with onDismiss for the web #15298. Again no help.

So now we're very confused about where this regression is coming from. @roryabraham has graciously created the ability to run the E2E tests on a specific branch a la carte. So we're going to try and use that to simulate git bisect essentially to figure out the offending PR / commit.

In the meantime we've decided to not block the deploy on this. However, to close this issue we should be getting the Open Search Page TTI back to around ~600ms. Currently it's regressed to ~660-700ms

cc @Expensify/mobile-deployers

[MelvinBot]

Triggered auto assignment to @johncschuster (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[MelvinBot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[johncschuster]

Hehe, I was just going to ask about the Bug label in relation to Bug0. I'll go ahead and triage this out.

[MelvinBot]

Current assignee @yuwenmemon is eligible for the Engineering assigner, not assigning anyone new.

[mountiny]

Margelo will try to help here as they initially helped to set this feature up https://expensify.slack.com/archives/C035J5C9FAP/p1677746998910309

[johncschuster]

👍