Re: Improving Excel generation performance through calling Java

Unfortunately that will not happen since you are still invoking from
RPG. I could be wrong, but I have a feeling when you use RPG to invoke
Java NO objects will ever be GC'ed unless explicitly told to or the
JVM ends. That includes objects created via other objects. I don't
know for sure, but I think that RPG is using JNI (Java Native
Interface) to invoke the methods, which is probably why they don't get
GC'ed.

Here is a link to the 5.3 reference, I'm sure it hasn't changed much,
on how to use JNI to invoke garbage collection.
http://tinyurl.com/yeox6y
ref:
https://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=/books_web/c0925075175.htm

I have not personally used the JNI calls to do GC. I usually just
invoke RPG from Java instead of the other way around. Unfortunately in
your case I don't think it would really work, so you have to call Java
from RPG. If you use the JNI to clean up objects just make sure you
don't prematurely clean them up. Part of the problem is POI in general
is fairly memory intensive. After all it is Horrible SpreadSheet
Format :-)

--
James R. Perkins



On Mon, Mar 22, 2010 at 08:23, <darren@xxxxxxxxx> wrote:

As to the performance, I had hoped that since I was having the java method
create the Row type object, rather than having RPG create the row object,
that garbage collection would take care of it better than RPG doing the
free local reference thing.

--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.