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

[Vinod Panicker]

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

>  > In summary, tsung is configured to use 4 clients, all of which are
>  > hostnames mapping to individual IP's of the client machine. The client
>  > machine has 2 NIC's, each of which is assigned 2 IP addresses.  Tsung
>  > ends up using just one of those IP addresses to generate load and
>  > eventually runs out of available client ports after 65k connections.
>
>  Weird. Can you show your xml config (clients part) and output of ifconfig
>  on your clients ?

   <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>

ifconfig on eowyn -

eth0      Link encap:Ethernet  HWaddr 00:15:17:50:66:D1
          inet addr:192.168.66.74  Bcast:192.168.66.255  Mask:255.255.255.0
          inet6 addr: fe80::215:17ff:fe50:66d1/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:69749 errors:0 dropped:0 overruns:0 frame:0
          TX packets:57 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:7215459 (6.8 MiB)  TX bytes:3996 (3.9 KiB)
          Base address:0x2000 Memory:e8180000-e81a0000

eth0:1    Link encap:Ethernet  HWaddr 00:15:17:50:66:D1
          inet addr:192.168.66.75  Bcast:0.0.0.0  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Base address:0x2000 Memory:e8180000-e81a0000

eth1      Link encap:Ethernet  HWaddr 00:15:17:50:66:D2
          inet addr:192.168.66.76  Bcast:192.168.66.255  Mask:255.255.255.0
          inet6 addr: fe80::215:17ff:fe50:66d2/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:14697471 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16805639 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2238093874 (2.0 GiB)  TX bytes:2269160395 (2.1 GiB)
          Base address:0x1100 Memory:e8020000-e8040000

eth1:1    Link encap:Ethernet  HWaddr 00:15:17:50:66:D2
          inet addr:192.168.66.77  Bcast:0.0.0.0  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Base address:0x1100 Memory:e8020000-e8040000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:5181 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5181 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:303616 (296.5 KiB)  TX bytes:303616 (296.5 KiB)

Thanks for the reply.
Regards.
Vinod.