Hello sipp-users,
I'm trying to use SIPp ti simulate about 50000 clinets. I'm using "UDP with
one socket per IP address" mode (-t ui) and I found some problems. First I set
file descriptors limit to 65536, but SIPp still was limited to 1024
connections. So I found that FD_SETSIZE value limits number of sockets. I made
changes in sipp.hpp file:
/*
#ifndef __CYGWIN
#ifndef FD_SETSIZE
#define FD_SETSIZE 65000
#endif
#else
#ifndef FD_SETSIZE
#define FD_SETSIZE 1024
#endif
#endif
*/
#define FD_SETSIZE 65536
So I just commented a section that defines FD_SETSIZE value and set it to
65536. Next I recompiled the sipp and it works with more opened sockets. The
same procedure was used on Fedora 6, Fedora 7 on i386 and Debian 4.0 on amd64.
What is the FD_SETSIZE ??
Next I created csv file:
SEQUENTIAL
SIPpUser00000;sipp00000;172.16.0.1
SIPpUser00001;sipp00001;172.16.0.2
SIPpUser00002;sipp00002;172.16.0.3
...
I've run server (on first PC):
./sipp -sn uas
and client (on second PC):
./sipp -d 30000000 -r 3 -sf uac_multi_ip.xml -t ui -inf uac_multi_ip.csv
-ip_field 2 192.168.0.1
and I found next small problem. SIPp doesn't work when IP is on field number 2.
Precisely: it is problem only with first line. When first line is:
172.16.0.1;sipp00000;172.16.0.1 the rest of the file is read properly. I didn't
try to search sources for an error. I just made the file:
SEQUENTIAL
172.16.0.1;SIPpUser00000;sipp00000
172.16.0.2;SIPpUser00001;sipp00001
172.16.0.3;SIPpUser00002;sipp00002
...
with 60000 different IP's and works ok, until...
I found some problems which was the results of limits of SIPp or Linux? I don't
know. Please help to find the reason:
Presented configuration works ok on the start. Client opens 60000 sockets, 1
for each IP and 90000 connections. When connection 90001 is opened then after
the pause of 30000s BYE message is send on connection 1 and it is closed.
System have now about 90000 opened/paused calls. New calls are created, but old
are closed. The configuration looks stable, but it is stable only untill the
call about 98000 is opened. From this moment retransmissions and unexpected
messages can be seen in server and client [the configuration tested on Pentium
D 2.8GHz, 1GB of RAM, Debian 4.0 on amd64 with kernel 2.6.22].
My question is: I've reached some limits of the system or of the SIPp ????
Next I run similar client on Fedora 6 [the same machines, kernel 2.6.22 on
i386]:
./sipp -d 10000000 -r 5 -sf uac_multi_ip.xml -t ui -inf uac_multi_ip.csv
-ip_field 2 192.168.0.1
so: 10000s of pause, 50000 calls simultaneously from 50000 different IPs (from
the list of 60000). It works stable when such clients was run on 2 PCs. When I
run 3 PCs I found similar situation to previous one. 150000 calls are opened
and paused without problems. On each client: 150000 opened, 100000 closed and
after some more calls (about 10000 to 20000) retransmissions and unexpected
messages start. [configuration with 2 PC as clients was stable long time]
The same question: limits of SIPp or of the system was reached?
How can I tune Linux to such configuration? Which part of sipp source code
should I read?
--
Best regards,
Marcin K. mailto:[EMAIL PROTECTED]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
