Skip to content

[Performance][MEDIUM] General performance investigation for opening app from customer profile trace #46595

Closed
4 of 4 issues completed

Description

@hannojg

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


What performance issue do we need to solve?

We had a customer meeting and they had really bad performance. We recorded multiple profile traces with them.
This issue is about the profile trace for app open.

The collection of issues:

What is the impact of this on end-users?

Slow or completely hanging/blocked app when starting.

List any benchmarks that show the severity of the issue

https://share.firefox.dev/4fgLVcm

Proposed solution (if any)

None yet, I will go through the profile and see what can be optimised, what exactly caused those lags.

List any benchmarks after implementing the changes to show impacts of the proposed solution (if any)

not available yet

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Version Number: v9.0.11-5
Reproducible in staging?: not tested
Reproducible in production?: yes
Email or phone of affected tester (no customers): customer
Logs: See performance file
Notes/Photos/Videos: See attached video
Expensify/Expensify Issue URL: n/a
Issue reported by: @hannojg
Slack conversation: https://expensify.slack.com/archives/C05LX9D6E07/p1721919928992729

View all open jobs on Upwork

Activity

  1. melvin-bot commented on Jul 31, 2024

    @melvin-bot

    Auto-assigning issues to engineers is no longer supported. If you think this issue should receive engineering attention, please raise it in #whatsnext.

  2. hannojg commented on Jul 31, 2024

    @hannojg
    ContributorAuthor

    cc @sakluger (feel free to assign me as I (or someone from my team) will work on this ticket!)

  3. sakluger commented on Aug 5, 2024

    @sakluger
    Contributor

    Hey @hannojg, any updates on this collection of issues?

  4. hannojg commented on Aug 6, 2024

    @hannojg
    ContributorAuthor

    Working through the issues one by one, currently working on this one:

    I will also find someone from my team to help with these performance issues!

  5. sakluger commented on Aug 8, 2024

    @sakluger
    Contributor

    Looks like we are adding some timing performance logging: #46807

  6. sakluger commented on Aug 12, 2024

    @sakluger
    Contributor

    I'm going to change this to a Weekly since it's a tracking issue related to four specific performance investigations.

  7. 93 remaining items

  8. sakluger commented on Apr 30, 2025

    @sakluger
    Contributor

    Good find @Nodonisko! Does it seem like the fast search tree is recreated many times in error, or was that done intentionally?

    Please let us know if you find anything else.

  9. sakluger commented on May 2, 2025

    @sakluger
    Contributor

    @Nodonisko and @hannojg - heads up that I will be OOO from May 5 - 16. Could you please leave at least one update over the next week or two to avoid having this issue go overdue? Thanks!

  10. Nodonisko commented on May 4, 2025

    @Nodonisko
    Contributor

    Sure thing, I will post updates here.

  11. Nodonisko commented on May 5, 2025

    @Nodonisko
    Contributor

    After some more investigation there seems to be also memory leak in component SearchAutocompleteList when using getParticipantsAutocompleteList. But still investigating what's exact reason for that leak.

  12. sakluger commented on May 19, 2025

    @sakluger
    Contributor

    Hey @Nodonisko, I'm back from OOO. Any additional updates?

  13. Nodonisko commented on May 20, 2025

    @Nodonisko
    Contributor

    @sakluger Hi, I recommend closing this one in favor of #60889. I handed all my finding from this issue to @sosek108 and he is continuing with further investigation.

  14. sakluger commented on May 28, 2025

    @sakluger
    Contributor

    Sounds good to me! Closing in favor of #60889.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions