projectbismark / bismark-active Goto Github PK

bismark-active should only run for a certain amount of time (400 seconds by default) before we kill it to reclaim resources.

Occasionally, D-ITG occasionally sticks around for too long and refuses to die when we kill its parent process. We should figure out why this is and/or the proper way to kill it.

Throughput tests in some routers (particularly in ZA/PK, maybe in IN) do not finish because of suspected buffering in the network which throws off netperf's timing.

http://www.netperf.org/pipermail/netperf-talk/2012-April/000932.html

(Check out follow ups too).

We need to figure out what are good numbers to use for the -s and -S options. What effect, if any, does it have on throughput?

It should use $info from the server, like the rtr script.

The bismark-netperf script needs to read the active conf file to see if it needs to set the -s and -S options.
http://www.netperf.org/svn/netperf2/trunk/doc/netperf.html#index-g_t_002ds_002c-Test_002dspecific-63

Note that it needs to come after all the main options and after a '--'. We already have one such option - the server data port (which we don't really use), so the update needs to take care of that.