fix: speed up dashboard loading - #3121
Merged
Merged
Conversation
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Why
The landing page eagerly loaded large optional chunks, fetched multi-megabyte read models it did not render, and repeatedly refreshed expensive readiness and analytics projections during active execution.
Performance verification
Measurements were taken against the local production build on the dashboard loopback URL with a fresh headless browser context.
Validation
pnpm run lintpnpm run test:backend— 5,743 passed, 7 skippedpnpm run test:dashboard— 2,279 passed, 1 skippedpnpm run buildScreenshots are not included because the change is performance-focused and does not intentionally alter dashboard appearance.
Risk and rollback
Risk is limited to Overview read-model freshness and lazy shell boundaries. Full task APIs remain unchanged by default, detailed Stats remains realtime, and all reduced-frequency resources retain polling or structure-event refreshes. Roll back this PR to restore the prior loading behavior.