This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Serious problems accessing cvs
- To: "Martin v. Loewis" <martin at loewis dot home dot cs dot tu-berlin dot de>
- Subject: Re: Serious problems accessing cvs
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Tue, 07 Mar 2000 14:34:32 -0700
- cc: kenner at vlsi1 dot ultra dot nyu dot edu, gcc at gcc dot gnu dot org
- Reply-To: law at cygnus dot com
In message <200003072123.WAA01557@loewis.home.cs.tu-berlin.de>you write:
> > If it's really a bandwidth problem, then throttling back the ftp access
> > should help.
>
> I'm not entirely certain about that. I notice that updating works
> quite well when I have no local changes. As soon as it starts merging
> at the other end, it won't come back. I then kill the update, restart
> it again, and it sometimes succeeds with the first file to merge, then
> hangs again.
The more local changes you have, the more data that has to be moved across
the wire. For each file you change, assume that a copy of it has to be
moved across the net at least once, possibly twice (I'm not a CVS expert, I
can only report what I see in practice).
That machine has cpu, memory & disk bandwidth to burn -- we're not even
close to hitting the capacity of that machine (we're typically using
less than 15% of the cpu horsepower on that box).
The only other thing I can think of is maybe y'all are hitting the machine
during its backup cycle, web database rebuilds or some other nightly task
(which will peg cpu & disk bandwidth for significant periods of time).
I believe ya'll both indicated when you were having trouble, but I don't
have those messages handy. Can you send me that data privately and I'll
try to see if it corresponds to any of the cron jobs on that box.
jeff