Moving to G1GC - An Experience Report by Kirk Pepperdine
1,125 views · Published 27 March 2018 · 56:58 · Indexed 21 October 2026
Channel: Devoxx · 2018 · Science & Technology
With the release of Java 9, our beloved mostly CMS collector was depreciated and G1GC replaced the Parallel collector as the default. The hype surrounding this massive change that the G1GC is the best collector… ever. Make no mistake about it, G1GC will be much much easier to tune. So, is this real or is it #fakenews. In this session we will explore the reality by looking experiences moving applications from CMS to G1GC in real production environments. The implications aren’t simply about performance. A sub-optimally tuned collector will increase your companies operating cost by 10-20%. We will also explore results from benchmarks that expose potential pain points. and offer some suggestions on what actions can offer some relief.
More from this channel
-
32:13
Writing Groovy AST Transformations: Getting Practical in an hour! by Baruch Sadogursky
-
25:58
TweetWallFX - Behind the Scenes by Sven Reimers
-
29:44
Second generation "workflow managers" for big data by Alex Van Boxel
-
29:13
Secrets are secrets. Please maintain them as secrets by Alex Soto
-
2:13:40
JavaScript build pipelines with Gulp.js by Stefan Baumgartner
-
2:04:09
Powerful Metaprogramming Techniques With Groovy by Jeff Brown
-
2:38:32
Distributed Machine Learning 101 using Apache Spark from a Browser by Xavier Tordoir/Andy Petrella
-
2:36:21
Caching 101: Caching on the JVM (and beyond) by Alex Snaps/Louis Jacomet