----- Original Message ---- From: Toby Johnson <[EMAIL PROTECTED]> To: Vss2Svn Users <vss2svn-users@lists.pumacode.org> Sent: Friday, April 20, 2007 3:13:02 PM Subject: Re: OOM issues: large files AND many commits in SS databases
> You may want to try running the old 0.11.0-alpha1 version[1] to at least > test this theory, since the sanity checker was much less ambitious and > therefore kept much less state data at that point. I gave this revision a try... it's still using too much RAM. This revision died just before processing an SVN ADD of a ~220MB file. (Windows XP SP2). SVN HEAD died some time shortly after processing the same file. (IIRC) Something just occured to me... This rev of vss2svn doesn't have the patch for ticket #25 applied to it, does it? I'll grab the source for this revision (I assume that it's tagged as 0.10.0-a1 in SVN), apply my patch to DumpFile.pm and see what happens. Also, I haven't yet had time to make any progress on pushing out SanityChecker to a database. Thanks for your input and assistance, -Kenneth __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ vss2svn-users mailing list Project homepage: http://www.pumacode.org/projects/vss2svn/ Subscribe/Unsubscribe/Admin: http://lists.pumacode.org/mailman/listinfo/vss2svn-users-lists.pumacode.org Mailing list web interface (with searchable archives): http://dir.gmane.org/gmane.comp.version-control.subversion.vss2svn.user
