I think you'll get better answers if you post onto the Red5 list.

I'm really not qualified to answer, but just to give you something to
think about, if you have 500Kbps video, that would mean you'd max out
the connection if a dorm with 200 students is connected with only
100Mbit (and they probably won't switch off their P2P clients for
you). So you'll need to learn about the existing infrastructure, too.
Then again, you'll end up needing several servers anyway, so you might
as well spread some of them out over campus.

But again, I'm not qualified and you're much more likely to find
somebody on the Red5 list who has practical experience with that kind
of setup and can tell you something about potential pitfalls like HDD
access times and so on.

Mark



On Sat, May 10, 2008 at 11:20 AM, Subscribe Mail
<[EMAIL PROTECTED]> wrote:
> Hi,
> I am new to architecting streaming solutions.
>
> Heres a requirement for one of my customers:
>
> 1. 5000 registered students. And potentially all of them could be watching
> the videos (lessons) on the system concurrently. (this can happen at Peak
> time - just before their exams)
>
> 2. I would like to have acceptable jitter at say the dimensions (length and
> breadth) and the resolution quality of say YouTube.  I would assume audio
> becomes more critical than the video as this is a lecture for the students.
>
> I was thinking that Red5 would be a good choice to steam these videos to
> these students.
>
> Can someone suggest the kind of hardware that would be needed to support
> this scale of streaming. Also, can someone help me with some indicative
> numbers of what such a hardware setup costs? I am looking for very broad
> level indicative numbers.
>
> Thanks.
> Regards,
> Ash
>
> _______________________________________________
>  osflash mailing list
>  [email protected]
>  http://osflash.org/mailman/listinfo/osflash_osflash.org
>
>

_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org

Reply via email to