RE: [cobalt-users] Bandwidth Calculations?

["Footballist " <footballist@xxxxxxxxxx>]

John,

Thank you for your detail and thorough explanations.

According to your below example, if my traffic is calculated to be 382
kilobits per second, does this number (382) get multiplied by the number
of seconds per month or what?

Anohter words, with my service, I have about 50 Gig of monthly bandwidth.
 Anything over that I will be charged extra.

So how would 382 kilobits per second translate n Gig per month????


---- "John M Troher" <admin@xxxxxxxx> wrote:
> the way alot of ISP's calculate bandwidth based on the 95th percentile
> 
> input/output readings are taken every 5 minutes on a fractional T1
> for
> example.
> 
> at the end of the month, the top 5 highest reading are thrown out.
> the highest remaining reading would be the usage based on the 95th
> percentile.
> 
> example 5 highest readings are  384, 422, 765, 492, 602 kilobits per
> second/input ,  these get tossed.
> 
> the highest remaining reading was 382 kilobits per second/input
> 
> you would be charged for the month based on 382 kilobits per second.
> 
> that is roughly how it works, many isp's do things different, but it
> is
> usually based on this process.
> 
> 
> 
> -----Original Message-----
> From: cobalt-users-admin@xxxxxxxxxxxxxxx
> [mailto:cobalt-users-admin@xxxxxxxxxxxxxxx]On Behalf Of Rodolfo J.
> Paiz
> Sent: Wednesday, June 06, 2001 1:32 PM
> To: cobalt-users@xxxxxxxxxxxxxxx
> Subject: Re: [cobalt-users] Bandwidth Calculations?
> 
> 
> At 6/6/01 09:05 AM -0700, you wrote:
> >Does anybody know how the bandwidth is calculated?
> 
> Can be done different ways. Ask your ISP for their particular method
> as
> there is no one "right" way. However...
> 
> >1. I have a box that receives lots of unwanted traffic.
> 
> >2. I do lots of non-httpd traffic on my own (i.e. upload and download
> >huge files using rsync).
> 
> >3. If I go fetching some pages (i.e. spider or crawlwer) using non
> httpd
> >means,
> 
> You seem to have the idea that HTTP is somehow different from other
> traffic. HTTP is a protocol, used for an application, whereas "traffic"
> is
> all about IP packets which are on a much lower level.
> 
> If you're a city planner considering a given road, you care how many
> *vehicles* use it so you know whether you have enough lanes. You do
> not
> give a damn whether they're cars, motorcycles, vans, or pickup trucks
> (let's leave out the semis here for a moment).
> 
> Bandwidth is measured in bits per second, traffic is measured in bits.
> What
> those bits contain is irrelevant. Generally yes, all those huge files
> *do*
> count towards your traffic allotment.
> 
> 
> --
> Rodolfo J. Paiz
> rpaiz@xxxxxxxxxxxxxx
> 
> _______________________________________________
> cobalt-users mailing list
> cobalt-users@xxxxxxxxxxxxxxx
> To Subscribe or Unsubscribe, please go to:
> http://list.cobalt.com/mailman/listinfo/cobalt-users
> 
> _______________________________________________
> cobalt-users mailing list
> cobalt-users@xxxxxxxxxxxxxxx
> To Subscribe or Unsubscribe, please go to:
> http://list.cobalt.com/mailman/listinfo/cobalt-users
> 

__________________________________________________
FREE voicemail, email, and fax...all in one place.
Sign Up Now! http://www.onebox.com