I’m looking to get the best performance out of a RTP over Quic stream using quinnquicsink/quinnquicsrc. What are the best parameters to adjust to improve performance?
Have not done really investigation on performance side of things. If quinn-rs exposes any parameters/API that can be helpful with that, we can look into exposing them as properties or such as appropriate on the element.
Also, there are examples available in the repository, if you have not already seen those.
Thanks for the response!
In the examples you seem to set the parameters to either the minimum or the maximum. Was there any specific reasoning for this? If I were to investigate the performance, do you think these parameters are the ones I should focus on?
sink.set_property("drop-buffer-for-datagram", true);
sink.set_property("initial-mtu", 1200u32);
sink.set_property("min-mtu", 1200u32);
sink.set_property("upper-bound-mtu", 65527u32);
sink.set_property("max-udp-payload-size", 65527u32);
sink.set_property("use-datagram", false);
I will look into quinn-rs and see if there is anything else that might be useful.
min-mtu is just the maximum UDP payload size guaranteed to be supported by the network, which is also the default. The upper bound is more of a depends.
With RTP over QUIC, we want the RTP payloader to not perform any segmenting of frames, letting it payload a large RTP packet. Segmenting and re-assembling should be taken care of by QUIC. For datagrams primarily, depending upon the settings, we might not be able to send this large packet. The settings were done to allow that during testing.
You might want to experiment depending on streams or datagram and your network.