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

Re: Speeding up cvs2svn (was Re: cvs2svn takes very long time to execute (days!))

From: <kfogel_at_collab.net>
Date: 2004-02-15 22:54:04 CET

"C. Michael Pilato" <cmpilato@collab.net> writes:
> -1 on making the --in-memory version the default. Generally speaking,
> folks are more likely to run out of RAM before running out of disk.
> It would be Badness for someone who had a big repository to run their
> conversion for hours and then have it fail because they hit the
> generally much smaller of the two available boundaries. Remember,
> most OSes (with which I'm familiar, at least) have some notion of a
> ramdisk -- folks can use that today without changes to cvs2svn itself.

I have to agree with Mike here. The most important thing is that
cvs2svn work out of the box, no matter what the input. Even
performance is secondary to that.

(But, if we can find a make it perform better without more thought on
the part of the user, then we win all around.)


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Feb 15 23:56:10 2004

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