Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(codec) Debounce the call that calc codec intersection set. #2622

Merged
merged 2 commits into from
Jan 27, 2025

Conversation

jallamsetty1
Copy link
Member

Calculate codec intersection set only once per second even when there is a burst of joins/leaves. Also, check for current codec before chaining a codec change operation when codec selection API is used.

Calculate codec intersection set only once per second even when there is a burst of joins/leaves. Also, check for current codec before chaining a codec change operation when codec selection API is used.
Copy link
Member

@saghul saghul left a comment

Choose a reason for hiding this comment

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

Left some comments, PTAL!

modules/RTC/TPCUtils.js Show resolved Hide resolved
@@ -159,6 +161,26 @@ export class QualityController {
(tpc: TraceablePeerConnection, stats: Map<number, IOutboundRtpStats>) => this._processOutboundRtpStats(tpc, stats));
}

/**
* Creates a debounced function that delays the execution of the provided function until after the specified delay
Copy link
Member

Choose a reason for hiding this comment

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

Isn't this basically lodash's throtlle? https://lodash.com/docs/4.17.15#throttle

Copy link
Member

Choose a reason for hiding this comment

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

Wait, I see you imported it but then didn't use it?

Copy link
Member Author

Choose a reason for hiding this comment

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

Oh yes, I was testing with lodash throttle with both the leading and trailing options set to true and ran into this limitation - If leading and trailing options are true, func is invoked on the trailing edge of the timeout only if the throttled function is invoked more than once during the wait timeout.
I can go back and test lodash throttle with only the trailing option set to true and I believe the end result will be the same. Will update this.

Copy link
Member

Choose a reason for hiding this comment

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

👍

Copy link
Member Author

@jallamsetty1 jallamsetty1 Jan 27, 2025

Choose a reason for hiding this comment

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

Actually when I pass { leading: false, trailing: true } to lodash's throttle, my testcases fail, its missing some of the calls when we expect them.

Copy link
Member

Choose a reason for hiding this comment

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

We are waiting for 1000 and advancing by 1000 I bet there are shenanigans there? Perhaps we should test by waiting a bit longer?

Copy link
Member Author

Choose a reason for hiding this comment

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

I got the same results when I had the timer set to 1200 ms. I remember this being the case when we initially discussed about debouncing this call and my unit tests for testing lodash's throttle had also failed.

Copy link
Member

Choose a reason for hiding this comment

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

Ok let's have it this way 👍

modules/qualitycontrol/QualityController.ts Show resolved Hide resolved
modules/qualitycontrol/CodecSelection.spec.js Show resolved Hide resolved
@jallamsetty1 jallamsetty1 merged commit dfc23df into master Jan 27, 2025
2 checks passed
@jallamsetty1 jallamsetty1 deleted the fix-set-codecs branch January 27, 2025 18:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants