[JIRA] [all-changes] (JENKINS-17349) CPU on master node keeps increasing and never come down
evernat resolved JENKINS-17349 as Fixed CPU on master node keeps increasing and never come down resolving this issue as fixed, since the related issue JENKINS-14362 was resolved as fixed (for Jenkins v1.520) Change By: evernat (21/Jun/13 11:57 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [all-changes] (JENKINS-17349) CPU on master node keeps increasing and never come down
Yinghua Wang commented on JENKINS-17349 CPU on master node keeps increasing and never come down I have the same issue on the latest 1.517. The master CPU usage keeps increasing to 400% until restart the Jenkins service - it drops to 95%. No such problem on 1.502 before I upgrade to 1.517. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [all-changes] (JENKINS-17349) CPU on master node keeps increasing and never come down
evernat commented on JENKINS-17349 CPU on master node keeps increasing and never come down This issue may be related to the JENKINS-14362 issue, where Jesse Glick has submitted in the comments, a patched Jenkins 1.513 for anyone to test. See https://issues.jenkins-ci.org/browse/JENKINS-14362?focusedCommentId=179526page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-179526 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [all-changes] (JENKINS-17349) CPU on master node keeps increasing and never come down
Martin-Louis Bright commented on JENKINS-17349 CPU on master node keeps increasing and never come down I have this issue with 1.515 as well. Forgive my ignorance, but how is limiting the memory with "-Xmx2048m -XX:MaxPermSize=512m" going to limit CPU usage? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [all-changes] (JENKINS-17349) CPU on master node keeps increasing and never come down
Daniel Pinyol commented on JENKINS-17349 CPU on master node keeps increasing and never come down We have this issue too with 1.514 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [all-changes] (JENKINS-17349) CPU on master node keeps increasing and never come down
Roger Myung commented on JENKINS-17349 CPU on master node keeps increasing and never come down We have this issue too. Two flags that we've tried unsuccessfully are --handlerCountMax=100 --handlerCountMaxIdle=20 I'm curious if there is a performance difference between Winstone and Tomcat. I was planning on moving to Tomcat to try to separate the web server process from the core Jenkins process. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [all-changes] (JENKINS-17349) CPU on master node keeps increasing and never come down
Michael Tharp commented on JENKINS-17349 CPU on master node keeps increasing and never come down I'm seeing this on 1.511 but have not yet tried adjusting launch options. Each "step" is another thread consuming 100% CPU. The one thread I have stuck right now is also in java.util.zip.Deflater.deflateBytes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [all-changes] (JENKINS-17349) CPU on master node keeps increasing and never come down
evernat commented on JENKINS-17349 CPU on master node keeps increasing and never come down Ok for MaxPermSize. At the end of the first report (cpu = 31%), there were 4 "RequestHandler..." threads with very high cpu usage. They were executing "java.util.zip.Deflater.deflateBytes(Native Method)". At the end of the second report (cpu = 6%), there was 1 "RequestHandlerThread2944" thread with high cpu usage. It was executing "java.util.zip.Deflater.deflateBytes(Native Method)". If you look at the threads at the bottom of the report today, is "RequestHandlerThread2944" still there and executing "java.util.zip.Deflater.deflateBytes(Native Method)"? Are there other threads like this doing the same thing today? If yes, what are the stack-traces of these threads? You may click on "Dump threads as text" below the threads table. Note that you can kill those threads with the red button at the right of the table, it may decrease the cpu used. But that's not a long term solution. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [all-changes] (JENKINS-17349) CPU on master node keeps increasing and never come down
sharon xia commented on JENKINS-17349 CPU on master node keeps increasing and never come down After the JVM arguments changed to -Xmx2048m -XX:MaxPermSize=512m, there is still a CPU increase after several days run. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [all-changes] (JENKINS-17349) CPU on master node keeps increasing and never come down
sharon xia updated JENKINS-17349 CPU on master node keeps increasing and never come down JavaMelody pdf after memory inceased. Change By: sharon xia (08/Apr/13 5:14 AM) Attachment: JavaMelody__CNRDGPS_4_8_13.pdf This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [all-changes] (JENKINS-17349) CPU on master node keeps increasing and never come down
sharon xia updated JENKINS-17349 CPU on master node keeps increasing and never come down In the middle of the picture, the CPU decreased dramatically after a system restart to let new parameters take effect. However, after about one week, the cpu increased to ~= 6%. Change By: sharon xia (08/Apr/13 5:18 AM) Attachment: CPUinceasepic.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
