Kari Niemelä

--txstart-time with -R

-- burst-size with -R results burst size of 128kB

Thanx, -l36 worked with --trip-times, but it does not prompt warning if too short, e.g -l4.

--trip-times XXX:~$ iperf -v iperf version 2.2.n (26 Oct 2024) pthreads XXX:~$ iperf -u -c 192.168.1.101 -t1 -l36 -b 20m -e --trip-times ERROR: payload (-l) size of 36 too small for --trip-times, must be 92 or greater XXX:~$ iperf -u -c 192.168.1.101 -t1 -l36 -b 20m -e ------------------------------------------------------------ Client connecting to 192.168.1.101, UDP port 5001 with pid 47764 (1/0 flows/load) TOS defaults to 0x0 (dscp=0,ecn=0) (Nagle on) Sending 36 byte datagrams, IPG target: 0.00...

--trip-times *XXX:~$ iperf -v iperf version 2.2.n (26 Oct 2024) pthreads XXX:~$ iperf -u -c 192.168.1.101 -t1 -l36 -b 20m -e --trip-times ERROR: payload (-l) size of 36 too small for --trip-times, must be 92 or greater XXX:~$ iperf -u -c 192.168.1.101 -t1 -l36 -b 20m -e ------------------------------------------------------------ Client connecting to 192.168.1.101, UDP port 5001 with pid 47764 (1/0 flows/load) TOS defaults to 0x0 (dscp=0,ecn=0) (Nagle on) Sending 36 byte datagrams, IPG target: 0.00...

Support for 64B packets (-l 36) with UDP

Slow start from 0Mbps is not applicable for video flow, but rather from bit rate given as isochronous (nominal) bit rate or from minimum bit rate providing yet viable quality. So minimum bit rate may need to be added as parameter e.g. for --isochronous with second option.

Slow start from 0Mbps is not applicable for video flow, but rather from bit rate given as isochronous (nominal) bit rate or from minimum bit rate providing yet viable quality. So minimum bit rate may need to be added as parameter e.g. for --isochronous with second option.