From: DJ Delorie <dj@delorie.com>
To: pfeifer@dbai.tuwien.ac.at
Cc: overseers@sourceware.cygnus.com, jason-swarelist@molenda.com,
cgf@cygnus.com, kingdon@panix.com, shebs@shebs.cnchost.com
Subject: Re: [Fwd: ftp probs]
Date: Sat, 30 Dec 2000 06:08:00 -0000 [thread overview]
Message-ID: <200006211521.LAA11283@envy.delorie.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0006211627060.16472-100000@nunki.dbai.tuwien.ac.at>
> As far as I understood DJ's analysis, this alone has the potential
> to save at least 10% (possibly more) of overall traffic.
That depends on how much of the snapshot traffic is from users vs
mirror sites (all mirrors download snapshots every day), and what
percent of the snapshot traffic is gcc vs binutils, gdb, cygwin, etc.
Cutting the frequency (or size) of snapshots is the only way to cut
down the traffic from mirror sites.
However, pointing away from sourceware's ftp will help.
WARNING: multiple messages have this Message-ID
From: DJ Delorie <dj@delorie.com>
To: pfeifer@dbai.tuwien.ac.at
Cc: overseers@sourceware.cygnus.com, jason-swarelist@molenda.com,
cgf@cygnus.com, kingdon@panix.com, shebs@shebs.cnchost.com
Subject: Re: [Fwd: ftp probs]
Date: Wed, 21 Jun 2000 08:21:00 -0000 [thread overview]
Message-ID: <200006211521.LAA11283@envy.delorie.com> (raw)
Message-ID: <20000621082100.MD4gYnBmWD3O1DKcYKdMz-6UWo9Le2kMwj-AadYnK7o@z> (raw)
In-Reply-To: <Pine.GSO.4.21.0006211627060.16472-100000@nunki.dbai.tuwien.ac.at>
> As far as I understood DJ's analysis, this alone has the potential
> to save at least 10% (possibly more) of overall traffic.
That depends on how much of the snapshot traffic is from users vs
mirror sites (all mirrors download snapshots every day), and what
percent of the snapshot traffic is gcc vs binutils, gdb, cygwin, etc.
Cutting the frequency (or size) of snapshots is the only way to cut
down the traffic from mirror sites.
However, pointing away from sourceware's ftp will help.
next prev parent reply other threads:[~2000-12-30 6:08 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 6:08 Stan Shebs
2000-06-20 22:05 ` Stan Shebs
2000-12-30 6:08 ` Jim Kingdon
2000-06-20 22:29 ` Jim Kingdon
2000-12-30 6:08 ` Chris Faylor
2000-06-20 22:38 ` Chris Faylor
2000-12-30 6:08 ` Jason Molenda
2000-06-20 23:57 ` Jason Molenda
2000-12-30 6:08 ` DJ Delorie
2000-06-21 7:54 ` DJ Delorie
2000-12-30 6:08 ` Chris Faylor
2000-06-21 8:00 ` Chris Faylor
2000-12-30 6:08 ` DJ Delorie
2000-06-21 8:19 ` DJ Delorie
2000-12-30 6:08 ` Jason Molenda
2000-06-21 0:09 ` Jason Molenda
2000-12-30 6:08 ` DJ Delorie
2000-06-21 7:13 ` DJ Delorie
2000-12-30 6:08 ` Gerald Pfeifer
2000-06-21 8:11 ` Gerald Pfeifer
2000-12-30 6:08 ` Jeffrey A Law
2000-06-21 8:30 ` Jeffrey A Law
2000-12-30 6:08 ` Gerald Pfeifer
2000-06-22 14:12 ` Gerald Pfeifer
2000-12-30 6:08 ` DJ Delorie
2000-06-21 8:39 ` DJ Delorie
2000-12-30 6:08 ` DJ Delorie [this message]
2000-06-21 8:21 ` DJ Delorie
2000-12-30 6:08 ` DJ Delorie
2000-06-21 7:11 ` DJ Delorie
2000-12-30 6:08 ` Chris Faylor
2000-06-20 22:13 ` Chris Faylor
2000-12-30 6:08 ` Jeffrey A Law
2000-06-21 8:47 ` Jeffrey A Law
2000-12-30 6:08 ` Jim Kingdon
2000-06-20 22:36 ` Jim Kingdon
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=200006211521.LAA11283@envy.delorie.com \
--to=dj@delorie.com \
--cc=cgf@cygnus.com \
--cc=jason-swarelist@molenda.com \
--cc=kingdon@panix.com \
--cc=overseers@sourceware.cygnus.com \
--cc=pfeifer@dbai.tuwien.ac.at \
--cc=shebs@shebs.cnchost.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).