× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



For performance with WDSC I think that there is no better solution than
adding more memory (IMHO).   In my experience setting the JVM max size to
greater than real memory is an extreme performance hit (this is on a laptop
with a slow disk) because of the paging that it causes.

Here are some jems of wisdom from Barry about setting up for best
performance....

http://www7b.software.ibm.com/wsdd/library/techarticles/0204_searle/searle.html#setup

Kind regards,

Mike


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



Monday, June 30, 2003 10:45 AM
To: "'Websphere Development Studio Client for iSeries'"
<wdsci-l@xxxxxxxxxxxx>
cc:
From: "Wills, Mike N. (TC)" <MNWills@xxxxxxxxxxxxxx>
Subject: RE: [WDSCI-L] Java memory leak?



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.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.