Re: [fossil-users] Import --svn "internal error: out of memory"
Am 27.12.2017 um 16:23 schrieb Warren Young: > On Dec 27, 2017, at 6:49 AM, Stephan Beal wrote: >> To quote the Oracle: >> >> "[Because] You didn't come here to make the choice, you've already made it. >> You're here to try to understand why you made it.” > Also, “Realize that there is no spoon. There is only fork.” > Nerds, all of you :-) ... I like it here ;-) ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Import --svn "internal error: out of memory"
On Dec 27, 2017, at 6:49 AM, Stephan Beal wrote: > > To quote the Oracle: > > "[Because] You didn't come here to make the choice, you've already made it. > You're here to try to understand why you made it.” Also, “Realize that there is no spoon. There is only fork.” ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Import --svn "internal error: out of memory"
On Wed, Dec 27, 2017 at 12:44 PM, Olivier Mascia wrote: > 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. > To quote the Oracle: "[Because] You didn't come here to make the choice, you've already made it. You're here to try to understand why you made it." Welcome aboard! :) -- - stephan beal http://wanderinghorse.net/home/stephan/ "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Import --svn "internal error: out of memory"
> Le 27 déc. 2017 à 13:22, Olivier Mascia a écrit : > >> 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? > > Considering that the dump file out of svnadmin is probably 'portable' across > platforms, and that the fossil pre-built binary for Mac is logically 64 bits, > I moved the dump file to my MacBook Pro where I'm currently re-running the > import. > > So far it has imported past the point where it failed on Windows (did about > 1/3 of the revisions for now). > > $ fossil import --svn integral.fossil integral.dump > Importing SVN revision: 6393 > > I'll report wether it went OK up the end or not and wether I seem to have > issues using fossil (32 bits) on Windows on such a repository afterwards. Success. $ fossil import --svn integral.fossil integral.dump Importing SVN revision: 15678 Done! Rebuilding repository meta-data... 100.0% complete... Vacuuming... ok And in between, while import running on Mac, I built a 64 bits binary on Windows, out of the latest trunk obtained by cloning the fossil repository, which went flawlessly (at least apparently, but I have confidence) and I now have there: This is fossil version 2.5 [f4a9df4dd0] 2017-12-23 04:21:41 UTC Compiled on Dec 27 2017 13:45:17 using msc-19.11 (64-bit) I think I should be covered for my further tests and discoveries, even though this is now latest unreleased trunk code. :) -- 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
Re: [fossil-users] Import --svn "internal error: out of memory"
> Le 27 déc. 2017 à 12:44, Olivier Mascia a écrit : > > 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? Considering that the dump file out of svnadmin is probably 'portable' across platforms, and that the fossil pre-built binary for Mac is logically 64 bits, I moved the dump file to my MacBook Pro where I'm currently re-running the import. So far it has imported past the point where it failed on Windows (did about 1/3 of the revisions for now). $ fossil import --svn integral.fossil integral.dump Importing SVN revision: 6393 I'll report wether it went OK up the end or not and wether I seem to have issues using fossil (32 bits) on Windows on such a repository afterwards. -- 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
[fossil-users] Import --svn "internal error: out of memory"
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
