If memory serves me right, Bob (Robert) McMahon wrote: > I have no insights without profiling the code paths which I have done > for iperf2 but not for iperf3.
Just for the record, I don't have any particular insights either; the jitter calculation (and the mysterious comment "This is NOT the way to calculate jitter") precedes my involvement with iperf3. The code in iperf2 and iperf3 looks to be similar. Food for thought: Are the comparisons between iperf2 and iperf3 using the same sending rate and packet size? Are the clocks on the client and server behaving sanely? (I don't think synchronized clocks are a requirement, although hopefully they aren't drifting too much relative to each other.) Bruce.
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/
_______________________________________________ Iperf-users mailing list Iperf-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/iperf-users
