RE: [WDSCI-L] Java memory leak?

["Mike Hockings" <hockings@xxxxxxxxxx>]

What!! No WebFacing, heresy, I say, heresy!

If all you are doing is RSE kinda stuff, editing and looking at '400 
libraries, then you might be OK with 512 M, though still more would be 
better of course (if your boss is asking that is).

Yes, must be, collecting garbage and putting in a heap, or is it the heap. 
 Don't know it's been really quiet here today and I'm going a wee bit 
crazy ;-)   Seriously I expect that any Java just running is creating 
objects and they build up before the GC kicks in.   If you look at the 
link that I posted a bit earlier it talks about how to set the GC limits 
so that you could have it run a bit more often.  That might knock the 
peaks down a bit.  You would have to experiment to find the settings that 
give your machine the best results.

Kind regards,

Mike

P.S. It's Canada day here on July 1st (well there too I guess) so don't 
expect a lot of response from us then.  We'll be out playing in the snow 
and setting off fireworks.  Phil might be online though as I don't expect 
he'll be out on his skis quite yet ;-)


Mike Hockings, P.Eng.
WebSphere Development Tools for AS/400  -  CODE/Designer & WebFacing !
IBM Canada Ltd. Laboratory 
hockings@xxxxxxxxxx 





Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
06/30/2003 07:07 PM
Please respond to Websphere Development Studio Client for iSeries 

 
        To:     Websphere Development Studio Client for iSeries 
<wdsci-l@xxxxxxxxxxxx>
        cc: 
        Subject:        RE: [WDSCI-L] Java memory leak?

 

Thanks, Mike

The most I can get through DELL is 512 meg - a Dell 4800. We'll see.

If I read the article correctly, the default maximum for Java heap (max 
memory?) is half of physical memory - that'd be 128 meg and seems to fit 
the behavior - it seems to go up to around 120 or more, then back down to 
something, 64? So if I leave things alone, does this work?

BTW, all the work I do is editing CL, CMD, and C source from the 400. No 
Java, no Webfacing, none of those intensive things. I could do everything 
in CODE and be very happy.

It still disturbs me that it grows while it is minimized, while I am not 
doing anything. Must be collecting garbage?

Vern

At 06:34 PM 6/30/2003 -0400, you wrote:
>If you can, you would get better performance with WDSC (4 or 5) if you 
went
>to 1G of memory.   256M is simply not enough, 512 is slow, 1 G is OK.  In
>my experience anyway.  If you need to run it on a machine with only 256M
>then you probably want to close all other applications to free up as much
>real memory as possible.
>
>It's probably fine that the Windows swapper be large but you don't want 
to
>set the max memory of the JVM for WDSC to be larger than real memory.
>
>Kind regards,
>
>Mike
>
>
>
> >
> >-----Original Message-----
> >From: Vern Hamberg
> >
> >Just got the version 5 upgrade. I am on Win XP SP1, 256 meg memory. 
Java
> >version is
> >
> >C:\Documents and Settings\Vern>java -version
> >java version "1.3.0"
> >Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0)
> >Classic VM (build 1.3.0, J2RE 1.3.0 IBM build cn130-20020124 (JIT 
enabled:
> >jitc)
> >
> >Task Manager memory usage shows javaw's allocation growing constantly.
>This
> >is while WDSC is running. When I got back to my machine, it was at 
64meg
> >(WDSC minimized), when I restored WDSC it jumped to 120meg and kept 
going.
> >When I minimized WDSC again, down to 2meg, then grew very quickly
>(minutes)
> >to 120meg, then a little while later down to 70meg or so, then grew 
again.
> >
> >Is this normal? Is this garbage collection? I also had a message that
> >virtual memory was running out - XP was adjusting it. Right now it says
>the
> >commit charge is 952 meg with 399 meg committed.