You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Kai Bartels <ka...@picturesafe.de> on 2004/03/08 10:11:49 UTC

Re: [w] cvs2svn: Conversion taking a very long time

Hi Mike, hi *!

I experienced the same behaviour when trying to convert our local repository.
It has just about 2G, a lot of files, some of them 5 to 6 years old, some
with hundreds of revisions. I had the repository nfs-mounted to the machine
that ran cvs2svn and normally stopped the programm after a few days.

On the other hands there were reports on this list of a much larger repository
(about 10G) having been converted in just 10h. The important difference
maybe that it had much less overall revisions (don't remember exactly, maybe
12000).

I'm just now giving it a try with a newer version of cvs2svn and a local
copy of the repository (i.e. without nfs).

greetings, Kai


On Sun, Mar 07, 2004 at 10:18:08AM +0000, Mike Crowe wrote:
> I have been trying to convert a sizeable CVS repository to subversion using
> the version of cvs2svn on the 1.0.x branch in r8550. I realise that this
> isn't really the latest version but the reason for that will become clearer
> later.
> 
> I've looked through the issue tracker and couldn't see anything
> particularly appropriate.
> 
> The CVS repository is five years old, just under 2GB in size, has 622
> tags/branches and around 50000 files. The repository is a mixture of files
> that have had only one or a handful of revisions and files that have had
> several hundred revisions.
> 
> I've left cvs2svn running for 25 days on an otherwise idle 1GHz P3 with
> python taking around 98% CPU. It doesn't appear to have used much swap. In
> that time it has "added or changed" nearly 130000 revisions and appears to
> have processed around 36000 of the files in the repository.
> 
> So,
> 
> 1. Is this the expected behaviour on a large repository with lots of tags and
> branches?
> 
> 2. Is there anything I can do to the repository to make it faster? Some of
> the tags could probably be removed for example.
> 
> 
> Obviously having to wait over a month for the repository to be converted
> would severely impede our ability to migrate to Subversion :(
> 
> -- 
> Mike Crowe
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
> 

-- 
"Reisen hat keinen Reiz, wenn du nirgendshin heimkehren kannst"
                                                              <Stanislaw Lem>
KBartels@picturesafe.de                  +                 www.picturesafe.de
picturesafe GmbH, Lueerstr. 3, D-30175 Hannover          fon:+49 511 85620 56
++ PGP Key fingerprint  1324 98A8 3BF8 4166 05E1  82D3 E168 6849 6022 5D32 ++
-----BEGIN GEEK CODE BLOCK-----
VERSION: 3.12
GCS d- s: a C++$ UL/S++$ P++ L++ E W-- N w--- !O !M PS+ PE Y+ PGP+ t R@ tv+>-
b+>++ DI++ G e+++ h* y?
------END GEEK CODE BLOCK------

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: [w] cvs2svn: Conversion taking a very long time

Posted by Andreas Kostyrka <an...@kostyrka.org>.
On Mon, Mar 08, 2004 at 04:19:48PM +0100, Erik Huelsmann wrote:
> 
> > I'm just now giving it a try with a newer version of cvs2svn and a local
> > copy of the repository (i.e. without nfs).
> 
> Just to remind everybody again:
> 
> *Never put your repository on an NFS drive*
> 
> The documentation says you shouldn't. So don't. There are *extremely* good
> reasons to tell you this. Disaster will happen if you do. Presumably that is
> not why you would use a version control system.
> 
> bye,
> 
> Erik.
> 
> PS: I know you wrote you are not going to do that anymore. This is for
> everybody else who's reading this too. 
Well, if you would have followed the thread, you would know that the repository
mentioned to be NFS mounted is the CVS input repository for cvs2svn, right?

Andreas

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: [w] cvs2svn: Conversion taking a very long time

Posted by Erik Huelsmann <e....@gmx.net>.
> I'm just now giving it a try with a newer version of cvs2svn and a local
> copy of the repository (i.e. without nfs).

Just to remind everybody again:

*Never put your repository on an NFS drive*

The documentation says you shouldn't. So don't. There are *extremely* good
reasons to tell you this. Disaster will happen if you do. Presumably that is
not why you would use a version control system.

bye,

Erik.

PS: I know you wrote you are not going to do that anymore. This is for
everybody else who's reading this too. 


-- 
+++ NEU bei GMX und erstmalig in Deutschland: TÜV-geprüfter Virenschutz +++
100% Virenerkennung nach Wildlist. Infos: http://www.gmx.net/virenschutz


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: [w] cvs2svn: Conversion taking a very long time

Posted by "Brian W. Fitzpatrick" <fi...@red-bean.com>.
On Mon, 2004-03-08 at 04:11, Kai Bartels wrote:
> Hi Mike, hi *!
> 
> I experienced the same behaviour when trying to convert our local repository.
> It has just about 2G, a lot of files, some of them 5 to 6 years old, some
> with hundreds of revisions. I had the repository nfs-mounted to the machine
> that ran cvs2svn and normally stopped the programm after a few days.
> 
> On the other hands there were reports on this list of a much larger repository
> (about 10G) having been converted in just 10h. The important difference
> maybe that it had much less overall revisions (don't remember exactly, maybe
> 12000).
> 
> I'm just now giving it a try with a newer version of cvs2svn and a local
> copy of the repository (i.e. without nfs).

As I said in my previous mail, this problem still exists.  It's a
scalability issue in cvs2svn that I'm looking into.  I hope to have more
information later today.

-Fitz


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org