Re: [reSIProcate-users] any TCP performance bench mark for latest resiprocate stack
Scott,
I set FD_SETSIZE to very high number 98304, and doubt if select() can handle this huge fds.
Frank
On Mon, Nov 16, 2009 at 9:48 AM, Scott Godin
<slgodin@xxxxxxxxx> wrote:
Unfortunately resip still uses select. There are a few (1-3) FD's
used by the stack for utility purposes (ie. dns sockets, select
interruptor, etc.), there is also a FD per transport and a FD is
required for each TCP/TLS connection. The number of FD's that you
can add to a select set (the number TCP/TLS supported) is OS/compiler
dependent. For example under Windows FD_SETSIZE defaults to 64 - this
means that somewhere near 60 TCP or TLS connections are supported.
For linux the limit is usually higher (ie. 1024). The FD_SETSIZE
definition can be controlled to increase the number of TCP/TLS sockets
supported.
Scott
On Mon, Nov 16, 2009 at 10:23 AM, fuliang yuan <
fuliangyuan@xxxxxxxxx> wrote:
> Hi,
>
> The old resiprocate stack used select() instead of poll() or epoll()
> Function poll or epoll can scale well for a large number of fds, but
> select() has limitation in this respect.
>
> What are the maximum concurrent TCP (TLS) connections for one latest sip
> stack?
>
> Thanks,
>
> Frank
>
> resiprocate-users mailing list
> resiprocate-users@xxxxxxxxxxxxxxx
> List Archive: http://list.resiprocate.org/archive/resiprocate-users/
>