Submitted JEP 189: Shenandoah: An Ultra-Low-Pause-Time Garbage Collector

Simone Bordet simone.bordet at gmail.com
Sat May 14 11:49:26 UTC 2016


Ciao,

On Fri, May 13, 2016 at 4:02 PM, Christine Flood <chf at redhat.com> wrote:
> OK, I've put together a pdf document which summarizes our changes.
>
> I'm happy to go into more detail or answer questions.

At the end of the section "Source Code Changes":

"We have measured their execution cost and have found so significant
overheap when running G1 with and without Shenandoah code."

I'm not sure I understand "found so significant overheap", can you
please expand ?

I read that Brooks pointers have not be often be considered because of
the high cost associated with indirection, but a blog from Roman
(https://rkennke.wordpress.com/2016/02/08/shenandoah-performance/)
seems to show that perhaps this belief should be re-evaluated.

Do you have any further insights that you can share on the good
performance of Shenandoah ?

Thanks !

-- 
Simone Bordet
http://bordet.blogspot.com
---
Finally, no matter how good the architecture and design are,
to deliver bug-free software with optimal performance and reliability,
the implementation technique must be flawless.   Victoria Livschitz



More information about the hotspot-gc-dev mailing list