Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows Server 2003Windows 2000Windows NTSmall Business ServerVirtual ServerExchange ServerIISHost Integration ServerISA ServerSMSWSUSMOMWindows Media ServerSecurityCertification
Related Topics
SQL ServerMS WindowsMS OfficePC HardwareMore Topics ...

Windows Server Forum / Windows Media Server / February 2004

Tip: Looking for answers? Try searching our database.

Peformance and Hardware Specs - Please share your experience

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Tom - 24 Feb 2004 00:29 GMT
Assuming 300KBIT streams, ON-Demand, "infinite
bandwidth", 2GB RAM

What is the max (rough neighborhood, very rough is OK)
concurrent connections with:

DUAL XEON 2.8 GHZ ?
w/ 7200RPM IDE Drive

ONE P4 3.0GHZ 800MHZ FSB ?
w/ 7200RPM IDE Drive

How do things change if drive is 7200RPM SATA IDE?

If you have been running under different hardware and
load, that's ok. In general, if you have had Windows
Media Server 2003 in production, please share your
numbers.  I'd like to hear your server specs and the
makeup of your streaming (i.e. how many max concurrent
streams?  what bitrate?  on-demand from hard disk?  How
many different files being served?)  Anything you can
share is appreciated.

Anyone out there who used Windows 2000 sever and then
migrated to Windows Server 2003?  What was your
percentage performance gain by moving to Windows 2003
Windows Media Server?  I have seen a few Windows 2000
benchmarks for streaming, but don't know how the figures
would translate into a much more optimized WMS 2003
scenario.

Thanks!
Tim 'StreamingMeeMee' Carter [MVP/Digital Media] - 24 Feb 2004 15:26 GMT
CPU doesn't matter much, you won't gain anything with a SMP box.  Spend
your money on F A S T disks or perhaps multiple load balanced machines
instead.

RAM isn't a big deal either until you get to high concurrent stream
counts -- WMS keeps a re-transmit buffer per connection; more
connections = more buffers.  2GB is plenty for multiple thousand.

Basically, it boils down to bandwidth.  Assuming you have GigE, and
300kbps streams the rough math works out like this:

1000 / .3 = 3333 concurrent streams.

This assumes a PERFECT network (impossible) and no stream delivery
overhead (also impossible).  I would go with something a bit more realistic:

(1000 *.7) / (.3 * 1.2) = 1667 concurrent streams.

This allows for 70% network utilization and 20% overhead in the stream
delivery (retransmissions, protocol overhead, etc).

So then, your disk I/O would need at least:

1700 * 300kbps = 510Mbps

IDE isn't going to cut it. ;-)  I've done systems of this magnitude
using FiberChannel attached EMC storage arrays into Compaq Proliant
boxes.  In my case, I was using multiple 100Mbps NICs, but the concepts
are the same.

T.

> Assuming 300KBIT streams, ON-Demand, "infinite
> bandwidth", 2GB RAM
>
> What is the max (rough neighborhood, very rough is OK)
> concurrent connections with:

Signature

Tim Carter / StreamingMeeMee
Frontier Digital
PH: 508.982.4800
AIM: streamingmeemee  MSN: streamingmeemee@hotmail.com
Microsoft Digital Media MVP 2002-2004

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.