[JIRA] (JENKINS-56595) Regression: higher than usual CPU usage with 2.164.1
Title: Message Title Shannon Kerr edited a comment on JENKINS-56595 Re: Regression: higher than usual CPU usage with 2.164.1 Pretty sure we are now seeing this or something very similar after our recent upgrade to 2.150.3. We had nothing like this back when we were on 2.138.1. I spread out some of our jobs and multibranch scans to try and mitigate the load. (fyi: running in Jenkins docker container) Of course this doesn't match up with the original reporter who said it wasn't seen until an upgrade from 2.150.3. I'm considering rolling back to 2.138.x at this point as it is disrupting my team. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56595) Regression: higher than usual CPU usage with 2.164.1
Title: Message Title Shannon Kerr commented on JENKINS-56595 Re: Regression: higher than usual CPU usage with 2.164.1 Pretty sure we are now seeing this or something very similar after our recent upgrade to 2.150.3. We had nothing like this back when we were on 2.138.1. I spread out some of our jobs and multibranch scans to try and mitigate the load. (fyi: running in Jenkins docker container) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56595) Regression: higher than usual CPU usage with 2.164.1
Title: Message Title Matthew Hall edited a comment on JENKINS-56595 Re: Regression: higher than usual CPU usage with 2.164.1 This sounds almost exactly like our failed upgrade attempt from 2.121.3 to 2.150.3. We were comfortably running with 4GB heap, and then suddenly the CPU was pegged, UI was slow to unresponsive. Had to revert back to 2.121.3. I did grab 1 threaddump [^threaddump-1552681298816.tdump] before reverting. But if you're looking for root cause changes, may want to include >= 2.121.3. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56595) Regression: higher than usual CPU usage with 2.164.1
Title: Message Title Matthew Hall edited a comment on JENKINS-56595 Re: Regression: higher than usual CPU usage with 2.164.1 This sounds almost exactly like our failed upgrade attempt from 2.121.3 to 2.150.3. We were comfortably running with 4GB heap, and then suddenly the CPU was pegged, UI was slow to unresponsive. Had to revert back to 2.121.3. Sadly, I did not grab any thread dumps at the time 1 threaddump before reverting . But if you're looking for root cause changes, may want to include >= 2.121.3. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56595) Regression: higher than usual CPU usage with 2.164.1
Title: Message Title Matthew Hall updated an issue Jenkins / JENKINS-56595 Regression: higher than usual CPU usage with 2.164.1 Change By: Matthew Hall Attachment: threaddump-1552681298816.tdump Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56595) Regression: higher than usual CPU usage with 2.164.1
Title: Message Title Matthew Hall commented on JENKINS-56595 Re: Regression: higher than usual CPU usage with 2.164.1 This sounds almost exactly like our failed upgrade attempt from 2.121.3 to 2.150.3. We were comfortably running with 4GB heap, and then suddenly the CPU was pegged, UI was slow to unresponsive. Had to revert back to 2.121.3. Sadly, I did not grab any thread dumps at the time. But if you're looking for root cause changes, may want to include >= 2.121.3. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56595) Regression: higher than usual CPU usage with 2.164.1
Title: Message Title Tyler Pickett commented on JENKINS-56595 Re: Regression: higher than usual CPU usage with 2.164.1 After having our Jenkins instance go down 4 times today we rolled back to 2.150.3 and immediately dropped from pegging the 4GB heap limit we have set to comfortably hovering around 2GB. I've collected several thread dumps over the last couple of weeks and will start trying to track down where the issue is. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56595) Regression: higher than usual CPU usage with 2.164.1
Title: Message Title Tyler Pickett updated an issue Jenkins / JENKINS-56595 Regression: higher than usual CPU usage with 2.164.1 Change By: Tyler Pickett Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56595) Regression: higher than usual CPU usage with 2.164.1
Title: Message Title Ryan Taylor commented on JENKINS-56595 Re: Regression: higher than usual CPU usage with 2.164.1 Can also confirm this behavior w/ 2.164.2 as well. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56595) Regression: higher than usual CPU usage with 2.164.1
Title: Message Title Tyler Pickett reopened an issue Additional info has been added, and we're willing to collect additional data as necessary. Jenkins / JENKINS-56595 Regression: higher than usual CPU usage with 2.164.1 Change By: Tyler Pickett Resolution: Incomplete Status: Closed Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56595) Regression: higher than usual CPU usage with 2.164.1
Title: Message Title Gunter Grodotzki commented on JENKINS-56595 Re: Regression: higher than usual CPU usage with 2.164.1 FWIW: we doubled the RAM from 4GB to 8GB instance (with ~50% JVM allocation) - it lasted longer without a crash but ultimately gave in after a couple of days doubled the RAM again, from 8GB to 16GB instance (with ~50% JVM allocation) - so far its lasting So for us that was quite a bump on resource requirements. Doubling is something one might be expecting (also because we were growing with more repositories) - but a 4x bump seemed a bit out of the norm. As long as JVM has enough RAM, the CPU usage is kept relatively low - so for now we are not seeing any issues. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56595) Regression: higher than usual CPU usage with 2.164.1
Title: Message Title Tyler Pickett commented on JENKINS-56595 Re: Regression: higher than usual CPU usage with 2.164.1 I was on vacation last week when Ryan Taylor commented or he would have included a set of thread traces I've attached one that I captured from our instance the week before last. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56595) Regression: higher than usual CPU usage with 2.164.1
Title: Message Title Tyler Pickett updated an issue Jenkins / JENKINS-56595 Regression: higher than usual CPU usage with 2.164.1 Change By: Tyler Pickett Attachment: jenkinshangWithJstack.6.output.tar.gz Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56595) Regression: higher than usual CPU usage with 2.164.1
Title: Message Title Ryan Taylor commented on JENKINS-56595 Re: Regression: higher than usual CPU usage with 2.164.1 I can also confirm this behavior on 2.164.1 Symptoms are: gerrit queue is blocked CPU utilization is all user and pegged to 100% IO drops to nothing The UI was completely locked up ~925 and was restarted at 937. System CPU spike at 933 was inspecting jenkins logs before reboot. This happens every few days so I should be able to capture more information on the next cycle. I assume a thread dump is the best resource to ascertain what's happening here?? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56595) Regression: higher than usual CPU usage with 2.164.1
Title: Message Title Ryan Taylor updated an issue Jenkins / JENKINS-56595 Regression: higher than usual CPU usage with 2.164.1 Change By: Ryan Taylor Attachment: image-2019-04-18-10-06-18-006.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56595) Regression: higher than usual CPU usage with 2.164.1
Title: Message Title Ryan Taylor updated an issue Jenkins / JENKINS-56595 Regression: higher than usual CPU usage with 2.164.1 Change By: Ryan Taylor Attachment: image-2019-04-18-10-06-42-865.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56595) Regression: higher than usual CPU usage with 2.164.1
Title: Message Title Daniel Beck closed an issue as Incomplete This report does not contain nearly enough information for us to investigate further. Jenkins / JENKINS-56595 Regression: higher than usual CPU usage with 2.164.1 Change By: Daniel Beck Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56595) Regression: higher than usual CPU usage with 2.164.1
Title: Message Title Gunter Grodotzki created an issue Jenkins / JENKINS-56595 Regression: higher than usual CPU usage with 2.164.1 Issue Type: Improvement Assignee: Unassigned Attachments: Screenshot 2019-03-18 at 13.36.04.png Components: core Created: 2019-03-18 11:37 Priority: Minor Reporter: Gunter Grodotzki Ever since upgrading to 2.164.1 (current LTS) from 2.150.3, we are experiencing higher than usual CPU usage which also caused a crash: Add Comment
