[Tsung] Generating over 32k clients from a single machine

[Vinod Panicker]

On Wed, Feb 27, 2008 at 6:03 PM, Vinod Panicker <vinod.p at gmail.com> wrote:
> On Wed, Feb 27, 2008 at 5:52 PM, Nicolas Niclausse <nicolas at niclux.org> wrote:
>  > Vinod Panicker ecrivait le 27.02.2008 12:59:
>  >
>  > > On Wed, Feb 27, 2008 at 4:56 PM, Nicolas Niclausse <nicolas at niclux.org> wrote:
>  >  >> Vinod Panicker ecrivait le 27.02.2008 12:13:
>  >  >>
>  >  >>> OK so the multiple IP thing wasn't really working out (though I
>  >  >>  > thought so).  A netstat dump showed that tsung was using just a single
>  >  >>  > IP address to generate the load.
>  >  >>  > According to the configuration though, it was *not* supposed to use
>  >  >>  > that IP address.  Seems like I've stumbled across a bug.  I'm using
>  >  >>  > tsung revision 722 from svn (since the latest available one was giving
>  >  >>  > errors that were reported already by someone on the list)
>  >  >>
>  >  >>  what kind of errors ?
>  >  >
>  >  > The one about "stop in state think" as mentioned in this thread -
>  >  > http://lists.process-one.net/pipermail/tsung-users/2008-February/000735.html
>  >
>  >  the method tag is not defined in your config file (<http ... method='get'
>  >  .../> ). Anyway, the default value (GET) is now set in the svn
>
>
> I didn't have any http request in the tsung.xml in my case. Anyways,
>  will try it out once again and report the findings.
>
>
> >  >    <clients>
>  >  >     <client host="eowyn" weight="1" maxusers="50000"/>
>  >  >     <client host="eowyn1" weight="1" maxusers="50000"/>
>  >  >     <client host="eowyn2" weight="1" maxusers="50000"/>
>  >  >     <client host="eowyn3" weight="1" maxusers="50000"/>
>  >  >   </clients>
>  >
>  >  This is not how it is supposed to work. For every IP you have on a client,
>  >  you must add an <ip> tag:
>  >       <client host="eowyn" weight="1" maxusers="100000">
>  >           <ip value="192.168.66.74"></ip>
>  >           <ip value="192.168.66.75"></ip>
>  >           <ip value="192.168.66.76"></ip>
>  >           <ip value="192.168.66.77"></ip>
>  >       </client>
>  >
>  >  (btw, having two physical interfaces in the same network is weird.)
>
>
>
> Thanks, will try this out.  The interfaces are configured such just so
>  we can get around the 65k limit per ip for the test.

This configuration allows tsung to use a single beam.smp process and
utilize all 4 ip addresses, but there's another weird problem
occurring now. Tsung is not reusing the port numbers between the ip
address.  Eg - port number 4444 will be used only once instead of 4
times. Eventually, it runs out of available ports at around 65k.
Verified this using the netstat output.

Regards,
Vinod.