Summary: XP memory management when running large Java app.s is very
shoddy. Buy more RAM as Windows paging does not work as it should. Any
time you hit above the RAM you go to a crawl. At home I have an
optimized disk subsystem on my mainboard and 8MB caching on my disk so
its faster but XP still mismanaged memory. A hole a mile wide for Linux
to run through!
Is this something to do with the GC and Windows memory manager? My
guess is the JVM classloader loads up .class and then writes image of
it somewhere so the memory is write and not written through so the RAM
is eaten. Rather than working from the disk image. Is this correct? If
so, classloader fix should not be incredibly tough. Still, pagefile
should end up with it all so increasing the pagefile *should* help.
Right?
My configs:
XP, WebLogic Workshop, WebLogic Server:
1 GB is minimum but broders on unbearable. We have 2.8Dell OptiPlex
GX270 which has hyper- threading and they suck. Kill all and only run
essentials. Have to log out and back in periodically to get 100MB back
from OS. Have to kill WorkShop after any builds and restart to get mem
back. Sometimes have to restart WLS too to get memory back.
Home: built up a 1GB machine with abit mb with nforce disk technology
and 128MB video card. Much faster than the DELL. Still goofy once all
memory is used up. Do Eclipse, MySQL, and Tomcat there with ease. Plus
running some video editting, PVR, or other stuff at same time. Only
ripping seems to hang me up.
Notebook: XP, SUSE, 1.6GHz Celeron, 764MB. This is just a very slow
machine. Like my DELL PC at work, Compaq went cheap on the disk and
disk subsystem. Even the RAM is used for the video rather than real
video memory - something that slipped by me when I bought it as I was
under time pressure due to the scammer Kelly from the City of Industry,
CA at IOSys/whatever he calls it now who never shipped my order AFAICT!
TimJowers
