I don't want to discourage you but I did spend quite a time looking at this
on Linux a couple of years ago and failed.
I came to the conclusion that the 1024 sockets is a C library restriction
and without recompiling the library there is not much you can do for a
single process. I did try running several processes each with 1000 but at
around 3000 sockets total in use Linux went so slowly that there was no
point. My guess was that the UDP tables were being searched inefficiently in
the kernel. There seems to be a timeout on port use, so you cannot even
close and re-use the sockets or keep using the same socket with different
ports. I was using 250 aliased IP addresses but I think it was the total
IP/port combinations that mattered.
Different Linux versions froze at different points - SuSE 9.0 would get to
3000 but SuSE 9.1 and 9.2 froze at anything over 1300. SuSE 10 was not
available when I did this.
What I did in the end was to write a small program to use the "packet"
interface to send registrations from different IP addresses. We have sourced
200K IP addresses per Linux that way.
Peter Higginson
Newport Networks Ltd,
http://www.newport-networks.com/
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: 07 September 2007 07:39
To: Rick Jones
Cc: [email protected]
Subject: Re: [Sipp-users] Limits of SIPp or limits of system?
Cytowanie Rick Jones <[EMAIL PROTECTED]>:
>> 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:
>
> Hmm, I wouldn't think that FD_SETSIZE would limit the number of
> sockets one can open.
SIPp compiled without my modification says:
Warning: open file limit > FD_SETSIZE; limiting max. # of open files to
FD_SETSIZE = 1024
The warning can be seen on the top of the console, above sipp's
Scenario Screen.
At compilation time I can read:
sipp.hpp:81:1: warning: "FD_SETSIZE" redefined
...
/usr/include/sys/select.h:81:1: warning: this is the location of the
previous definition
>> 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 ??
>
> It is used with select(), which takes in up to three sets of "fd_set"
> for read, write and error where each bit in an fd_set corresponds to
> a specific file (socket) descriptor.
>
> On some platforms, it may not be advisable to mess-around with
> FD_SETSIZE - especially if linking with pre-compiled stuff which used
> a smaller value.
>
> The select() manpage on your system(s) should have more information.
>
> The poll() call does not have the same restriction as select() since
> it doesn't use fd_sets.
thanks for explanation. Does the sipp 2.01 use select()? It uses
poll(). Maybe FD_SETSIZE is obselete?
-------------------------------------------------------------------------
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
---------------------------------------------------------------------------------------------
This e-mail may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this e-mail in error)
please
notify the sender immediately and delete this e-mail. Any unauthorized copying,
disclosure or distribution of the contents in this e-mail is strictly forbidden.
---------------------------------------------------------------------------------------------
Newport Networks Limited is registered in England. Registration number 4067591.
Registered office: 6 St. Andrew Street, London EC4A 3LX
---------------------------------------------------------------------------------------------
-------------------------------------------------------------------------
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
