what about Azul's Zing JVM?

[Vitaly Davidovich]

As a gross oversimplification their GC is concurrent to mutator (java)
threads but is mostly pauseless (they still pause at times but only very
briefly) because they use read barriers.   This means that if a mutator
thread reads memory that's been relocated, they trap this condition at read
time, fix up the pointer (mutator does this itself), and continue on.  Last
I heard this approach required azul's os support for bulk in/mapping of
pagetable entries, and required a Linux patch for x86 to do the same (but
it wasn't accepted into mainline kernel).

What's interesting is whether hotspot has any plans to do something similar?
On Nov 28, 2011 4:27 AM, "Li Li" <fancyerii at gmail.com> wrote:

> hi everybody,
>     I read an article today about Azul's Zing JVM. It is said that this
> jvm is pauseless.
>     In my application, our machine is about 48GB and about 25GB memory is
> given to jvm(by -Xmx). But it will occasionally pause 1-2 seconds.
>     So when I saw this, I want to know whether it's so good as they say.
> And I googled and found a related question in stackoverflow:
> http://stackoverflow.com/questions/4491260/explanation-of-azuls-pauseless-garbage-collector
>     after reading, I am still confusing. Anyone would give more detail
> explanations about it? thanks
>
> _______________________________________________
> hotspot-gc-use mailing list
> hotspot-gc-use at openjdk.java.net
> http://mail.openjdk.java.net/mailman/listinfo/hotspot-gc-use
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/hotspot-gc-dev/attachments/20111128/e968e276/attachment.htm>
-------------- next part --------------
_______________________________________________
hotspot-gc-use mailing list
hotspot-gc-use at openjdk.java.net
http://mail.openjdk.java.net/mailman/listinfo/hotspot-gc-use