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

Re: suggestions for large project (90K files, 930MB) - slow svn status

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-12-14 03:00:20 CET

On Dec 13, 2004, at 5:54 PM, Tim Harvey wrote:
> I ran a test where I created an FSFS repository and imported the tree.
> Doing a
> 'svn status' at the top of the tree takes 4 minutes, which is going
> to make it
> fairly unusable for me. Does this 4 minutes sound right?

Sure, why not? How long would you expect 90,000 stat() calls to take?
That's about 375 stat() calls per second. That seems pretty good, no?

Remember that 'svn up' and 'svn commit' do the same thing. So be
prepared for the same pain if you run those commands from the top of
such a huge working copy.

I certainly wouldn't expect CVS to behave any differently here...

> Thanks for any suggestions

My suggestion is that you not run 'svn status' from the top of such a
huge working copy. :-)

Work in smaller pieces... check out smaller sections of the repository.
  Run 'svn status' and 'svn commit' on directories lower-down in the
hierarchy when you can. I imagine the *only* time you would run 'svn
status' or 'svn commit' is when you absolutely need to commit a whole
bunch of spread-out changes as a single changeset.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Dec 14 03:04:54 2004

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

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