This message was deleted.
# cloud
s
This message was deleted.
👀 1
d
Hey Mate, I took a look at stunner. It's very cool! This could make it more flexible in terms of pod allocation. Have you been able to load test the solution yet? LiveKit ships with a single-port UDP mode that can also avoid the use of host networking. However, IIRC it tends to run into a network bottleneck around 100Mbps. This was due to multiple goroutines locking before writing to a single socket. Because of that we stopped recommending UDPMux in production deploys.
If you are able to get around it, I'd be very curious to see your solution! from a dev-ex perspective a single port is much easier to work with
m
We ran basic load testing with iperf2 (you can find the related script under example/benchmark). Our goal was to figure out the overhead added by STUNner. The results actually depend on a lot of factors, like environment, packet length, network..etc.
Btw, we do not mux UDP packets, so I do not expect drastic drop at 100Mbps, but we have not gone up till that with bandwidth. Do you have any recommended settings or tools that we could use to benchmark STUNner? Or if you have dedicated test environment, we would be happy to help you to test it out 🙂
On the other hand we have eBPF acceleration on the roadmap that will eventually boost STUNner's performance