This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: GC_enable_incremental()

From: DHollenbeck <dick at softplc dot com>
To: "Boehm, Hans" <hans dot boehm at hp dot com>
Cc: java at gcc dot gnu dot org
Date: Thu, 09 Sep 2004 11:47:57 -0500
Subject: Re: GC_enable_incremental()
References: <B27561804CF1BE4F8943BB2CB29E18EA062CF3@hplextmp.hpl.hp.com>

:

3) I'm not sure it would help that much, since most of the GC time in your context (tiny heap, I presume?) is probably spent tracing the huge root set, and that will still happen with the world stopped. There are plans to fix this, but it hasn't happened.

I think most of the 57 msecs might be coming from the mechanism used to "stop the world", not the scanning of the root set. Is this possible?

I get the same results with a 4 megabyte heap as with a 32 mb heap, both lead to intermittent 57 msec delays.

Dick

Follow-Ups:
- Re: GC_enable_incremental()
  - From: Andrew Haley

References:
- RE: GC_enable_incremental()
  - From: Boehm, Hans

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]