|
I have had similar issues with my use of the HSSF API's (I haven't used
Scott's) and the only way I was able to improve performance and memory
consumption was to put Java entirely in charge of it's own garbage
collection. Initially I was calling the Java methods directly from RPG, but
to fix the long run times I instead coded the entire process in Java and ran
it in a batch job. The process went from around 30 minutes to 3 minutes,
and I believe it had to do with the efficiency (or lack of) between RPG and
Java.
What would be cool is if somebody would come up with a layered approach that
would allow the RPG programmer to write cell contents to a DB2 table, then
invoke a Java process to go through all the values in DB2 and apply them to
a spreadsheet. It actually wouldn't be that hard to write now that I think
about it - very similar in nature to my RPG Chart Engine which you can check
out if you want (free and open source:
http://mowyourlawn.com/RPGChartEngine.html)
HTH,
Aaron Bartell
http://mowyourlawn.com
http://mowyourlawn.com/blog/
On Tue, Mar 2, 2010 at 8:40 AM,<darren@xxxxxxxxx> wrote:
I'm using the HSSF POI API's, via Scott Klement's service programs, to
generate a rather large spreadsheet. It has two tabs with about 20K rows,
and I've come to accept that it will take a little while to run. However,
as I watch my job, I see 'Temporary Storage Used' go as high as 600MB.
I've studied the service programs, as well as my own code, to make sure
that I'm freeing local references to objects whenever I'm done with them.
Is this normal behavior for these API's with a larger spreadsheet, or do I
have a memory leak somewhere?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.