[netperf-talk] exact behaviour of generated burst traffic

[Kristijan Dragicevic]

Hello,

Thank you for the quick reply.

> Just to be pedantic, you did configure netperf with burst mode enabled yes?

Yes I did. Burst mode and intervals were enabled.

> -w sets an interval timer, so it is how often a burst should be sent, 
> not an interval between bursts.  the expectation is that netperf 
> finishes the -b burst of sends before that interval timer pops, and sits 
> in a sigsuspend() waiting for the interval timer (this assumes that one 
> isn't using --enable-spin from top of trunk at 
> http://www.netperf.org/svn/netperf2/trunk/)
> 
> If it takes longer than -w to send the -b burst, it can appear that 
> netperf is not bursting at all.  It can also appear that netperf will 
> finish "early" on some systems that do not have (or netperf does not 
> know has) siginfo support to be able to restart selected system calls 
> based on what the signal handler does.

OK, I'm fine with that. 
Let's imagine follwowing concrete example:
Let's say I set parameter "-w 100". And let us assume I choose a right value for parameter -b, so that sending a burst would end after 10ms.
What happens in the 90 ms till the next burst is sent out (I mean are there sent still packets in a different rate or aren't there sent packets at all)?
I ask this question, because when I get the stats of my measurement, I always have about the same amount of packets emitted, no matter I choose long intervals with short bursts or vice versa (of course I chose also values stepwise in between).

_______________________________________________________________
SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192