Re: [Turnserver-devel] Turnserver Performance Testing...

[Bill C. <bc...@co...>]

Recompiling with switch '--enable-fdsetsize=65535' allows us to get past the 203 simultaneous connection limit.

Once we formulate our findings, we'll post to group.

Regards,
Bill Clark


From: Bill Clark [mailto:bc...@co...]
Sent: Monday, March 19, 2012 9:12 AM
To: tur...@li...
Subject: Re: [Turnserver-devel] Turnserver Performance Testing...

Resending without attachment to avoid message size limits and requiring moderator approval.

From: Bill Clark [mailto:bc...@co...]
Sent: Friday, March 16, 2012 12:20 PM
To: tur...@li...<mailto:tur...@li...>
Subject: [Turnserver-devel] Turnserver Performance Testing...

Hi Sebastien,

We're hitting a wall of 203 simultaneous connections on the turnserver.  Could you please provide any server-level or turnserver configuration that would increase this number?

Attached is a netstat capture (netstat -aptn | grep turn) of all sockets open on turnserver.

We're stressing the Turnserver using a modified test_turn_client and netcat as the peer.  The test_turn_client simply allocates, sets permissions and waits for peer to send data.  Once test_turn_client is notified of connection attempt, it binds and echoes data back to peer.

We've increased the number of 'open file' handles to 65535 for all users in /etc/security/limits.conf and ensured value persists across reboots using 'ulimit -a'

Setup:

1)      Configuration

a.       Range of allowable sockets increased 40K

                                                               i.      max_port = 65535

                                                             ii.      min_port = 25535

b.      turn_tcp = true

c.       using user file for authentication

2)      User file contains 40K users (ex user1, user2, ..., user40000) with appropriate password, domain and authorized syntax.

Execution:

1)      All clients (aka test_turn_client) processes execute on own server (IP 10.11.205.2)

2)      All peers (aka netcast) execute on own server (IP 10.11.205.4)

3)      Turnserver is running on own server (IP 10.11.205.5)

Any help on this matter would be greatly appreciated.

Regards,
Bill Clark