ta
TanStack
GitHub
router
Workspace
GitHub
CI Pipeline Executions
Current execution
Succeeded
perf/frame-decoder-index-pointer
Configuration
Self-Healing CI
Project Graph
Resource Usage
Analysis
Conformance
Runs
Current run
Succeeded
Tasks
Resource Usage
Insights
Compare tasks
Analytics
Sign in
Toggle sidebar
perf(start-client-core): O(1) buffer drain in client frame decoder The frame decoder dropped consumed chunks from its buffer with bufferList.shift(), which is O(n). When a single large frame (e.g. a big RawStream payload) is assembled from many small network reads, the extract loop calls shift() once per chunk, making reassembly O(n^2). Track the first un-consumed chunk with a head pointer and advance it in O(1) instead of shifting. Consumed slots are released for GC, and the buffer is compacted when fully drained (O(1) reset) or once the consumed prefix grows past a small threshold (amortized O(1) per chunk). A micro-benchmark draining 1000 small chunks is ~11x faster.
nx run-many --target=build --exclude=examples/** --exclude=e2e/**
⌘K
Succeeded
nx run-many --target=build --exclude=examples/** --exclude=e2e/**
Click to copy
Linux
4 CPU cores
db82fabc
7663
Get faster results
Learn how to enable distribution.
Atomizer enabled
43 groups of tasks optimized.