Re: [Iperf-users] iperf3: abrupt interval issue

2018-05-08 Thread Bruce A. Mah
If memory serves me right, Bob McMahon wrote: > Hi Nikita, > > I don't know the iperf3 code.  We've been maintaining iperf2 mostly per > WiFi testing needs.  Bruce's original response suggested internal timers > not firing on time. Sorry for the radio silence...yes I think this is still the case

Re: [Iperf-users] iperf3: abrupt interval issue

2018-05-08 Thread Bob McMahon via Iperf-users
Hi Nikita, I don't know the iperf3 code. We've been maintaining iperf2 mostly per WiFi testing needs. Bruce's original response suggested internal timers not firing on time. Bob On Tue, May 8, 2018 at 12:26 AM, Nikita Gupta wrote: > Yes, iperf2 giving correct result. But can you explain why

Re: [Iperf-users] iperf3: abrupt interval issue

2018-05-08 Thread Nikita Gupta
Yes, iperf2 giving correct result. But can you explain why *iperf3* is not showing data of 1 Sec but of 1.24 sec? On Tue, 8 May 2018 at 10:37 AM, Bob McMahon wrote: > iperf2 seems to be indicating 83 socket writes per second with no write > errors. The congestion window is 42K and the RTT is 3.