Hi Michael,
The author of JamVM is trying to implement this behaviour. It is
strongly in development and probably CPU intensive when the heap is
shrinked because you have to update all pointers in your memory. This is
a somewhat complicated procedure as you have to scan the heap for all
pointers
Hi,I have gotten my answers on IRC, but thought I would also ask here. Some background on my problem.I have a need for a Java application to load a large amount of data. Larger than is normal, I can load it into the JVM my using the correct -Xmx values. The issues is that after I have loaded the
An alternative, is to use a subprocess (shell), to do the large work
and quit afterwards. So your app becomes a wrapping manager that
spawns the subprocess only when needed.
The startup time will be a bit larger, but you can return all the
memory to the OS.
Just to give some option that works
i read the article about kaffe's FAQ.gcstrategy, a paragraph is like this:
...
So, what does Kaffe do to find the sweet spot between not collecting toooften and not using too much memory? It looks at how much memory has beenallocated since the last time a collection happened. If this amount of
be an improvement.
What exactly is the Kaffe garbage collection policy?
See FAQ.gcstrategy.
cheers,
dalibor topic
__
Do you Yahoo!?
Yahoo! Tax Center - forms, calculators, tips, more
http://taxes.yahoo.com
Using Kaffe CVS, it looks like when I call:
System.gc();
System.runFinalization();
It locks the whole VM for the GC. Is there any way to prevent this?
Sun doesn't do this. Also it seems rather slower than Sun.
What exactly is the Kaffe garbage collection policy? Under Sun VMs, it
would appear
