Paul Lussier <pll@lanminds.com> writes:
> $ time svn status -u -v > /tmp/foo
> real 3m19.599s
> user 2m13.660s
> sys 0m5.260s
>
> This kernel tree is fresh from kernel.org, and immediately after an
> 'svn import' and 'svn co'. So, other than the svn overhead[1], this is
> pristine kernel source. 3 minutes 20 seconds seems a little long to
> determine the status of an unchanged repository, though, doesn't it?
Yes it does.
> Does svn cache changes anywhere? Or does it need to check diffs
> between each and every file in the repo and in the .svn area?
Upgrade to the latest source, and we have better caching now. "svn
status" is about 5 times faster.
> [1] The size of the svn repo is > 3x the size of just the raw
> kernel tree:
>
> Checked out revision 1.
> pll@tater:/usr/local/src$ du -sh linux-2.4.19/
> 479M linux-2.4.19
>
> pll@tater:/usr/local/src/foo$ tar jxf ../tars/linux-2.4.19.tar.bz2
> pll@tater:/usr/local/src/foo$ du -sh linux-2.4.19/
> 159M linux-2.4.19
>
> Don't know if that matters, but it might well be why the 'svn status'
> takes so long.
The size of the repository is irrelevant. 'svn status' doesn't use
the network. You want to remove extra logfiles in the repos,
however. See all the log* files in there? db_archive will tell you
which ones can be removed... probably most of them.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 8 22:17:22 2002