You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tick benchmark output additionally tracks measured heap allocations during the timed loop (`Allocations`, `Alloc/tick`) so Phase 2 zero-allocation evidence is captured per scenario.
91
+
92
+
`benchmark_evaluation.json` contains:
93
+
94
+
1. selected policy profile
95
+
2. issue summary (errors/warnings)
96
+
3. per-check findings with metric keys and threshold context
97
+
83
98
## Evidence Rules
84
99
85
100
For any published performance claim, attach:
@@ -94,16 +109,16 @@ Claims without linked artifacts are treated as unsupported.
94
109
95
110
## CI Guidance
96
111
97
-
Benchmarks are intentionally not part of default CI pass/fail lanes due to runtime and host variance.
112
+
Benchmarks are intentionally separated from the default CI correctness lanes.
98
113
99
114
Recommended:
100
115
101
-
1. Run benchmark workflow on demand (`workflow_dispatch`) or scheduled lane.
116
+
1. Run benchmark evidence workflow on demand (`workflow_dispatch`) or scheduled lane.
102
117
2. Store artifacts as CI build artifacts.
103
-
3.Compare against previous baseline with explicit tolerance policy.
118
+
3.Apply `ci-hosted` profile on hosted runners and reserve strict gating for dedicated runners.
104
119
105
120
## Next Phase 2 Steps
106
121
107
-
1.Add allocation-count instrumentation in tick path.
108
-
2.Define numeric regression thresholds per workload class.
0 commit comments