hippogrief/pobsync
1
0
Fork 0
Code Issues 21 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

(bugfix) Avoid live filesystem scans for backup data summaries #97

New Issue
Closed
opened 2026-06-08 22:40:00 +02:00 by parkel · 0 comments
parkel commented 2026-06-08 22:40:00 +02:00
Owner
Copy Link

Dashboard, hosts list, and host detail currently derive backup data by walking snapshot trees when stored snapshot metadata is missing or incomplete. On large backup targets this can turn ordinary web requests and live-refresh partials into unbounded filesystem scans, causing slow pages and possible OOMs.

Acceptance criteria:

  • Web views do not call full-tree storage scans while rendering dashboard, hosts list, or host detail.
  • Missing or stale snapshot storage metadata is represented as unknown/not measured instead of being recomputed synchronously.
  • Existing stored snapshot metadata is still used for displayed totals where available.
  • Tests guard against accidental tree_usage() calls from stats summary rendering paths.
  • UI copy avoids implying live measurement when values come from stored metadata.

Follow-up work for periodic/cached refresh is tracked separately.

Dashboard, hosts list, and host detail currently derive backup data by walking snapshot trees when stored snapshot metadata is missing or incomplete. On large backup targets this can turn ordinary web requests and live-refresh partials into unbounded filesystem scans, causing slow pages and possible OOMs. Acceptance criteria: - Web views do not call full-tree storage scans while rendering dashboard, hosts list, or host detail. - Missing or stale snapshot storage metadata is represented as unknown/not measured instead of being recomputed synchronously. - Existing stored snapshot metadata is still used for displayed totals where available. - Tests guard against accidental `tree_usage()` calls from stats summary rendering paths. - UI copy avoids implying live measurement when values come from stored metadata. Follow-up work for periodic/cached refresh is tracked separately.
parkel added this to the 1.4 milestone 2026-06-08 22:40:00 +02:00
parkel added the area: observabilitybugfix labels 2026-06-08 22:40:00 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area: future
Longer-term product direction.
 area: observability
Metrics, history, and capacity insights.
 area: policy
Backup policies, templates, and automation.
 area: restore
Restore and recovery workflows.
 area: security
Permissions, audit, and security hardening.
 bugfix
Bug fixes and correctness work.
 docs
Documentation and operator guidance.
 feature
New functionality.
 refactor
Internal restructuring without direct behavior changes.
 release
Release preparation and publishing.
 security
Security, permissions, and audit work.
No Label area: observability bugfix
Milestone
No items
No Milestone 1.4
Projects
Clear projects
No project
Assignees
Clear assignees
parkel
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: hippogrief/pobsync#97
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?