Re: svn update slow / post-commit issues

Well, I did two things to cut the update times down to nothing (well 3
seconds via HTTP and 2 seconds using file://).

1.) Removed a directory that was filled with dynamically created
content (ie. a new folder for each record is created in a single
directory - legacy code - don't yell at me). This had 2500'ish
directories each with 1-N images (about 400MB on disk).

2.) Switched from using my.domain.com to 192.168.1.25

I'm sure #1 had more to do with it than anything else.

--Joe

--
Joseph C. Stump
joe@joestump.net
http://www.joestump.net
On Mar 22, 2005, at 4:11 PM, Ben Collins-Sussman wrote:
>
> On Mar 22, 2005, at 5:44 PM, Joe Stump wrote:
>
>> Thanks for the comparison numbers, but I'm not sure what could be 
>> "seriously wrong" with my setup. I have everything set up per the 
>> book and I'm on a local network. I'm able to reproduce the delay 
>> using file:// as well.
>>
>
> Is your working copy really large in terms of the number of files and 
> directories?
>
> 'svn update' needs to crawl the working copy and read every single 
> .svn/entries file in every directory.  Then it reports the 
> working-revs to the server.  Can you do tests to figure out what's 
> taking so long?  For example, are there many minutes of client disk 
> I/O before the server begins to send a network response?  Where is the 
> delay happening?
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org