-
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 2023-11-06] [Performance] Optimize setting initial ref in functional components #30208
Comments
Triggered auto assignment to @mountiny ( |
Issue created for tracking purposes. |
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. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.92-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 2023-11-06. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
|
Triggered auto assignment to @trjExpensify ( |
Bug0 Triage Checklist (Main S/O)
|
We only need to pay $250 to @allroundexperts, there was a regression from the PR |
Sounds good! |
Waiting out the regression period still, Melv. |
This is ready @allroundexperts can you make a request on NewDot and we can close this one |
@allroundexperts have you made the request? |
Yes. Good to close. Thanks! |
$250 payment approved for @allroundexperts |
What performance issue do we need to solve?
Setting initial ref in functional components in a way that is running calculation only once
What is the impact of this on end-users?
Slightly more loading time/memory usage of multiple components
List any benchmarks that show the severity of the issue
Gains may be minor, but new approach is following best practices (also discussed on slack with Expensify team )
Proposed solution (if any)
Changing not optimal
useRefs
to other hooks (or setting initial value to useRef if applicable).List any benchmarks after implementing the changes to show impacts of the proposed solution (if any)
It's not optimal to collect those benchmark in this case.
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number:
Reproducible in staging?:
Reproducible in production?:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by:
Slack conversation:
The text was updated successfully, but these errors were encountered: