This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: GCJ and Boehm GC "Incremental Collection"
- From: "Craig A. Vanderborgh" <craigv at voxware dot com>
- To: java at gcc dot gnu dot org
- Cc: Hans dot Boehm at hp dot com
- Date: Tue, 06 Dec 2005 12:35:56 -0500
- Subject: Re: GCJ and Boehm GC "Incremental Collection"
Hello Again,
Another idea has occurred to us, one that could reduce our need for
"incremental GC" in the short run.
What we have been trying to do for several years now is to use certain
memory heuristics to "anticipate" our application's need for GC, and
then to request a GC ourselves as soon as possible before the collector
would decide to do a "world-stopped" collection on its own. This could
allow us to perform GC at a "less disruptive" time, for example at a
time that would not pause audio prompt playback in our application.
The trouble is that our attempts to come up with a predictive criterion
for when GC will happen have all failed quite spectacularly. The
closest we've come is by using
Runtime.freeMemory()/Runtime.totalMemory() to compute a "% Java memory
available" and use a comparison to some constant to decide whether we
should request GC.
Needless to say, this kind of thing does not really work. So the
question is - How can we find out whether Boehm GC is "thinking about"
doing a collection before it actually decides to do one? I'm going to
go read the Boehm code and see what I can figure out, but any input from
Dr. Boehm and others how to achieve this in an appropriate way would be
greatly appreciated.
Thanks in advance,
craig vanderborgh
voxware incorporated