> > 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. > > If it is non-blocking, why would one be concerned about the elapsed > time of GC and what would be the interest of having multiple threads > working in parallel on GC. Or would you really have allocation rates > so high that a single thread could not keep with it? Or should we > conclude that current implementations don't deploy such algorithms?
Note the "mostly" - architecturally java on current hardware needs soem blocking to do certain compaction tasks, but the blocking can be minimised and localised. 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/
