public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Jason Molenda <jason@molenda.com>
To: Jim Kingdon <kingdon@redhat.com>
Cc: overseers@sourceware.cygnus.com
Subject: Re: ftp load
Date: Tue, 14 Mar 2000 14:20:00 -0000	[thread overview]
Message-ID: <20000314141927.A29899@shell17.ba.best.com> (raw)
Message-ID: <20000314142000.XcnLxvYGbsLKdzuUfZXWQMFDj9cXYEf8WbEhVfn3VRI@z> (raw)
In-Reply-To: <200003142156.QAA22288@devserv.devel.redhat.com>

On Tue, Mar 14, 2000 at 04:56:17PM -0500, Jim Kingdon wrote:

> I'm not sure I was right.  If anyone
> wants to crunch the numbers at
> http://sourceware.cygnus.com/sourceware/bandwidth/ please do.  Right
> now I'm getting:


The numbers here really aren't (IMHO) that useful when comparing
against the actual line bandwidth.  All service-protocol overhead
and TCP/IP-level overhead goes unaccounted for.  Some protocols,
like HTTP, are chatty and many connections are short-lived, so the
overhead is not insignificant.  And CVS, rsync, and mail go completely
unmeasured in the bandwidth reports (and mail, at least, is a couple
of GB a week).

BBN can give us network usage graphs -- these are what you want.
I used to be able to get these from Ian Elverson.  Maybe if you
ask Marc real nice he could ask for them.  Or maybe give you a
contact addr at BBN where you could get them to send the things to
you.

The overall bandwidth number isn't very useful because it tells
you nothing about how loaded the network is during the prime-time
hours, i.e. the time we really care about.

You can see what the graph looks like here (this is measuring the
Cygnus T1 on the week when sourceware went to its own net):

   http://sourceware.cygnus.com/sourceware/bandwidth/net-usage-1999-12-12.jpg

On the topic of colocation -- this is something that the RH IS guys
came to IanE about right near the beginning, so _someone_ had it in
mind or in a plan at some point.  I don't know who had contacted Ian
about this or how serious they were about doing it.

Jason

  parent reply	other threads:[~2000-03-14 14:20 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-30  6:08 Stan Shebs
2000-03-14  8:32 ` Stan Shebs
2000-12-30  6:08 ` Jeffrey A Law
2000-03-14  8:45   ` Jeffrey A Law
2000-12-30  6:08   ` Chris Faylor
2000-03-14  9:35     ` Chris Faylor
2000-12-30  6:08     ` Bart Veer
2000-03-14  9:42       ` Bart Veer
2000-12-30  6:08   ` Jim Kingdon
2000-03-14 13:56     ` Jim Kingdon
2000-12-30  6:08     ` Jason Molenda [this message]
2000-03-14 14:20       ` Jason Molenda
2000-12-30  6:08     ` Bart Veer
2000-03-15  3:29       ` Bart Veer
2000-12-30  6:08       ` Chris Faylor
2000-03-15  5:38         ` Chris Faylor
2000-12-30  6:08         ` Jim Kingdon
2000-03-15  6:26           ` Jim Kingdon
2000-12-30  6:08           ` Chris Faylor
2000-03-15  6:30             ` Chris Faylor
2000-12-30  6:08             ` Jim Kingdon
2000-03-15  6:46               ` Jim Kingdon
2000-12-30  6:08               ` Chris Faylor
2000-03-15  7:00                 ` Chris Faylor
2000-12-30  6:08   ` Mark Galassi
2000-03-14 10:43     ` Mark Galassi
2000-12-30  6:08 Louis Stone-Collonge
2000-03-21 22:14 ` Louis Stone-Collonge
2000-12-30  6:08 ` 'Chris Faylor'
2000-03-21 22:17   ` 'Chris Faylor'
2000-12-30  6:08 ` Jim Kingdon
2000-03-22  6:49   ` Jim Kingdon
2000-12-30  6:08   ` Stan Shebs
2000-03-23  8:32     ` Stan Shebs

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20000314141927.A29899@shell17.ba.best.com \
    --to=jason@molenda.com \
    --cc=kingdon@redhat.com \
    --cc=overseers@sourceware.cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).