`You just want to repeat a single download and measure its time,`
Yes that's exactly it. 

What I don't get is the mapping between the DATA_SET items and the python code. 
I get that for the PLOTS[XXX], you should specify in  'series' the name of a 
DATA_SETS entry but I haven't seen yet how the runner exports its parsed values 
to the DATA_SETS. In this example what decides the kind of data that 'TCP 
iperf' represents among all the values returned by iperf output ?

The last line of iperf output being a recap of the full download is the reason 
for this addition 
https://github.com/tohojo/flent/compare/master...teto:iperf_delay?expand=1#diff-9257f1ed49fd478f9b31d21c2b63a4b6R1325
 (e.g., substract the first timestamp to the last one). When cleaning up the 
code I would move it a bit later since here it is apparently recomputed for 
each new line.

To sum up
1/ how can I get 'TCP iperf' to represent the duration of one download ?
2/ how to run several iperf run in order to plot the cdf of the previous result.

Thanks for the help. I am very impressed by the tool so far (I've been writing 
a tool to compute one-way delays and Multipath TCP statistics so I know it can 
be tricky).



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tohojo/flent/issues/138#issuecomment-395356461
_______________________________________________
Flent-users mailing list
Flent-users@flent.org
http://flent.org/mailman/listinfo/flent-users_flent.org

Reply via email to