-
Enhancement
-
Resolution: Won't Fix
-
P4
-
None
-
1.3.0
-
x86
-
windows_nt
Name: skT88420 Date: 09/03/99
For my application (soft real-time control with Java), it is extremely important that my application not get locked out for long periods of time. So I was looking forward to trying HotSpot, perhaps with incremental garbage collection. However, I still notice that my app is am frequently locked out for over 150ms (and sometimes up to 1 second!!) while garbage collection occurs. When I run in verbose GC mode, delays during "Full GC" are explicitly displayed on the screen, and my app confirms that certain critical operations were delayed by that amount of time.
Can you explain what is "Full GC" as printed by your "verbose GC" Java command-line switch? Is there any hope that incremental garbage collection will become truly incremental, and not lock out my application for long periods of time? Running Microsoft's VM, I can run for many days without being locked out for more than 60ms...do you have any idea why their stop-and-copy GC seems to be faster than your incremental GC?
(Review ID: 94852)
======================================================================
- relates to
-
JDK-4459148 Incremental GC has delays upto 13 seconds under jdk1.2.2 / 1.3.1 / 1.4.0-b64
-
- Closed
-