QRun-IO/qbit-alerts
3
0 Fork 0
Code Issues 2 Pull Requests 5 Actions Packages Projects Releases 18 Wiki Activity

perf: scheduled jobs and the signal queue issue far fewer statements #75

Merged
james.maes merged 2 commits from perf/scheduled-job-statements into develop 2026-11-10 22:11:43 +00:00
Conversation 0 Commits 2 Files Changed 29
+2336 -156
2 Commits
Author SHA1 Message Date
james.maesandClaude Fable 5.2 f0c6c77354 docs: upgrade notes for the statement reduction
maven / build (push) Successful in 2m52s
Details
build / maven (push) Successful in 2m52s
Details 
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
 2026-11-10 15:39:57 -06:00
james.maesandClaude Fable 5.2 e26116e075 perf: scheduled jobs and the signal queue issue far fewer statements
maven / build (push) Successful in 2m25s
Details
build / maven (push) Successful in 2m25s
Details 
The alerts jobs run every 15 to 60 seconds, so their statement count is a
host's constant database load. StatementBudgetTest counts the statements of
each job and polled request and fails when they grow with the rows held.
Measured with the same scenarios before (0.1.0-RC.18) and after:

- alertsEscalateAndRemind, 50 open alerts, nothing due: 452 -> 1. It reads
  only alerts a reminder or an escalation policy can apply to, decides from
  the row and the reference tables, and takes the per-alert transaction only
  when something may be due. An alert with nothing due is not written, so
  timedNotificationCheckedAt is the last attempt, not the last tick.
- alertsEvaluateMonitors: 20 monitors not due 5 -> 2 (due monitors selected
  in SQL, upkeep in one read); 20 due clean monitors 185 -> 84; a per-record
  monitor refreshing 10 alerts 205 -> 120.
- alertsDeliverNotifications: idle 9 -> 7; 60 pending deliveries in 2 groups
  317 -> 22; the purge runs hourly instead of every tick.
- Queued producer signals are recorded in batches: 200 resolves for alerts
  that are not open plus 50 heartbeats 369 -> about 33. A repeated raise of
  an open alert 17 -> 10.

AlertsReferenceCache holds alert types, groups, escalation policies, steps
and enabled mutes in a core Memoization registered with core ClusterCaches.
A record-change listener clears a table on every node (ClusterBus) when it
is written through QQQ; entries expire after 60 seconds; a table over 2,000
rows is not held. A type's openCount and lastRaisedAt are engine counters:
they do not clear the cache and are no longer record-audited.

Changeset 55 adds ix_alerts_alert_flapping for the upkeep read.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
 2026-11-10 15:39:02 -06:00