ta
TanStack
GitHub
router
Workspace
GitHub
CI Pipeline Executions
Current execution
Succeeded
memory-bench-settle-barrier
Runs and Agents
Configuration
Self-Healing CI
Project Graph
Circular Dependencies
Enterprise
Resource Usage
Analysis
Conformance
Enterprise
Runs
Current run
Succeeded
Tasks
Resource Usage
Insights
Compare tasks
Analytics
Sign in
Toggle sidebar
bench(memory): restrict floor verification to peak-shape scenarios The floor-verified barrier fixed its target - the serialization family went to <=0.45% across three CI runs, attractor gone - but destabilized churn/abort scenarios (request-churn solid 420KB vs 3.4MB): their inter- iteration floor legitimately drifts, so the verification capped out chronically and the ~48 extra collections per iteration eventually hit a compaction that double-copies the live set. Split by scenario shape: serialization-payload, peak-large-page and streaming-peak keep the verified barrier (flat floor, proven fix); churn and abort scenarios go back to the plain fixed-count barrier that held them at <=1.7% in the two previous CI rounds. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
nx affected --targets=test:eslint,test:unit,test:e2e,test:types,test:build,build --parallel=3
⌘K
Succeeded
nx affected --targets=test:eslint,test:unit,test:e2e,test:types,test:build,build --parallel=3
Click to copy
253520dd
7739
98%
Cache hits
45 of 46 tasks used cache.
Atomizer enabled
24 groups of tasks optimized.