I can suppose a memory leak caused by new objects created and not
deleted...
I am not the ultimate java specialist but if you create an object with and
instruction like
Object x = new Object();
and do not delete it by an instruction like
x=null;
the x object will be deleted by the internal garbage collector after some
time depending on your GC and VM settings..
this could explain your heap size... (a java object takes at minimum 16
bytes)
I would then suggest to explicitly delete/nullify objects..
Paul
From: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 17/06/2015 20:56
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/
midrange.com
