Hosting guys - difference between mbps and gigs? - GoFuckYourself.com

jawanda · 09-28-2005, 11:47 AM

Can someone explain to me in laymen's terms the relationship between mbps and gigs per month?

I'm a bit confused ... how do you calculate something like gigs per month based on a per second speed?

Thanks,

-P

jawanda · 09-28-2005, 11:51 AM

come on guys ... it's a simple question no?

thanks,

-P

zagi · 09-28-2005, 11:53 AM

Mbps is transfer speed like miles per hour

10Mbps say is 60Mph

And GB is the transfer amount or miles travelled

Like 60 Miles in 1 hour of travel at 60Mph

Roughly 1Mbps of transfer speed held steady for a month results in 300GB transferred

pronwatcher · 09-28-2005, 12:00 PM

Like another poster said MB per second is like renting a car - if you go 75 miles an hour they charge you more than if you went 20 miles an hour.
GB / Total Transfer is billed based on the total amount of traffic going to your server/web sites. Or, as in our example, the total distance traveled.

Most ISPs use 95th percentile billing for traffic. You can read more about it at http://www.seanadams.com/95/ -- basically, you're charged for the amount of traffic you use 95 percent of the time. This is actually a very fare number - it removes spikes and tells you how much actual traffic your website/server are experiencing. For anything over 1-3 mb/s, this is the most effecient, cheapest bandwidth monitoring.

Small web hosts will often offer billing per gigabyte transferred. This is useful for very small web sites where you're only expecting a few gigs of transfer a month. The cost of per gigabyte is often fixed and you pay for all that you use.

Brad Mitchell · 09-28-2005, 01:08 PM

It's basically like this:

Per gigabyte billing related to megabit per second MBPS in the following way. If your server were to push out 1 megabit constantly for a 30 day month with no up or downswing you would push approximately 320 gigabytes. The reality is that a server's inbound and outbound traffic looks more like the stock market with highs and lows. So, with billing on per mbps on 95th percentile to actually push 320 gigabytes you would most definitely be at more than one megabit with average traffic patterns - probably around two but potentially as much as 3 megabit if you traffic was very spikey.

Both measurements can be taken on your server's 10/100/1000 port where a sample of the amount of traffic being pushed out every 5 minutes is taken. Over the course of a month all of the samples are stored and then at the end of the month the top 5% highest samples are dropped on 95th percentile per megabit billing (some 400 or so samples) that represent about your 30 hours of peak usage.

All hosts pay their upstream providers on either 95th percentile billing or by buying full ports, regardless of how much is used. For example, a host might purchase 100 megabit on a gigabit port and will pay for at least the first hundred megabit as he is committed to that and then will have to pay overage if his overall 95th percentile measurement comes in over 100 megabit. Conversely, a host might purchase 100 megabit on a 100 megabit port and if he doesn't use all of the bandwidth all of the time (which a host couldn't unless he was oversubscribing and then choosing to drop packets when he is otherwise peaking over 100 megabit) just like a host could flat out choose to purchase a gigabit of bandwidth regardless of whether or not he uses it.

Most hosts charge on 95th for clients that use more than a few hundred gigabytes because that is the only metric that ties back to their cost structure. Selling by the gigabyte unless it is at a high rate puts a host at risk for someone who might say peak at 30 megabit during the day but have lows of a few megabit and only end up pushing out a thousand gigs. I have a client who is very "peaky" like that because he does live web cams so his traffic is through the roof in the evenings. To charge him on any other measurement would put me at risk of losing money on the traffic.

Hope that helps!

Cheers,

Brad

aico · 09-28-2005, 01:13 PM

Quote:

Originally Posted by zagi

Mbps is transfer speed like miles per hour

10Mbps say is 60Mph

And GB is the transfer amount or miles travelled

Like 60 Miles in 1 hour of travel at 60Mph

Roughly 1Mbps of transfer speed held steady for a month results in 300GB transferred

I keep hearing this figure but I have yet to see it. For example, my server is at 4.48 Mbps for this month and have 424.03GB used...

jawanda · 09-28-2005, 01:22 PM

thanks for the info people, very helpful

-P

09-28-2005, 01:25 PM

1 megabit/s (mbit) is like is 0.125 megabyte/s (1 byte = 8 bit)

So...

If you're pushing the server 1 mbit all the time for one month .. YOU BURN:

0.125 megabyte/sec x 60 (to get minutes) x 60 (to get hours) x 24 (for one day) x 30 for one month = 3.240.000 MEGABYTES /1000 =

324 GIGABYTES / month

Well, if you have a 10mbit server you can theoretically burn 3240 GIGABYTES

09-28-2005, 11:47 AM	#1
jawanda Confirmed User Join Date: Feb 2003 Posts: 6,040	Hosting guys - difference between mbps and gigs? Can someone explain to me in laymen's terms the relationship between mbps and gigs per month? I'm a bit confused ... how do you calculate something like gigs per month based on a per second speed? Thanks, -P

09-28-2005, 11:53 AM	#3
zagi Confirmed User Join Date: Jan 2004 Posts: 1,238	Mbps is transfer speed like miles per hour 10Mbps say is 60Mph And GB is the transfer amount or miles travelled Like 60 Miles in 1 hour of travel at 60Mph Roughly 1Mbps of transfer speed held steady for a month results in 300GB transferred __________________ Managed US/NL Hosting [ [Reality Check Network ] Dell XEON Servers + 1/2/3 TB Packages ICQ: 4-930-562

09-28-2005, 12:00 PM	#4
pronwatcher Registered User Join Date: Aug 2005 Posts: 8	MB vs GB Like another poster said MB per second is like renting a car - if you go 75 miles an hour they charge you more than if you went 20 miles an hour. GB / Total Transfer is billed based on the total amount of traffic going to your server/web sites. Or, as in our example, the total distance traveled. Most ISPs use 95th percentile billing for traffic. You can read more about it at http://www.seanadams.com/95/ -- basically, you're charged for the amount of traffic you use 95 percent of the time. This is actually a very fare number - it removes spikes and tells you how much actual traffic your website/server are experiencing. For anything over 1-3 mb/s, this is the most effecient, cheapest bandwidth monitoring. Small web hosts will often offer billing per gigabyte transferred. This is useful for very small web sites where you're only expecting a few gigs of transfer a month. The cost of per gigabyte is often fixed and you pay for all that you use.

09-28-2005, 01:08 PM	#5
Brad Mitchell Confirmed User Industry Role: Join Date: Nov 2001 Location: Southfield, MI Posts: 9,813	It's basically like this: Per gigabyte billing related to megabit per second MBPS in the following way. If your server were to push out 1 megabit constantly for a 30 day month with no up or downswing you would push approximately 320 gigabytes. The reality is that a server's inbound and outbound traffic looks more like the stock market with highs and lows. So, with billing on per mbps on 95th percentile to actually push 320 gigabytes you would most definitely be at more than one megabit with average traffic patterns - probably around two but potentially as much as 3 megabit if you traffic was very spikey. Both measurements can be taken on your server's 10/100/1000 port where a sample of the amount of traffic being pushed out every 5 minutes is taken. Over the course of a month all of the samples are stored and then at the end of the month the top 5% highest samples are dropped on 95th percentile per megabit billing (some 400 or so samples) that represent about your 30 hours of peak usage. All hosts pay their upstream providers on either 95th percentile billing or by buying full ports, regardless of how much is used. For example, a host might purchase 100 megabit on a gigabit port and will pay for at least the first hundred megabit as he is committed to that and then will have to pay overage if his overall 95th percentile measurement comes in over 100 megabit. Conversely, a host might purchase 100 megabit on a 100 megabit port and if he doesn't use all of the bandwidth all of the time (which a host couldn't unless he was oversubscribing and then choosing to drop packets when he is otherwise peaking over 100 megabit) just like a host could flat out choose to purchase a gigabit of bandwidth regardless of whether or not he uses it. Most hosts charge on 95th for clients that use more than a few hundred gigabytes because that is the only metric that ties back to their cost structure. Selling by the gigabyte unless it is at a high rate puts a host at risk for someone who might say peak at 30 megabit during the day but have lows of a few megabit and only end up pushing out a thousand gigs. I have a client who is very "peaky" like that because he does live web cams so his traffic is through the roof in the evenings. To charge him on any other measurement would put me at risk of losing money on the traffic. Hope that helps! Cheers, Brad __________________ President at MojoHost \| brad at mojohost dot com \| Skype MojoHostBrad 71 industry awards for hosting and professional excellence since 1999

09-28-2005, 01:25 PM	#8
Gasper Guest Posts: n/a	1 megabit/s (mbit) is like is 0.125 megabyte/s (1 byte = 8 bit) So... If you're pushing the server 1 mbit all the time for one month .. YOU BURN: 0.125 megabyte/sec x 60 (to get minutes) x 60 (to get hours) x 24 (for one day) x 30 for one month = 3.240.000 MEGABYTES /1000 = 324 GIGABYTES / month Well, if you have a 10mbit server you can theoretically burn 3240 GIGABYTES Last edited by Gasper; 09-28-2005 at 01:27 PM..

09-28-2005, 11:51 AM	#2
jawanda Confirmed User Join Date: Feb 2003 Posts: 6,040	come on guys ... it's a simple question no? thanks, -P

09-28-2005, 01:22 PM	#7
jawanda Confirmed User Join Date: Feb 2003 Posts: 6,040	thanks for the info people, very helpful -P