Re: Java batch job performance issue

It is difficult to offer any advice without knowing more details about the
application. How is CLLE ³initializing² java? How is RPGLE ³calling² the
java process? What is the java processing doing?

Java heap will continue to grow until the garbage collector kicks in and
it will clean objects that are no longer referenced. Make sure you are
not holding references to objects after they are no longer needed.

--
Marshall Dunbar



-----Original Message-----
From: <Steinmetz>, Paul <PSteinmetz@xxxxxxxxxx>
Reply-To: Java Programming on and around the IBM i <java400-l@xxxxxxxxxxxx>
Date: Thursday, June 18, 2015 at 9:09 AM
To: "'java400-l@xxxxxxxxxxxx'" <java400-l@xxxxxxxxxxxx>
Subject: Java batch job performance issue

We are testing our first Java application.
V7R1 JDK 6.0 32 bit.
Sending 1,000,000 single requests in batch to a remote server.

This was a stress test.

Job was constantly taking 50% CPU, very little disk.

When started, job was doing 25 api calls per second, now it is 3 after
740,000 after 18 hours.
The heap size started at 30MB and is now roughly 600MB.

The job did not error, simply slowed down.
We cancelled at this point.

The process is called from an RPGLE pgm, Java is initialized in CLLE pgm.

Any thoughts?

Thank You
_____
Paul Steinmetz
IBM i Systems Administrator

Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071

610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home

psteinmetz@xxxxxxxxxx
http://www.pencor.com/

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