JPluck has extremely high memory usage when doing complex plucks. This is to the point where it generates java Out of memory exceptions and can't get everything:
In particular, class.java.lang.RuntimeException: java.sql.SQLException: out of memory E.g, I'm trying to pluck the low-bandwidth version of the CIA World Factbook: http://www.cia.gov/cia/publications/factbook/countrylisting.html Link Depth: 1, include full-size images, multi-image (500x500) exclude http://www\.cia\.gov/cia/publications/factbook/index\.html The Taskmanager reports JPluckX.exe memory usage peaks around 168 MB, (I'm running Win2k on a machine with 256 MB of RAM). As the pluck runs, it generates the exceptions more frequently, and spidering happens more slowly. Eventually, the spidering stops entirely. JPluckX remains responsive to clicks: cancelling or switching between the Progress or the Log still work. However, CPU utilization goes to 0%. I've also tried it with on WinXP with 512 MB of RAM. It doesn't exhibit the OOM exceptions, and it eventually finish running the spidering process, but it stops at 0% when it reaches the "Generating document" stage. -alan -- Alan Hoyle - [EMAIL PROTECTED] - http://www.alanhoyle.com/ "I don't want the world, I just want your half." -TMBG Get Horizontal, Play Ultimate. _______________________________________________ plucker-list mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-list
