-
Notifications
You must be signed in to change notification settings - Fork 3k
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-10-09] [HOLD for payment 2023-09-27] [Tracking] Improve ReportScreen re-renders #26087
Comments
Job added to Upwork: https://www.upwork.com/jobs/~010777a443667dee8f |
Triggered auto assignment to @Christinadobrzyn ( |
This comment was marked as off-topic.
This comment was marked as off-topic.
Triggered auto assignment to Contributor Plus for review of internal employee PR - @ntdiary ( |
Assign me :) |
📣 @ospfranco! 📣
|
Hey @ospfranco can you complete these steps for the Upwork job assignment? Thanks! #26087 (comment) |
I'm working with margelo internally, do I need an upwork account @mountiny? |
@Christinadobrzyn @ospfranco is from Margelo so he does not use Upwork |
Ah! So sorry for my confusion @ospfranco! |
I think this can be moved to weekly as it looks like a PR is started. |
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. |
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.75-12 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-10-09. 🎊 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:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
Correct $1000 to @situchan that is it. Oscar is from agency |
Sounds good, sorry for the delay, here is the payment details Payouts due: Issue Reporter: NA Eligible for 50% #urgency bonus? NA- internal job @situchan are you paid through Upwork? If yes, can you accept the offer here - https://www.upwork.com/jobs/~0102af23fe16b91266 |
@Christinadobrzyn Oscar is paid outside of Upwork since he is from Margelo |
Sounds good - thanks @mountiny. @situchan I paid you based on this payment structure in Upwork. closing this but let me know if I'm missing anything |
cc @Christinadobrzyn Seems you have missed #26087 (comment) |
Ah that was my bad too, @fedirjh was additional help on this complex PR, they also reviewed and tested so they should get $1000 too |
Ah sorry for missing that @fedirjh - thank you for letting me know. Can you accept my offer in Upwork here - https://www.upwork.com/jobs/~0102af23fe16b91266 |
Awesome! @fedirjh Paid you based on this payment structure I think we're good to close, please reopen if anything else is needed! |
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
The Report screen has a lot of performance bottlenecks. Mostly they are caused by unnecessary re-renders and given this component is very heavy to render, it can visibly slow down the App.
Solution
This is a tracking issue for multiple PRs and improvements which are found.
We are analysing the render cycles via Flipper Profiler and React Dev Tools and finding where are the bottle necks in the rendering of the component and its sub-tree.
So far we have found bugs regarding shared context and misuse of hooks that cause unnecessary re-renders. It might be an issue of death by a thousand paper cuts where seemingly innocuous changes cause large tree re-renders.
PRs:
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: