TanStackOSS
    router
    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 affected --targets=test:eslint,test:unit,test:e2e,test:types,test:build,build --parallel=3
Succeeded
CI Pipeline Execution

nx affected --targets=test:eslint,test:unit,test:e2e,test:types,test:build,build --parallel=3

Click to copy
read access token used
db82fabc7663
6%

Cache hits

28 of 439 tasks used cache.

91%

Distribution saved time

14m 00s instead of 2h 31m 31s.

Atomizer enabled

161 groups of tasks optimized.

© 2026 - Nx Cloud

Terms of ServicePrivacy PolicyChangelogStatusDocsContact Nx CloudPricingCompany@NxDevTools