× 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.



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.


_______________________________________________ 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.

_______________________________________________
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 ...

Replies:

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.