On Sep 15, 2:37 pm, Simon Large <simon.tortoise..._at_googlemail.com>
wrote:
> > Are all working copies on the machine affected (i.e. does updating a
> > fresh checkout also take so much time)?
>
> > If a fresh working copy is quicker then the timestamps in the working
> > copy may be off, forcing SVN to compare files to their base copy to
> > see if there are local modifications.
>
> This would happen if an application changes the datestamps on files
> even when the content is unchanged. If date is changed but length is
> the same, Subversion will do a byte-by-byte compare. You can fix the
> timestamps using TSVN->Cleanup.
>
> Do you get the same problems if you use the subversion command line client?
>
> Simon
>
It makes no difference if its a newly chocked out fresh working copy
or if its an old working copy. Perhaps a slightly longer pause but
since the pauses have different lengths almost every time (althought
almost never no pause at all) I dont think its a factor.
Cleanup doesnt make a difference either I'm afraid
And yes, we have the same trouble with the command line tool. I can
see that there is a lot of disk activity during the pauses. Is there
some way to log what is being done on the client. Is it going through
the entire working copy? Both before and after getting files?
I have tried different versions of Tortoise and SVN but no
difference.....I am at a loss
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2395906
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-09-17 12:43:08 CEST