| You are here: Home > Reference Guides > Bandwidth |
| ||||||||||||||||
|
|
Back to Reference GuidesBandwidthTo make an informed decision regarding bandwidth for web hosting solutions, be it for a dynamic ecommerce site or static media servers, an understanding of basic terminology is in order. Bit (connection) vs Byte (transfer or storage)The measurement of the network connections is done in bits as opposed to data transfer and computer storage which we measure in bytes. Eight bits is the equivalent of one byte. Thus a 100Mbps (Mega bit per second) can handle 12Megabytes of data per second.Units of measurement
To get a meaningful estimate of throughput, divide the data connection pipe by eight. i.e. A 56K modem can download at a maximum throughput of around 7KiloBytes per second. Residential Lines
Dedicated Pipes (Web Hosting in Data Centers)
Bandwidth, How to Choose?Which is better, (a) a fixed 2,500 Gigs of transfer per month (a shared 100Mbps pipe, by 20 servers) or (b) an unlimited 10Mbps pipe?Of course, (a) hands down! Why? A 10Mbps pipe can handle a MAXIMUM throughput of 3,240 Gigs of data transfer per month (30 days). Since almost ALL traffic occurs on some sort of bell curve, your server will start to suffer LONG before it ever reaches that theoretical limit. Think gridlock, rush hour in downtown LA. At 50% of your theoretical throughput limit, you would have already started suffering long delays/lag time during your peak hours of operations and it is time to move to a bigger pipe. A 10Mbps connection can handle websites of up to 1,600 Gigs of transfer a month. A 100Mbps connection can handle websites of up to 16,000 Gigs of transfer a month. Typical website bandwidth load per month?99% of websites consume less then 10Gigs of data transfer a month.As soon as your website exceeds 300Gigs of data transfer a month (or makes intensive use of CPU or diskspace) then it will be time to place it on its own server. Once you exceed 1,500 Gigs of data transfer a month time to start thinking about a load balancer, or a web farm. Once you are at that point it is a question of what parts of the system do you want to farm out. A common solution is creating an image server web rack. In that case you can skip the load balancer and go with a round robin DNS solution. A domain name would have multiple IP addresses associated to it, each request would go out to each domain in a round robin sequence) If its a forum that is causing the load then making a db only server could be the way to go. It would then be easier to cluster that server as the load increases. Hope that helps would be web masters to plan out how to grow their web sites, and as a final note, get a hosting provider that can provide real phone support when you need it |
||||||||||||||||||||||||||||||||||||||||||||||||||
|
contact us: elouai@gmail.com ©2003-2008 eLouai.com, All rights reserved |