--- "David A. Desrosiers" <[EMAIL PROTECTED]> wrote: > > > Any ideas? Could it be not enough memory on my > machine, plucker is > > using a very significant amount of memory by this > point. Or is there > > just a limit to how many documents plucker-build > will handle? There > > is a LOT of links between these documents.. Can > there be too many > > links? > > It shouldn't be.. Which version of Python are you > using? How > much RAM and swap is on your machine? Is this > Windows? Or Linux? >
Ram 256, Swap 512, Linux. Plucker-build is using around 220 Megs of memory by the time it dies. Memory doesn't really seem to be an issue but it is a possiblity. > > Anyway I could split the documents into two groups > but I would > > prefer not to do that because of the number of > links between the > > pages. > > This should get easier with Plucker 2.0, with > inter-document > linking, but you're right, it makes sense to keep it > all in one file. > > What were your build parameters passed to > plucker-build? > Not at my home machine so I don't have the exact details, but I am using compression, no color, no images, traverse depth of 4... I think that is all the basic parameters I am using. > I'm building documents on a regular basis with > several hundred > thousand pages, successfully. Granted, it takes a > few _days_ to build > it from scratch, but it does work, and doesn't seem > to crash when > parsing or when loaded on the device. > Is there a way not to build from scratch? Is there some sort of incremental build ability to plucker-build?? Nathan Bullock ===== Visit my website at http://www.nathanbullock.org ______________________________________________________________________ Post your free ad now! http://personals.yahoo.ca _______________________________________________ plucker-list mailing list [email protected] http://lists.rubberchicken.org/mailman/listinfo/plucker-list
