-
Notifications
You must be signed in to change notification settings - Fork 64
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
GCC: RateController does not use the internal state #271
Comments
sterlingdeng
pushed a commit
to sterlingdeng/interceptor
that referenced
this issue
Dec 20, 2024
This fixes an issue described in pion#271. The original implementation did not transition rate controller states properly.
sterlingdeng
pushed a commit
to sterlingdeng/interceptor
that referenced
this issue
Dec 21, 2024
This fixes an issue described in pion#271. The original implementation did not transition rate controller states properly.
sterlingdeng
pushed a commit
to sterlingdeng/interceptor
that referenced
this issue
Dec 21, 2024
This fixes an issue described in pion#271. The original implementation did not transition rate controller states properly.
sterlingdeng
pushed a commit
to sterlingdeng/interceptor
that referenced
this issue
Dec 21, 2024
This fixes an issue described in pion#271. The original implementation did not transition rate controller states properly.
I noticed this same issue when doing a port of GCC for QUIC and was looking at different implementations. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Your environment.
What did you do?
RateController on the delay stats update doesn't use the internals state. Should we make a transition from the internal state, not from the current one (which is always increase actually)? Snippet from the rate_controller.go :
What did you expect?
Using the internal state (smth like this):
What happened?
The text was updated successfully, but these errors were encountered: