{"push_id":2767108199,"size":1,"distinct_size":1,"ref":"refs/heads/iss-jenkins-run","head":"a505ac7a59e5fc88f9fdfdadf85fe5cf05720379","before":"68e19d771c43acf2c228245020de8449c05a2ca7","commits":[{"sha":"a505ac7a59e5fc88f9fdfdadf85fe5cf05720379","author":{"name":"hriships","email":"0fdcda9c954cc007cec533eab0fd2408d4eefbbc@gmail.com"},"message":"Optimize Jenkins performance to fix slow booting issue\n\nJenkins works very slow during first boot and unidling phase. It turns\nout that JVM Garbage Collector (GC) threads occupies most of CPU aggressively\nto avail more heap memory because initial heap size is very less. Hence this\nlong pause of GC freeze the Jenkins application to execute.\nThis patch tweaks few JVM GC parameters to set enough heap memory (Xms is 50% of Xmx) that\npreventing GC to kick in on Jenkins boot. Also reduced the number of GC threads to\nprevent it from using all processor cores.\n\nFixes issue: https://github.com/openshiftio/openshift.io/issues/3956\n\nRelated issue: https://github.com/openshiftio/openshift.io/issues/3861","distinct":true,"url":"https://api.github.com/repos/hrishin/fabric8-tenant-jenkins/commits/a505ac7a59e5fc88f9fdfdadf85fe5cf05720379"}]}
{"actor":{"display_login":"hrishin"}}