Dear,
Being "rookie" with Fossil, I'm starting some tests to migrate some of our
subversion repositories to Fossil and have a better test bed to learn fossil
before eventually deciding on a switch.
I have successfully migrated a rather small (and secondary) repository with
only some hundreds of revisions.
So decided to run the same test on our main one.
The dump file (out of svnadmin) is about 12.6 GB, which I guess is not that
large and holds about 15600 revisions to a rather large number of files (>27000
files, >1300 folders/subfolders). It has the usual structure of trunk,
branches, tags, with few branches and few tags.
The svnadmin dump ran quickly (matter of <10 minutes with option -M 512).
But the fossil import turned short after about 3200 revisions (and about 10
minutes too) as such:
C:\Develop\Fossil>fossil import --svn integral.fossil integral.dump
Importing SVN revision: 3203
Fossil internal error: out of memory
What could I do from here to overcome this or, before that, better identify
what might be the reason for "out of memory"?
This is fossil version 2.4 [a0001dcf57] 2017-11-03 09:29:29 UTC.
The computer I'm running it on for now is a VM with 4 GB RAM which could be
easily reconfigured for much more, even if only temporarily, but as I
understand the fossil.exe I have downloaded from fossil-scm.org is a 32-bits
process, so should not benefit much.
Should I see to build my own copy of fossil, as a 64-bits process first and
simply retry?
Or are there other paths to walk first?
--
Best Regards, Meilleures salutations, Met vriendelijke groeten,
Olivier Mascia
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
