On 4/20/06, Rob Terrell <[EMAIL PROTECTED]> wrote:
It's really cool! And it'll be even cooler if you can contribute this test tool to us. ;-)
My company has heavy-duty FCS use, both on single servers and using
Flash CDNs like VitalStream and Akamai. We regularly QA our servers
(and our streaming partners) against 500, 1000, 5000 and more RMTP
streams -- we've provisioned events for as many as 40,000 streams.
Once .4 is out, I'm planning on using our testing center to do a
reality check on Red5. If there are any particular scenarios you
would like me to test, let me know.
It's really cool! And it'll be even cooler if you can contribute this test tool to us. ;-)
And John is right -- the single point of failure is a big problem. I
have spent some time working on a poor man's clustering setup for
Red5, although with the API in flux it's not a serious effort right
now. Definitely it will be a major component for me once the API
settles down.
On Apr 19, 2006, at 10:46 AM, John Grden wrote:
> I've often heard numbers like 1000 concurrent connections on a
> single box being a common max point, but I'm sure it can change per
> situation based on what you're doing. The issue is quality of
> experience with that many users obviously. *Can* a server do
> 2500? I doubt it, but I could be totaly wrong. And even if it
> could, it'd bprobably be a miserable experience.
>
> Plus, that's just a single point of failure waiting to happen -
> what about failover/redundancy etc? I've been down this road on a
> major scale and you have to have something planned for load
> balancing the community (hardware AND software IE: loadbalancing
> via the switch that handles your traffic etc), redundancy etc.
_______________________________________________
Red5 mailing list
[email protected]
http://osflash.org/mailman/listinfo/red5_osflash.org
--
Best Regards
Steven Gong
_______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
