Diego Soares

Having the same issue. ------------------------------------------------------------ Client connecting to XXXXX.XXXX.XXXX.dev, UDP port 5100 with pid 455958 (1 flows) TOS set to 0x0 (Nagle on) Sending 8500 byte datagrams, IPG target: 10000.00 us (kalman adjust) UDP buffer size: 208 KByte (default) ------------------------------------------------------------ [ 1] local 10.10.11.207%ens5 port 45830 connected with 10.10.11.6 port 5100 (sock=3) on 2023-08-02 14:42:32.533 (UTC) [ ID] Interval Transfer...

Having the same issue. ------------------------------------------------------------ Client connecting to swxtch-receiver-0.swxtch.ibehr.people.aws.dev, UDP port 5100 with pid 455958 (1 flows) TOS set to 0x0 (Nagle on) Sending 8500 byte datagrams, IPG target: 10000.00 us (kalman adjust) UDP buffer size: 208 KByte (default) ------------------------------------------------------------ [ 1] local 10.10.11.207%ens5 port 45830 connected with 10.10.11.6 port 5100 (sock=3) on 2023-08-02 14:42:32.533 (UTC)...

Hi Robert, On the Multicast side there is no ACK from the server, correct? The Client is just pushing the traffic into the network and the server does not matter. If this is not the case, how multiple servers (receivers) are handled? And for -P doesn't help because I the unicast scenario since the server becomes the bottleneck and -P is not supported for MCAST. On Thu, Mar 16, 2023 at 7:41 PM Robert McMahon rjmcmahon@users.sourceforge.net wrote: I don't see the multicast output. Do you have server...

Hi Robert, On the Multicast side there is no ACK from the server, correct? The Client is just pushing the traffic into the network and the server side does not matter. If this is not the case, how multiple servers (receivers) are handled? And for -P doesn't help. In the unicast scenario the server becomes the bottleneck since the server thread becomes CPU constrained. But the unicast piece is not a problem because I can achieve my machine limits with several iperf server threads and cliente. On multicast...

I have a machine that can drive 50Gbps on the NIC and 10Mpps with a 5Gbps limit per flow. When I try to stress test it with multicast I can't. I performed the following tests. For 200, 250, 300, 500 and 700 Bytes Unicast I am CPU bound and understandably cannot drive the 5Gbps per flow, on 1000, 1500 and 8000bytes I can achieve the 5Gbps. However with Multicast I cannot get close to the unicast numbers and CPU does not hit 100%. Can someone explain this behavior? ### ### 200 Bytes ### root@ip-10-0-164-135:~#...

Multicast performance