[Phase 5] Add performance workers, fixtures, and CI budgets #35

New issue

Closed

opened 2026-07-25 21:57:35 +00:00 by lost-rob0t · 0 comments

lost-rob0t commented

2026-07-25 21:57:35 +00:00

(Migrated from github.com)

Parent: #2
Depends on: #6, #13, #19, #23, #24, #25, #28, #29, #32

Scope

Move heavy parsing, hashing, large imports, and eligible layout work off the main thread.
Add deterministic performance fixtures for graph, table, map, timeline, action streaming, import, and offline restore.
Measure startup, interaction latency, snapshot projection, batch application, memory growth, and worker cleanup.
Define CI budgets and regression thresholds.
Add graceful degradation paths before renderer or memory failure.

Acceptance criteria

Performance tests produce machine-readable reports.
CI fails material regressions against approved budgets.
Long tasks do not block critical interaction beyond the defined threshold.
Repeated workspace and worker lifecycle tests do not leak unbounded resources.
Large projections degrade to bounded summaries, clustering, or tables instead of freezing.

Parent: #2 Depends on: #6, #13, #19, #23, #24, #25, #28, #29, #32 ## Scope - Move heavy parsing, hashing, large imports, and eligible layout work off the main thread. - Add deterministic performance fixtures for graph, table, map, timeline, action streaming, import, and offline restore. - Measure startup, interaction latency, snapshot projection, batch application, memory growth, and worker cleanup. - Define CI budgets and regression thresholds. - Add graceful degradation paths before renderer or memory failure. ## Acceptance criteria - Performance tests produce machine-readable reports. - CI fails material regressions against approved budgets. - Long tasks do not block critical interaction beyond the defined threshold. - Repeated workspace and worker lifecycle tests do not leak unbounded resources. - Large projections degrade to bounded summaries, clustering, or tables instead of freezing.