I think there are two main ways in which Plucker falls short of iSilo (and
some ways in which it is better). The first is the 32K limit. The
second, and more serious, is that parser is, I think, less robust. I've
just converted a 100mb collection of texts with iSilo, but both JPluck2
and PyPlucker ran out of memory. (JPluck2 ran out first with an error
message; PyPlucker started thrashing later, but then was no longer making
any progress.) This was on a 224mb machine, so theoretically there should
have been enough space to hold the whole collection in memory. (I ran
PyPlucker once under Windows, and a second time under Linux, so it's not
an OS issue.)
Does PyPlucker maybe keep all the texts in RAM rather than saving them to
a cache? Can this be fixed?
Alex
--
Dr. Alexander R. Pruss || e-mail: [EMAIL PROTECTED]
Philosophy Department || online papers and home page:
Georgetown University || www.georgetown.edu/faculty/ap85
Washington, DC 20057 ||
U.S.A. ||
-----------------------------------------------------------------------------
"Philosophiam discimus non ut tantum sciamus, sed ut boni efficiamur."
- Paul of Worczyn (1424)
_______________________________________________
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
