From: Christopher Faylor <cgf@redhat.com>
To: Jason Molenda <jason-swarelist@molenda.com>
Cc: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>,
overseers@gcc.gnu.org, Zack Weinberg <zack@codesourcery.com>,
"Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>,
gcc@gcc.gnu.org, gdb@sources.redhat.com, jimb@redhat.com,
rth@redhat.com
Subject: Re: gcc development schedule [Re: sharing libcpp between GDB and GCC]
Date: Thu, 28 Mar 2002 07:17:00 -0000 [thread overview]
Message-ID: <20020328151711.GB11781@redhat.com> (raw)
In-Reply-To: <20020328020102.A31507@molenda.com>
On Thu, Mar 28, 2002 at 02:01:02AM -0800, Jason Molenda wrote:
>On Thu, Mar 28, 2002 at 01:53:46AM -0800, Jason Molenda wrote:
>
>> None that I know of. cvs logging bites. We do track the # of
>> bytes being sent/received from different hosts and the frequency
>> with which hosts connect. The host that downloaded the most number
>> of bytes last week by anoncvs? A purdue.edu site. Two redhat.com
>> and one suse.de sites make the top six; an IP# and a cable modem
>> (rogers.com) finish out the top six. Not very useful without some
>> idea what repository or what sorts of operations we're talking
>> about.
>
>Ahem, this is how it looks when sorted by connections, but it's
>rather different when sorted by bytes downloaded. For last week,
>it looks more like this:
>
>698 358 959 cwi.nl
>523 131 718 cpe.net.cable.rogers.com
>316 859 474 dsl.snfc21.pacbell.net
>302 256 065 sympatico.ca
>220 184 438 austin.ibm.com
>208 933 189 redhat.com
>175 256 836 mypointsinc.com
>144 845 712 dip.t-dialin.net
>
>The first field is bytes transferred over the week; the second is
>the domains for these sites.
>
>It's easy to think these sites are doing something Evil, but chances
>are they're just doing some automated cvs updates on multiple
>repositories once or twice a day, or they had a single big checkout
>of gcc/src and a periodic cvs update or what have you. Don't read
>too much into it without looking closer - I'm just providing an
>example of what we do track and what we can report.
Btw, just as a data point, I did make a change wrt anoncvs access
last week sometime. I upped the load average block so that anoncvs
would still keep working under high loads. There is still a maximum
of 10 anoncvs processes possible, though. I can lower that but then
the anoncvs people will be complaining.
FWIW, I don't know what's special about me but I'm not seeing a problem
with cvs update. Maybe I'm just hitting it at the right time.
cgf
next prev parent reply other threads:[~2002-03-28 15:17 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-27 19:17 Kaveh R. Ghazi
2002-03-27 19:46 ` Zack Weinberg
2002-03-28 1:24 ` Gerald Pfeifer
2002-03-28 1:53 ` Jason Molenda
2002-03-28 2:01 ` Jason Molenda
2002-03-28 7:17 ` Christopher Faylor [this message]
2002-03-28 9:01 ` David O'Brien
2002-03-28 21:29 ` Christopher Faylor
2002-03-28 9:00 ` David O'Brien
2002-04-03 14:19 ` Jim Blandy
2002-04-03 14:29 ` Phil Edwards
2002-03-28 12:34 ` Phil Edwards
-- strict thread matches above, loose matches on Subject: below --
2002-03-27 6:01 Robert Dewar
2002-03-25 15:40 sharing libcpp between GDB and GCC Jim Blandy
2002-03-25 20:07 ` Zack Weinberg
2002-03-26 14:29 ` gcc development schedule [Re: sharing libcpp between GDB and GCC] Richard Henderson
2002-03-26 14:37 ` David Edelsohn
2002-03-26 21:32 ` Andreas Jaeger
2002-03-26 15:17 ` Neil Booth
2002-03-26 15:30 ` Tom Lord
2002-03-26 15:40 ` David Edelsohn
2002-03-26 16:03 ` Tom Lord
2002-03-26 16:41 ` Tim Hollebeek
2002-03-26 22:23 ` Eli Zaretskii
2002-03-26 22:43 ` Tom Lord
2002-03-27 7:18 ` mike stump
2002-03-27 9:00 ` law
2002-03-27 10:13 ` Neil Booth
2002-03-26 22:45 ` Tom Lord
2002-03-26 23:11 ` Daniel Berlin
2002-03-26 23:53 ` Tom Lord
2002-03-27 4:32 ` Fergus Henderson
2002-03-27 6:30 ` Andrew Cagney
2002-03-27 6:43 ` Gianni Mariani
2002-03-26 22:39 ` Andreas Jaeger
2002-03-26 22:54 ` Tom Lord
2002-03-26 15:31 ` Zack Weinberg
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=20020328151711.GB11781@redhat.com \
--to=cgf@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=ghazi@caip.rutgers.edu \
--cc=jason-swarelist@molenda.com \
--cc=jimb@redhat.com \
--cc=overseers@gcc.gnu.org \
--cc=pfeifer@dbai.tuwien.ac.at \
--cc=rth@redhat.com \
--cc=zack@codesourcery.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