[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: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2004-02-15 23:30:24 CET

Tobias Ringström <tobias@ringstrom.mine.nu> writes:

> I'm thinking of adding an --in-memory option. The question of what
> should be the default is interesting. If we can make the DB-version
> faster, the question is moot, of course. As it stands right now, I'd
> personally prefer to make in-memory be default, and add a --huge-repos
> options for slow on-disk processing. I wouldn't dare to do that
> without support on the dev list of course.

-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.

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:31:27 2004

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

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