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

Benchmark an AuditLog clustered-key flip and revisit per-node KPI sampling cadence #78

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

Tracked follow-ups from arch-review 04, recorded in the ConfigurationDatabase spec:

  • P3: benchmark whether flipping the dbo.AuditLog clustered key from (EventId, OccurredAtUtc) to (OccurredAtUtc, EventId) improves range-scan locality once real volume exists.
  • P4: the per-node KPI sampling cadence, a lower-urgency hardening item. Verify still open, since the spec gives no detail.

(P6, AuditLog reconciliation keyset paging, now looks done: SiteAuditReconciliationActor keeps a (Since, AfterId) cursor and sends AfterId. The spec line is stale.)

Source: docs/requirements/Component-ConfigurationDatabase.md § Data-layer conventions & tracked follow-ups (arch-review 04)

Tracked follow-ups from arch-review 04, recorded in the ConfigurationDatabase spec: - **P3:** benchmark whether flipping the `dbo.AuditLog` clustered key from `(EventId, OccurredAtUtc)` to `(OccurredAtUtc, EventId)` improves range-scan locality once real volume exists. - **P4:** the per-node KPI sampling cadence, a lower-urgency hardening item. Verify still open, since the spec gives no detail. (P6, AuditLog reconciliation keyset paging, now looks done: `SiteAuditReconciliationActor` keeps a `(Since, AfterId)` cursor and sends `AfterId`. The spec line is stale.) Source: `docs/requirements/Component-ConfigurationDatabase.md` § Data-layer conventions & tracked follow-ups (arch-review 04)
dohertj2 added the type:debtpriority:p3migrated labels 2026-11-06 15:24:48 -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:p3 type:debt
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#78
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?