dohertj2/ScadaBridge
1
0
Fork 0
Code Issues 42 Pull Requests Actions Packages Projects Releases Wiki Activity

Measure WP-4 residual load criteria (site-event-log retention, audit load vs central, large-template flatten, UI under load) #49

New Issue
Open
opened 2026-11-06 15:24:36 -05:00 by dohertj2 · 0 comments
dohertj2 commented 2026-11-06 15:24:36 -05:00
Owner
Copy Link
Copy Source

Register row 30 (deferred-work register).

The row-25 target-scale harness covered the site-runtime data path only. Sub-criteria [xc-3] site-event-log retention volume, [xc-4] audit-load-vs-central degradation, [xc-5] large-template flattening time and [xc-8] UI responsiveness under load were deliberately not covered.

Revisit trigger (from register): Before declaring phase-8 WP-4 complete, or production go-live at target scale.

Current state: Not measured; phase-8 WP-4 is closed for the site-runtime path only.
Related: docs/plans/2026-08-15-target-scale-load-test-results.md §6.

Source: docs/plans/2026-07-08-deferred-work-register.md row 30

Register row 30 (deferred-work register). The row-25 target-scale harness covered the site-runtime data path only. Sub-criteria `[xc-3]` site-event-log retention volume, `[xc-4]` audit-load-vs-central degradation, `[xc-5]` large-template flattening time and `[xc-8]` UI responsiveness under load were deliberately not covered. **Revisit trigger (from register):** Before declaring phase-8 WP-4 complete, or production go-live at target scale. **Current state:** Not measured; phase-8 WP-4 is closed for the site-runtime path only. Related: `docs/plans/2026-08-15-target-scale-load-test-results.md` §6. Source: `docs/plans/2026-07-08-deferred-work-register.md` row 30
dohertj2 added the type:testpriority:p2migrated labels 2026-11-06 15:24:36 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
blocked
Blocked by dependency or external hold
 cross-repo
Needs coordinated change in another family repo (wire contract etc.)
 migrated
Migrated from a markdown backlog (2026-11 standardization)
 priority:p0
Must-have / blocking
 priority:p1
High priority
 priority:p2
Normal priority
 priority:p3
Low priority / nice to have
 type:bug
Defect in shipped behaviour
 type:debt
Technical debt / hygiene
 type:deploy-gate
Rollout/deploy/migration step not yet done on an environment
 type:docs
Documentation work
 type:feature
Feature implementation
 type:followup
Follow-up deferred from a plan, PR or gate
 type:infra
Infrastructure and scaffolding
 type:review-finding
Unfixed finding from an architecture/code review
 type:test
Test work
No Label migrated priority:p2 type:test
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
dohertj2 (dohertj2)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dohertj2/ScadaBridge#49
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?