Hi guys, I'd like to propose that we explicitly set the Java args for the Jenkins packages to use either Concurrent Mark Sweep or G1 as the default GC algorithm.
The reason for this is that Jenkins is generally used as a long-running server process, and large stop-the-world GC pauses can pose a problem for stability and user experience. The default Java GC algorithm (ParallelGC) is tuned to optimize throughput at the expense of potentially multi-second major GC pauses with large heaps, which is obviously not a good fit for this case. This is why Oracle is moving to G1 as the default as of Java 9. I would suggest either CMS or G1 make good defaults for normal Jenkins users, because they greatly reduce average and maximum GC pause times. Thoughts? Regards, Sam Van Oort -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/c009a299-1b23-4cb8-97ef-c6718fc279e1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
