Re: jenkins consumes lot of memory

[Adam PAPAI]

It has been fixed in the version 1.485. What's new in 1.485 (2012/10/07) Build records are now lazy loaded, resulting in a reduced startup time (issue 8754) We're using 1.510 and upgrading every week if it worth to upgrade (checking the changelog first). How long do you keep the build history? Do you have artifacts? do you delete them periodically?   Viktor Konnyu April 15, 2013 10:35 AM From which version is this implemented? We are using LTS 1.480.3 -Djava.awt.headless=true -Xms1g -Xmx6g -XX:MaxPermSize=512M -XX:+UseParallelGC -XX:ParallelGCThreads=16 -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -verbose:gc -Djava.net.preferIPv4Stack=true -XX:+HeapDumpOnOutOfMemoryError Java version is Java(TM) SE Runtime Environment (build 1.7.0_17-b02) Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode) Thanks, Viktor On 2013.04.15. 10:17, Adam PAPAI wrote: -- 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/groups/opt_out.     Adam PAPAI April 15, 2013 10:17 AM What version are you using? The newer version's read the build history on demand. And you can control the memory usage as well via parameters like: JAVA_ARGS="-Djava.awt.headless=true -Xms1g -Xmx10g -XX:MaxPermSize=1G -XX:+UseParNewGC" This is a very optimal setup for us. ~100 nodes, ~200 jobs with thousands of tests (heavy loaded jenkins cluster running 0-24 and building continuously) -- 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/groups/opt_out.     Viktor Konnyu April 15, 2013 10:14 AM Hi, Jenkins seems to consume an awful lot of memory. As I understand it is due to keeping build logs in memory for one. My question is what other factors influence jenkins' memory consumption and what can I do about it? Also, is there a way to flush the memory on demand or force a GC without restarting the server? Thanks for your answers! Viktor -- Adam PAPAI E-mail: w...@wooh.hu Phone: +3630 3355735 Web: http://www.wooh.hu -- 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/groups/opt_out.