RE: [WDSCI-L] Java memory leak?

["Mike Hockings" <hockings@xxxxxxxxxx>]

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


Mike Hockings, P.Eng.
IBM Canada Ltd. Laboratory
hockings@xxxxxxxxxx



Monday, June 30, 2003 5:30 PM
To: Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
cc:
From: Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>
Subject: RE: [WDSCI-L] Java memory leak?



Mike

I'll try bringing the paging file down again. But Win XP is what has
complained when it was at 512meg. Have 256meg memory.

As far as clearing memory, it's during the run of WDSC that I see the
oscillation. It doesn't seem to hang around

I've got to get another 256 meg out of my boss - heh! Elvis, don't tell
him!

Later

Vern

At 09:33 AM 6/30/2003 -0500, you wrote:
>Couple things, first of all, as a performance thing, I have always
hard-set
>my virtual memory. The reason? Fragmentation it cuts away performance. As
a
>general rule of thumb, set it to twice as much as you have memory. But
that
>can be unrealistic, so in my case I have 512 MB or RAM and 768 MB of VM.
>
>Secondly, I have found that if I run MaxMem
>(http://www.analogx.com/contents/download/system/maxmem.htm) you can more
>easily clean up after WDSc more often. MaxMem is a little (about 1.5 mb
>utility) that runs on your PC and cleans up lost memory. It does a good
job
>of it. Whenever I run WDSc, I run MaxMem.
>
>-----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.


_______________________________________________
This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.