Yes I can: - [1, 2] The pauseless collector also has the highly desirable side-benefit of producing improved memory locality. This happens because the algorith

Yes I can: - [1, 2] The pauseless collector also has the highly desirable side-benefit of producing improved memory locality. This happens because the algorithm works by attempting to relocate groups of tightly-coupled objects into regions of adjacent memory, providing excellent paging and cache locality properties for those objects. This can also benefit highly multithreaded applications that operate on distinct sets of object data. If you read the whitepaper on Azul[3] you will get a glimpse of how things got a lot more involved. And all of this gets a lot more complicated when programmming for multiple cores[4]. But not everybody is using the Erlang VM or Sun's JVM (HotSpot). The point is generic: don't assume things are on your platform by watching other platforms. Don't use old data to guide your search, no matter how brilliant/famous the author is. [1]http://java.sun.com/products/hotspot/docs/whitepaper/Java_HotSpot_WP_Final_4_30_01.html http://java.sun.com/products/hotspot/docs/whitepaper/Java_Ho... [2]http://java.sun.com/docs/books/performance/1st_edition/html/JPAppHotspot.fm.html http://java.sun.com/docs/books/performance/1st_edition/html/... [3]http://www.infoq.com/articles/azul_gc_in_detail http://www.infoq.com/articles/azul_gc_in_detail [4]http://www.javacodegeeks.com/2011/04/erlang-vs-java-memory-architecture.html http://www.javacodegeeks.com/2011/04/erlang-vs-java-memory-a...