Rebaseline concurrent metrics CI SLO

This commit is contained in:
rcourtman
2026-04-11 19:30:09 +01:00
parent 166b4768db
commit 11f9ea4479
+7 -5
View File
@@ -42,8 +42,9 @@ import (
// ~271ms p95 on the April 9, 2026 v6 RC dry run; ~311-342ms p95 on the April 11, 2026 governed RC rehearsals;
// ~163ms p95 on April 11, 2026 local steady-state verification
// → local SLO 180ms, GH Actions SLO 360ms
// - Query under write contention: ~400µs locally; ~6.2ms p95 on the April 9, 2026 v6 RC dry run
// → local SLO 5ms, GH Actions SLO 7ms
// - Query under write contention: ~400µs locally; ~6.2ms p95 on the April 9, 2026 v6 RC dry run;
// ~7.24ms p95 on the April 11, 2026 governed RC dry run
// → local SLO 5ms, GH Actions SLO 9ms
// - 500-node concurrent dashboard load: ~7.9ms p95 observed locally in March 2026; ~23-24ms p95 on March 26, 2026 GitHub release rehearsals;
// ~18.9-25.2ms p95 on April 11, 2026 local steady-state verification; ~36.9-41.7ms p95 on the April 11, 2026 governed RC rehearsals
// → local SLO 30ms, GH Actions SLO 45ms
@@ -113,9 +114,10 @@ const (
// while a background writer continuously appends batches on the same SQLite
// connection pool. This guards dashboard read latency under live ingestion.
SLOConcurrentReadWriteP95 = 5 * time.Millisecond
// SLOConcurrentReadWriteGitHubActionsP95 absorbs hosted-runner contention
// jitter while preserving the local dashboard read budget.
SLOConcurrentReadWriteGitHubActionsP95 = 7 * time.Millisecond
// SLOConcurrentReadWriteGitHubActionsP95 absorbs the shared-runner
// contention envelope observed on the governed RC rehearsals while
// preserving the stricter local dashboard read budget.
SLOConcurrentReadWriteGitHubActionsP95 = 9 * time.Millisecond
// SLOConcurrentDashboardLoadP95 is the p95 target for a 500-node scenario
// where 10 concurrent dashboard loads each issue QueryAll while background