[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Corrupt repository on large commit (was Re: svn+ssh on Win32)

From: Steve Williams <stevewilliams_at_kromestudios.com>
Date: 2003-07-21 23:37:37 CEST

> > Project #1 takes much longer (longer than Project #2) to perform the
> > initial checkout.
> > Again, it is my belief that it is the number of files, not the size of
> > them, that causes the checkout to take so long.
> Yes, absolutely. A huge number of files will cause a huge REPORT
> response from the server. If the server is *buffering* the entire
> report before sending it to you, it will take a *really* long time
> before you see a single file added to your working copy.
> Please please please, upgrade to 0.25, and turn off mod_deflate.

As I said in my response, the client was hammering the local drive when the
timeout error occurred. There was no network activity and no server drive
activity. Surely this is not a sign that the server is buffering the
report? I think the client was dealing with the report at the time the
timeout error occurred.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 21 23:38:33 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.