[JIRA] (OVIRT-1756) configure jenkins.ovirt.org to G1 garbage collector

12 Nov 2017


      This is a multi-part message in MIME format...

------------=_1510506540-17733-147
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


     [ https://ovirt-jira.atlassian.net/browse/OVIRT-1756?page=com.atlassian.jira.p... ]

Barak Korren updated OVIRT-1756:
--------------------------------
    Epic Link: OVIRT-403
...
configure jenkins.ovirt.org to G1 garbage collector
---------------------------------------------------
Key: OVIRT-1756
                URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1756
            Project: oVirt - virtualization made easy
         Issue Type: By-EMAIL
         Components: oVirt CI
           Reporter: rgolanbb
           Assignee: infra
I noticed jenkins process cpu consumption going over 100% and stalling the
web handlers. The io wait is not a problem nor mem.
What I suspect is going on is tons of GC and GC pressure given that 12GB
heap and fairly nice amount of users and requests.
What we can do is to configure the gc logging to see if that is really GC
pauses really and to move to using the G1 garbage collector.
See this post from cloudbees on the move to G1 collector
https://www.cloudbees.com/blog/joining-big-leagues-tuning-jenkins-gc-respons...
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100070)

------------=_1510506540-17733-147
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1756?page=com.atlassian.jira.p... ]</pre>
<h3>Barak Korren updated OVIRT-1756:</h3>
<pre>Epic Link: OVIRT-403</pre>
<blockquote><h3>configure jenkins.ovirt.org to G1 garbage collector</h3>
<pre>     Key: OVIRT-1756
     URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1756
 Project: oVirt - virtualization made easy
         Issue Type: By-EMAIL
         Components: oVirt CI
Reporter: rgolanbb
Assignee: infra</pre>
<p>I noticed jenkins process cpu consumption going over 100% and stalling the web handlers. The io wait is not a problem nor mem. What I suspect is going on is tons of GC and GC pressure given that 12GB heap and fairly nice amount of users and requests. What we can do is to configure the gc logging to see if that is really GC pauses really and to move to using the G1 garbage collector. See this post from cloudbees on the move to G1 collector <a href="https://www.cloudbees.com/blog/joining-big-leagues-tuning-jenkins-gc-responsiveness-and-stability">https://www.cloudbees.com/blog/joining-big-leagues-tuning-jenkins-gc-responsiveness-and-stability</a></p></blockquote>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)</p>

<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyzY..." alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/>
</body></html>

------------=_1510506540-17733-147--

Barak Korren (oVirt JIRA)

tags

participants (1)