mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-15 14:43:36 -05:00
Obvious slow loading of some of the budget info/settings #1451
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#1451
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @youngcw on GitHub (Sep 28, 2024).
Verified issue does not already exist?
What happened?
This isn't really a bug, but at very least its become worse for me lately.
When the budget loads, certain bits of data are correct from the first render, but not all the data/settings are available from the first render. This causes the page to progressively update as that data becomes available. I've attached a screen recording that shows what Im seeing. Its much worse on my phone using my real budget. I think a similar thing is happening on the mobile accounts page where the balances all start at 0 then update after a second or two.
The bits of data/settings that I've seen be affected by this are:
Goal data (goal value and long goal)
Privacy mode
Category Notes
Can these bits of data/settings be made to be available at first render? The category budget, spent and balance fields are, so why not the other bits of info?
I cant seem to get it to happen the demo, so it may have been introduced since the 24.9.0 release.
To recreate:
1.Open the edge build
2. view as many months as you can
3. turn on privacy mode
4. add some notes and or templates (the goal is to add as much data to the screen as possible)
5. refresh the page a few times and watch closely. Sometimes its more noticeable than others.
progressive_load_cut.webm
Where are you hosting Actual?
None
What browsers are you seeing the problem on?
No response
Operating System
None
@MatissJanis commented on GitHub (Sep 28, 2024):
The move to
SyncedPrefswould have caused the privacy mode toggle (and other synced prefs) to appear to be a bit slower. Each time it loads a preference - it performs a separate call to the backend. Individually that's super fast, but if there are hundreds of calls - things can get slow.There's definitely an optimization we could do here (i.e. fetch all synced prefs and store in redux state; and then just get them from the state instead of backend). I'll look into updating that after the upcoming release.
As for the other things: no immediate ideas.
@youngcw commented on GitHub (Oct 2, 2024):
A note one this: it looks like, at least the template data, doesn't load until after a sync has finished. I haven't tested this on desktop but that looks to be part of the reason on mobile.