2014-08-25 14:11 GMT+02:00 Vincent Massol <vmas...@gmail.com>: > > Some fresh news: > > * Today we’ve seen CPU usage at 800% for the jenkins master process. Note > that we don’t do any build on the jenkins master, they’re all executed on > slave agents. > * Going to http://ci.xwiki.org/threadDump was showing a "Caused by: > java.lang.OutOfMemoryError: GC overhead limit exceeded” error > * We checked permgen and it was used at 99.72% > * We were using -Xmx1024m -XX:MaxPermSize=384m on jenkins master and > we’ve just increased the permgen to 512MB even though we don’t really > understand why it would require so much permgen on jenkins master (for > jenkins agents we’re using: -Xmx1536m -XX:MaxPermSize=512m -Xms512m and > they seem ok). Ayn idea? > * If we still have permgen issues with 512MB on master, we’ll take a heap > dump and share it somewhere if we can’t find out the problem (likely since > we don’t know the jenkins’s source code). >
Weird indeed. Sure it depends on the volume and the jobs you run, but we have -Xmx1024 -XX:MaxPermSize=256m on a ~15 slaves/~500+ actives jobs without memory issue (but still a bit behind for the master's version ATM: Jenkins 1.559). Maybe try to disable the maximum plugins you can temporarily? At least that should help you know if the issue is in core or more likely in one of the installed plugins? My 2 cents -- Baptiste -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
