Skip to content

Replace NodeStats forward_scheduling_delay with processing per subscriber - #1895

Merged
boks1971 merged 2 commits into
mainfrom
raja/forward-processing-per-subscriber
Oct 26, 2026
Merged

boks1971 merged 2 commits into
mainfrom
raja/forward-processing-per-subscriber

Conversation

@boks1971

Copy link
Copy Markdown
Contributor

Replaces NodeStats.forward_scheduling_delay (field 57, added in #1891) with forward_processing_per_subscriber: the mean forwarding work per subscriber written, in ns. Scheduling delay did not rise under CPU load in a load test, so nothing uses it. The field keeps its number and type. A livekit/livekit PR fills it.

🤖 Generated with Claude Code

…r_subscriber

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@boks1971 boks1971 self-assigned this Oct 26, 2026
@changeset-bot

changeset-bot Bot commented Oct 26, 2026 •

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 3150a77

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages
Name Type
github.com/livekit/protocol Patch
@livekit/protocol Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

// p90 time from arrival to dequeue, in ns, for packets that found their forwarder idle
uint32 forward_scheduling_delay = 57;
// mean forwarding work per subscriber, in ns: (end of fan-out - dequeue) / subscribers written
uint32 forward_processing_per_subscriber = 57;

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a recent change and it is not there any where except staging. So, replacing.

@boks1971
boks1971 merged commit 211df6b into main Oct 26, 2026
8 checks passed
@boks1971
boks1971 deleted the raja/forward-processing-per-subscriber branch October 26, 2026 18:44
@github-actions github-actions Bot mentioned this pull request Oct 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants