<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hello,<div><br></div><div><div><div>On 27 Aug 2014, at 12:34, Giovanni Giorgi <<a href="mailto:jj@gioorgi.com">jj@gioorgi.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span style="font-family: SourceCodePro-Regular; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;">About garbage collection: Java is very strong in this area. Also the new G1, a low latency GC works very well</span></blockquote></div><br></div><div>Maybe G1 is has been designed to reduce GUI freeze but we had a serious issue in production due to G1 along with one Java library lately.</div><div><br></div><div>In the nutshell, the system went crazy but consuming all CPU resource. As the result, Java dies but it also killed all Erlang nodes running on same HW. I would skip our internal Java - Erlang ping-pong but investigation shown that one of 3rd party library was not compatible with G1, it cause huge dirty heaps and garbage collection was instant operation… So, we swap GC and had fun with 800 tunables :-)</div><div><br></div><div>and I would disagree that Java is very string in GC area, Erlang GC is many time superior in terms of latency. It has it own problems but they rare impact the overall system stability</div><div><br></div><div>Best Regards, </div><div>Dmitry</div></body></html>