On 22.06.21 14:03, Koen Vandeputte wrote: > > Thanks for confirming that. > > What would really help is a small table showing this: > > Real physical distance? (in m) > ack_to reported while stressing the link: > > 20MHz: xx > 10 MHz: yy > 5 MHz: zz > > I'll try to simulate the issue somewhere in the next days. > > > Please do note that ongoing effort is currently going on to improve > dynack on lower distances. > > It was observed and reported by me to Lorenzo that ack_to was way > higher than fixed settings when > real distance is <6km > > Some testing patches were cooked and tested in the field last month > covering long and short distances (1km up to 24km) > and these are matching fixed distance ack_to very close now. (speeds > using dynack were also higher than fixed settings) > It's not finalized yet. > > Also do note that dynack only shows (any) benefit when having links >3km > Below that, timing jitter and processing time seems to have more > influence on ack_to than actual distance. > > Regards, > > Koen > Here the testresults real physical distance: 1m BW: 20mhz ackto: 50 iperf3 [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 86.4 MBytes 72.4 Mbits/sec 0 sender [ 5] 0.00-10.01 sec 86.0 MBytes 72.0 Mbits/sec receiver BW: 5mhz ackto: 50 iperf3 [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.01 sec 45.2 KBytes 37.0 Kbits/sec 14 sender [ 5] 0.00-10.07 sec 5.66 KBytes 4.60 Kbits/sec receiver BW: 10mhz ackto: 50 iperf3 [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 127 KBytes 104 Kbits/sec 30 sender [ 5] 0.00-14.10 sec 107 KBytes 62.4 Kbits/sec receiver Also longer iperf3 tests didnt change anything on this behaviour. After this test we were actually able to get the ack_to doing something for 5mhz (ack_to 641 - ~12MBit iperf3) and 10mhz (ack_to 258 - ~14MBit iperf3) by doing some random wifi-restarts (using openwrt 'wifi' command) and reboots, but this is not really reproducible. We got the gutfeeling that there might be some issue reseting of the dynack part when changing the bandwidths. This might explain, why for the test above the ack_to doesnt change at all from the 50 of the 20Mhz BW. Or is this normal behaviour that the ack_to doesnt change after a bandwidth change? Another observation: Is it normal that 'iw dev' doesnt show 5 & 10 MHz, but always 20 MHz? (We verified that we actually get 5/10MHz Channels by checking visibility of the AP with other clients). To rule out a hardware problem: We used the same hardware successfully on a 8km/20MHz link with dynack. Regards, Julian
