-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[HOLD for payment 2024-08-14] [HOLD for payment 2024-08-09] Optimize frontend performance in most recent mode #45528
Comments
Triggered auto assignment to Contributor-plus team member for initial proposal review - @mkhutornyi ( |
Triggered auto assignment to @dylanexpensify ( |
Hi, I'd like to work on this:) |
Can someone please assign me here for the C+ review, thanks |
please assingn me too for #46500 |
Payment Summary
BugZero Checklist (@dylanexpensify)
|
Can you pay me for this review @dylanexpensify , thanks |
On it now, apologies! |
me too for #46500 : ) |
I think we can close this one since we've started creating separate issues for the performance related PRs recently? |
I guess i’m still due payment here 😬 |
|
opps, Let me check upwork once to match that issue |
I am still due payment btw 😄 |
@ishpaul777 were you reviewer here? |
yes! I reviewed #46500 which was linked to this PR |
Roger! Paying today! |
Payment summary: Contributor+: @ishpaul777 $250 Please apply/request! |
Please apply here! |
@dylanexpensify could you please send in the offer. DMed you my upwork profile, i have no upwork connects to apply to job. |
BTW sent offer @ishpaul777, invite to @mkhutornyi, @allgandalf mind applying? |
@mkhutornyi @allgandalf sent offers! |
Upwork being glitchy for me, attempting again today! |
Done! |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
Problem
For moderate to large accounts like @JmillsExpensify's, the app frequently hangs and lags when doing basic actions like approving reports, pinning reports, etc. We know this performance should be better, but is it possible to optimize it only on the frontend, or do we also need to implement pagination to return less total reports.
Solution
Profile the app when it's lagging to see where the most time is being spent and how we might improve it. Determine if optimizations will be sufficient or if pagination is required.
We have started investigating Jason's app performance in this thread.
cc @marcaaron @adhorodyski
Issue Owner
Current Issue Owner: @dylanexpensifyThe text was updated successfully, but these errors were encountered: