how to distinguish busy server from blocked port

[Andrew Sinning]

I did some testing today with 9 work stations, each with 101 connections
to Red5.  The way I set up the test, I launched a single instance on
each machine, then launched a controller instance that could spawn slave
instances on the connected clients.

In this test, all 900 of the spawned connections were instantiated
almost simultaneously.  Each of them first logged in via http to a php
application and then made a NetConnection to Red5.  At about 850
connections things seemed to slow down a bit, but I can't yet determine
if this had to do with bottle-necks in the office or at the server.

Anyway, what I did find was that some of the first attempts to connect
failed, so I configured my connection object to continuously attempt to
reconnect every 2 seconds until successful.

Now I'm working on the contingency of firewalls.  I've set up my router
to block port 1935.  What I've found is that it can take more that 20
seconds to get a NetConnection.Connect.Failed response with a blocked port.

So, how do I distinguish between a situation where the port is block and
where there are just too many clients trying to connect?

Thanks!

_______________________________________________
Red5 mailing list
Red5@...
http://osflash.org/mailman/listinfo/red5_osflash.org

[Walter Tak]

If you connect to a PHP-script first then you'd be able to calculate an
average number of connected or connecting users in your database.

In case it's above a certain threshold you'd be able to tell your
Flash/Flex/Java client that it's too busy at the moment to connect (or to
delay a connection for say 5-10 seconds).

W.

----- Original Message -----
From: "Andrew Sinning" <andrew@...>
To: <red5@...>
Sent: Wednesday, 28 October 2009 23:31
Subject: [Red5] how to distinguish busy server from blocked port

>I did some testing today with 9 work stations, each with 101 connections to
>Red5.  The way I set up the test, I launched a single instance on each
>machine, then launched a controller instance that could spawn slave
>instances on the connected clients.
>
> In this test, all 900 of the spawned connections were instantiated almost
> simultaneously.  Each of them first logged in via http to a php
> application and then made a NetConnection to Red5.  At about 850
> connections things seemed to slow down a bit, but I can't yet determine if
> this had to do with bottle-necks in the office or at the server.
>
> Anyway, what I did find was that some of the first attempts to connect
> failed, so I configured my connection object to continuously attempt to
> reconnect every 2 seconds until successful.
>
> Now I'm working on the contingency of firewalls.  I've set up my router to
> block port 1935.  What I've found is that it can take more that 20 seconds
> to get a NetConnection.Connect.Failed response with a blocked port.
>
> So, how do I distinguish between a situation where the port is block and
> where there are just too many clients trying to connect?
>
> Thanks!
>
> _______________________________________________
> Red5 mailing list
> Red5@...
> http://osflash.org/mailman/listinfo/red5_osflash.org
>

_______________________________________________
Red5 mailing list
Red5@...
http://osflash.org/mailman/listinfo/red5_osflash.org