Re:Why Java Now Rocks More Than Ever: Part 1 – The Java Comp...
by pron on Monday October 07, 2013 @10:31AM
(#6508454)
You are right, but newer Java versions have what is called "GC ergonomics": you simply define either a throughput or a latency goal, and the JVM tries to dynamically change the settings until to achieve your goals.
[ Parent
| on HN ]
Re:Why Java Now Rocks More Than Ever: Part 1 – The Java Comp...
by fizx on Monday October 07, 2013 @11:17AM
(#6508738)
Some applications can be pathological, in which case you are better off setting lower-level flags. For example, Lucene both churns through tons of short-lived strings and tries to maintain caches of large arrays. The memory/gc optimizer handles this very poorly.
Between modern Java tending to move caches to unmanaged memory-mapped regions as libraries mature, and the potential of G1 as a concurrent compacting collector, we're on the cusp of not having to worry about any of this anymore.