We might need to know, language wise, how the Java application is
structured. If you're using the JNI toolset to use something like RPG
calling Java methods, then its very easy to generate object references that
the GC doesn't know it can clean up. If that's how you're doing it, then
you have to specifically tell the JVM that you're done with an object,
because the garbage collector is operating at a different level than your
program.
There is a JAVA400-L list.
From: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 06/17/2015 02:55 PM
Subject: Java batch job performance issue
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
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.
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 Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.