You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2025-07-25] [Due for payment 2025-07-18] Improve performance of loading report transactions across components #64163
Problem
Multiple components throughout the app independently filter the entire transaction collection using Onyx selectors to get transactions for specific reports, which causes significant performance overhead.
Solution
Create a centralized transactions computation that group transactions by report IDs and store it as derived value.
Results for creating an expense in an expense chat for 7k reports and 350 transactions: 8.2s → 5.9s (~30% improvement)
changed the title [-][Due for payment 2025-07-18] Improve performance of loading report transactions across components[/-][+][Due for payment 2025-07-25] [Due for payment 2025-07-18] Improve performance of loading report transactions across components[/+]on Jul 18, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.82-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@eVoloshchak@RachCHopkins The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
@RachCHopkins, not sure if checklist is needed here, this wasn't a bug, rather a performance improvement, so there is no PR that has caused this and no regression tests needed
Activity
TMisiukiewicz commentedon Jun 13, 2025
cc @mountiny can I get assigned please?
melvin-bot commentedon Jun 13, 2025
Triggered auto assignment to @RachCHopkins (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.melvin-bot commentedon Jun 23, 2025
@TMisiukiewicz Huh... This is 4 days overdue. Who can take care of this?
TMisiukiewicz commentedon Jun 23, 2025
PR is approved by C+
TMisiukiewicz commentedon Jun 30, 2025
Getting back to this after #63655 revert
melvin-bot commentedon Jun 30, 2025
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.
21 remaining items
[-][Due for payment 2025-07-18] Improve performance of loading report transactions across components[/-][+][Due for payment 2025-07-25] [Due for payment 2025-07-18] Improve performance of loading report transactions across components[/+]melvin-bot commentedon Jul 18, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.82-7 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 2025-07-25. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Jul 18, 2025
@eVoloshchak @RachCHopkins The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
RachCHopkins commentedon Jul 21, 2025
Waiting on checklist please @eVoloshchak
eVoloshchak commentedon Jul 21, 2025
@RachCHopkins, not sure if checklist is needed here, this wasn't a bug, rather a performance improvement, so there is no PR that has caused this and no regression tests needed
RachCHopkins commentedon Jul 23, 2025
Thanks @eVoloshchak! In that case, @roryabraham is this a Standard $250 pricetag?
roryabraham commentedon Jul 23, 2025
@RachCHopkins Yep!
melvin-bot commentedon Jul 25, 2025
Payment Summary
Upwork Job
BugZero Checklist (@RachCHopkins)
RachCHopkins commentedon Jul 28, 2025
Payment Summary:
No Upwork job.
🟢 to request payment @eVoloshchak!
garrettmknight commentedon Dec 18, 2025
$250 approved for @eVoloshchak