"stop the world"

[Quinnie]

Has anyone heard of "stop of the world" algorithms? They are the
garbage collection algorithms. So java runs the garbage collector
concurrently with the users program (the mutator), though, depending
on the implementation it may suspend the mutator when it does most of
its work to avoid invalid heap data...So can you find an algorithm
(like mark and sweep) and consider how to safely run the collector
concurrently, allowing it to do as much work as possible without
suspending the user processor and
what checks need to be added to the user program and how the collector
should proceed. Any help would be so appreciated.

 

[Ben_]

Sorry, I don't understand the question

Anyway...

JDK 1.4 has support for new algorithms and allows for a "concurrent" mode,
where GC runs all the time (concurrently with the app, hence the name). From
readings ("J2EE vs .NET Application Server Performance Benchmark",
middleware-company.com), I understand that over the course of time under
heavy load, this is more effective than stop-the-world approach, since it
avoids a stop of the processing (and thus avoids filling in the queue of
work of the application while it is stopped) although it takes resources all
the time.