> One of the problems with Java Garbage Collection is that it halts > other work in the JVM for the duration of the GC (because you're > moving stuff around, you can't have people trying to use it). While GC > has improved over time to reduce the amount of objects handled during > each scan, my understanding is that it still suspends other JVM work. > Part of GC can exploit additional CPUs when you activate the parallel > GC (not the default).
Thats an implementation flaw (maybe flaw is a strong word given its a hard problem). Schoeberl and Puffitsch for one produced a mostly non blocking garbage collection for Java which only blocks the threads it needs and only at the points it has to. Rather useful for multi-threaded systems. Alan ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
