[Red5] Server choices for Red5: A Double Dual Core CPU or afaster-clocked single core Pentium 4?

Ed Wise flash at christianweb.com
Sun Nov 25 08:39:20 PST 2007


Thank you Dominick; I didn't know there was such a thing.  Currently we think it's best to host everything on our own server, so it can easily interface with our database and everything on the server side.  But we'll keep this in mind.  Thanks for telling me.

Ed
  ----- Original Message ----- 
  From: Dominick Accattato 
  To: red5 at osflash.org 
  Sent: Sunday, November 25, 2007 2:57 AM
  Subject: Re: [Red5] Server choices for Red5: A Double Dual Core CPU or afaster-clocked single core Pentium 4?


  Ed:

  If your looking for an infrastructure that will allow for failover support, redundancy and expansion please feel free to check out www.red5server.com.  If you have any questions please contact me and we can discuss options.  Thanks. 


  On Nov 24, 2007 1:52 PM, Ed Wise <flash at christianweb.com> wrote:

    Which server would be better suited for running Red5:

    Pentium 4, 3.0 GHz
    32-bit OS: Windows Server 2003 (Standard Edition) 

    or

    2x Dual Core AMD Opteron 2216 (2.4 GHz) 
    (the web hosting company says "2 x 2 x 2.4 GHz")
    64-bit OS: Windows Server 2003 (Standard Edition) 64-bit Edition

    I guess this question kinda depends on whether or not Red5 takes advantage of dual core CPUs, which I suppose depends on if Java does, which I think it does.  In that case, the second choice would probably be better -- that is, if Red5/Java can distribute tasks/threads/whatever among the CPUs.  Can someone confirm that I'm right on this?  

    Also is a 64-bit server (hardware and OS) okay for Red5?  And will that also yield better performance?

    I want to consider just the CPUs, but if you really want to know the RAM, the Pentium 4 is 2GB and the double dual core is 8GB (and I suppose that is a big consideration).

    Ed

    P.S. Intended application is a one-to-many video/voice chat app (with text chat also) that should be able to accommodate up to 200 concurrent users spread out among about 10 rooms.  So, it should be able to handle up to 10 incoming concurrent video (and audio) streams (one from each room), each being streamed back out to all the users in the room it originated from (up to say, 50 users in a room).  (But total users in all 10 rooms would total 200 or less).



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





  -- 
  Dominick Accattato, CTO
  Infrared5 Inc.
  www.infrared5.com 


------------------------------------------------------------------------------


  _______________________________________________
  Red5 mailing list
  Red5 at osflash.org
  http://osflash.org/mailman/listinfo/red5_osflash.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://osflash.org/pipermail/red5_osflash.org/attachments/20071125/becb3620/attachment.html 


More information about the Red5 mailing list