[JIRA] (JENKINS-15619) Huge Files sync eat all the Java memory and make very long gc
Rob Petti commented on JENKINS-15619 Huge Files sync eat all the Java memory and make very long gc That is only one of several changes that have been made since 1.1.13 in order to address memory issues. Can I ask why you won't simply upgrade to the latest? 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
[JIRA] (JENKINS-15619) Huge Files sync eat all the Java memory and make very long gc
sh j commented on JENKINS-15619 Huge Files sync eat all the Java memory and make very long gc added limit* for number of files per changelist in order to avoid OOM on large changes (issue #13109) We applied this change our plugin 1.1.13 but it have same problems. Our job always used -f option. P4 plugin keep below sync log in heap when a Job syncing sources. p4 sync -f //aaa//////.java#head ... is it correct? we run 100+ build Simultaneously and all job start syncing a lot of file. If out heap is full before syncing complete than is it possible the thrown out the log immediately? 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
[JIRA] (JENKINS-15619) Huge Files sync eat all the Java memory and make very long gc
sh j commented on JENKINS-15619 Huge Files sync eat all the Java memory and make very long gc Thank you very much. I will check it!!! 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
[JIRA] (JENKINS-15619) Huge Files sync eat all the Java memory and make very long gc
Rob Petti resolved JENKINS-15619 as Cannot Reproduce Huge Files sync eat all the Java memory and make very long gc Change By: Rob Petti (25/Oct/12 4:27 AM) Status: Open Resolved Resolution: Cannot Reproduce 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
[JIRA] (JENKINS-15619) Huge Files sync eat all the Java memory and make very long gc
Rob Petti commented on JENKINS-15619 Huge Files sync eat all the Java memory and make very long gc Wow, that's really old... This was fixed back in 1.3.13, I believe, but I highly recommend updating to the latest. 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
[JIRA] (JENKINS-15619) Huge Files sync eat all the Java memory and make very long gc
sh j commented on JENKINS-15619 Huge Files sync eat all the Java memory and make very long gc we use 1.1.13 now. which version was this problem solved from ? 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
[JIRA] (JENKINS-15619) Huge Files sync eat all the Java memory and make very long gc
Rob Petti assigned JENKINS-15619 to Rob Petti Huge Files sync eat all the Java memory and make very long gc Change By: Rob Petti (25/Oct/12 2:39 AM) Assignee: Rob Petti 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
[JIRA] (JENKINS-15619) Huge Files sync eat all the Java memory and make very long gc
Rob Petti commented on JENKINS-15619 Huge Files sync eat all the Java memory and make very long gc It's already limited, and most of the log is thrown out immediately rather than stored for that very reason. What version of the perforce plugin are you using? I've synced millions of files at once without any issues. 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
[JIRA] (JENKINS-15619) Huge Files sync eat all the Java memory and make very long gc
sh j created JENKINS-15619 Huge Files sync eat all the Java memory and make very long gc Issue Type: Bug Assignee: Unassigned Components: perforce Created: 25/Oct/12 1:41 AM Description: With really huge Files sync the p4 plugin can run out of java heap space and it make long gc. At least it looks like the reason for memory problems would be huge file sync logs when file syncing. An example case: Start 50+ builds same time ( a sync include 40+ files ) Our 200G heap exhausted in 3 min and make very long gc. Maybe there should be an option to limit the amount of sync log that p4 plugin keep while syncing? Now we are limiting simultaneously over 20 p4 sync manually. plz help me. Project: Jenkins Priority: Major Reporter: sh j 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
[JIRA] (JENKINS-15619) Huge Files sync eat all the Java memory and make very long gc
sh j updated JENKINS-15619 Huge Files sync eat all the Java memory and make very long gc Change By: sh j (25/Oct/12 1:42 AM) Description: With really huge Files sync the p4 plugin can run out of java heap space and it make long gc. At least it looks like the reason for memory problems would be huge file sync logs when file syncing. An example case:Start 50+ builds same time ( a sync include 40+ files )Our 200G heap exhausted in 3 min and make very long gc.Maybe there should be an option to limit the amount of sync log that p4 plugin keep while syncing?Now we are limiting simultaneously over 20 p4 sync manually. plz help me. 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
