The max. amount of RAM was already increased from 128Mb to 256Mb and the image handling was optimized so that images are cached to disk rather than kept in memory. This is basically all I'm going to do about the memory usage. There's no point in spending any more effort, my plate is full already. (I have food spilling all over the floor, so to speak.) Even so, Sunrise still converts typical documents just fine.
Both Sunrise and JPluck are simply not suitable for converting super-size documents because of the wasteful use of memory in the core JPluck library, which I talked about in the other thread. (For the sake of comparison, the JPluck EXE launcher only allocates a maximum of 128Mb.)
As for a solution: you can launch Sunrise from the command-line and thus pass the maximum amount of memory to use:
java -Xmx1024m -cp .;build\sunrise.jar;lib\commons-logging.jar;lib\hsqldbmain.jar;lib\jetty.jar;lib\n ekohtml.jar;lib\servlet.jar;lib\smalljs.jar;lib\sp inner.jar;lib\swt.jar;lib\xercesMinimal.jar com.distantchord.sunrise.Desktop
where -Xmx####m is max. amount of megabytes that the VM is allowed to allocate. (Naturally, everything should go on one line.)
Starting multiple instances this way will fail. (The EXE launcher creates a mutex to prevent this.) If you're on Windows XP you'll lose the "rounded" look-and-feel as the EXE contains a manifest for enabling it.
I just looked on plkr.org and your Perl spider isn't even available, at least not from there. The only thing Perl thing I could find were some 4-year-old files in
CVS.
Seriously, I think it's about time you made it public. If it's really so great, it deserves a release.
Anyway, I'm not interested in a competition in who has the best Plucker tool. Sunrise simply is what it is, take it or leave it.