Pluggable congestion control

[isaachess]

Right now this package uses an implementation of TCP-cubic for congestion control. It would be nice if the code easily allowed different congestion control algos to be used.

For example, if I wanted to use a LEDBAT congestion control algorithm, if I were to write my own implementation of the SendAlgorithm interface I still don't see a way to plug that in when I create a new session.

So it would be nice, even if we do not yet have officially supported congestion control other than cubic, to have an easy way to write one and use it instead of cubic.

[isaachess]

The reason I'm asking this is specifically for LEDBAT. We need the ability to use cubic cc for some connections, but LEDBAT for others. So if there is already a simple way to do that with this QUIC implementation I'd be interested in that.

[lucas-clemente]

I think the options are either having an enum for the congestion controllers we support (which wouldn't allow it to be different on a connection basis), or adding a func (connectionID int64) SendAlgorithm to the quic.Config.

We also have plans to support BBR (#341), and for that we'll need to change the SendAlgorithm interface – so there will be breaking changes at some point.

If you plan to do benchmarks please be aware that some performance-relevant parts of our implementation are still lacking (e.g. loss recovery).

[isaachess]

I think having different congestion-control per-connection is not really what I need (sorry for being imprecise), but rather being able to change it per-process.

And yes, I agree having an enum for officially supported congestion controllers is a fantastic idea. I just think even now, before you get around to officially supporting a bunch of different congestion controllers, the code could be rewritten a little to make it simpler to write your own congestion controller and plug it into the session.

[lucas-clemente]

SGTM :) If forking is an acceptable solution for now, the relevant line you need to change is https://github.com/lucas-clemente/quic-go/blob/master/ackhandler/sent_packet_handler.go#L69.

Feel free to send PRs to simplify things wherever you think it makes sense – what specifically did you have in mind?

[qiulaidongfeng]

Hi All:

For those who are concerned about this issue
https://github.com/qiulaidongfeng/quic-go
The experiment to solve this issue by exporting SendAlgorithmWithDebugInfos and adding the Congestion field in Config is now available. Those interested are welcome to experiment with different congestion control algorithms, and feedback is highly appreciated.

I implemented a version of bbrv1 myself with only about 200 lines of code, which can serve as an example for adding new algorithms.bbr v1

[marten-seemann]

@qiulaidongfeng Please stop commenting on old issues advertising your BBR implementation.