ci probe: tier1-spike2 isolation (do not merge) - #2924
Conversation
|
size-limit report 📦
|
Coverage Report for CI Build 29784307146Warning No base build found for commit Coverage: 75.328%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsRequires a base build to compare against. How to fix this → Coverage Stats
💛 - Coveralls |
Merging this PR will regress 1 benchmark
|
| Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|
| ❌ | merge |
266.5 µs | 369.6 µs | -27.9% |
| ⚡ | merge |
165.2 µs | 73.3 µs | ×2.3 |
| ⚡ | reconcile: deep tree, 10 of ~12k paths subscribed |
6.4 ms | 3.3 ms | +92.01% |
Tip
Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.
Comparing probe/tier1-spike2 (d97746c) with next (2bf022e)
|
Probe result: reproduces #2923's merge deltas exactly in isolation — merge-mixed −27.9% AND merge-static ×2.3, the coupled pair. Confirms both come solely from the affects-channel read()-shape change. Since merge-mixed is a plain-JS getter/value descriptor bench (getter body |
Attribution probe for #2923's CodSpeed result (merge-mixed −28%, alongside merge-static ×2.2 / reconcile +92% / update1to1 +5.5% improvements). Isolates one spike. Closes after CodSpeed reports.