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
[Tracking] Audit performance and scalability of Onyx #67140
First, we need a deep and objective assessment of where the current Onyx falls short. What are the specific pain points and performance bottlenecks? Can we optimize the current implementation further, or are we genuinely constrained by its foundational design? This clarity is critical before we can justify any major re-architecture.
Step 2: Define the Vision
Next, we should holistically define what Onyx 2.0 should be, assuming the core philosophy of Onyx 1.0 still makes sense for the kind of app NewDot aspires to be. The app’s scale, usage patterns, and customer demands have evolved significantly since Onyx was first created. We now have a much better understanding of the performance characteristics needed to support our largest customers.
Step 3: Explore the Solution
Once we’ve aligned on (1) clearly defined problems and (2) a shared vision, we can explore the best way forward. That might mean rethinking Onyx’s architecture — or it might validate continuing with incremental improvements. But we’ll be making that choice with solid footing.
Let's take it step by step, acknowledging that we might want to stop after each of these steps:
Objective Analysis
Define the Vision
Explore the Solution
The analysis can very possibly show that the gains are not that large for the App's performance, considering that the large onyx states will not be the norm as more data is paginated for the App. As @kubabutkiewicz noted in his exploration of storage eviction, the size of data is not really a problem on Onyx side as much as the amount of data manipulation that is happening on App side.
As noted in Slack, this is lower priority at the moment than Critical or some other High quality initiatives.
P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!
Activity
melvin-bot commentedon Jul 25, 2025
Triggered auto assignment to @greg-schroeder (
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.blazejkustra commentedon Jul 25, 2025
Commenting for assignment 😶🌫️
mountiny commentedon Jul 25, 2025
Already assigned (you no longer have to comment to be assigned)
41 remaining items
VickyStash commentedon Jan 7, 2026
Hey-hey, it's not overdue, I'm catching up after the vacation!
VickyStash commentedon Jan 9, 2026
Weekly update
fabioh8010 commentedon Jan 22, 2026
Weekly update
Additionally, as we are moving into more smaller issues and focused on simplification of Onyx, we opened a few ones this week:
mountiny commentedon Jan 26, 2026
I am going to keep this one open until all the audit tasks are done, but now I will focus on the improvements over here #80355
fabioh8010 commentedon Jan 27, 2026
No updates this week as we are focusing on the Improvements for now.
melvin-bot commentedon Feb 20, 2026
This issue has not been updated in over 15 days. @tgolen, @chuckdries, @fabioh8010, @blazejkustra, @roryabraham eroding to Monthly issue.
P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!
mountiny commentedon Feb 20, 2026
@fabioh8010 Keeping this tracking open for now
melvin-bot commentedon May 4, 2026
@tgolen, @chuckdries, @fabioh8010, @blazejkustra, @roryabraham, this Monthly task hasn't been acted upon in 6 weeks; closing.
If you disagree, feel encouraged to reopen it -- but pick your least important issue to close instead.
fabioh8010 commentedon May 5, 2026
@mountiny I think we can keep this closed in favor of #80355