TanStackOSS
    router

router

GitHub
OverviewRunsAnalytics
Loading workspace stats
Loading workspace insights...
Statistics interval
7 days30 days

Latest CI Pipeline Executions

Sort by
  • Succeeded
    7663

    38c9d48a 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.

    by Yagiz Nizipli

    Y

© 2026 - Nx Cloud

Terms of ServicePrivacy PolicyChangelogStatusDocsContact Nx CloudPricingCompany@NxDevTools