> From: Robert Cronk [mailto:rcronk@altiris.com]
>
> 1. client speed - we have a big repository since we include
> our build tools in the repository and updates and statuses
> can take over a minute to complete.
I suspect the problem is the size of your repository. The only 100% safe
way to check whether the WC file has been modified is to do a byte-by-byte
comparison with the "pristine" copies. Unfortunately, doing this for an
entire WC is a worst-case for disk cacheing -- each "svn status" will go
through all those files in order. If both sets of files can fit in your
disk cache together, the comparison will run quite quickly. If not, svn
*has* to read all the files from the disk, every time.
I suspect that other SCMs cheat a bit, and assume that if the modification
time of the file hasn't changed since it was checked out that it is
unchanged. That would dramatically reduce the pressure on the disk cache.
Dale
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Aug 22 16:59:23 2005