Decrease the Garbage Collector Threshold

We've been running into problems with running out of PermGen memory using TeamCity 9.0.1.  We've managed to solve most of them using settings recommend in the docs, but we've noticed the Garbage Collector is still not being initiated to free space until the PermGen memory is already maxed out.  Is there a recommended way to decrease the threshold so the garbage collector will kick in around 85%?  The lost productivity of having to recover the entire service is much worse than any performance hit we'd take from running the gc more often.  I'm posting a screenshot of our diagnostics to help make the situation more clear.



Attachment(s):
tc_mem.JPG
5 comments
Comment actions Permalink

Hi Samuel,

What memory settings do you use for TeamCity now?

0
Comment actions Permalink

64 bit JVM

-Xms2000m -Xmx3000m -XX:MaxPermSize=540m

0
Comment actions Permalink

Do you have any custom plugins installed? What version of JVM do you use? What OS?
Also I'd try to install the most recent version of TeamCity.

0
Comment actions Permalink

The only extra plugins we have installed are the HipChat Notifier, and a Python Runner.

java version "1.7.0_75"
Ubuntu 14.04.1 LTS (GNU/Linux 3.13.0-32-generic x86_64)

Upgrading to 9.0.2 is on the list, but it won't be happening immediately.

0
Comment actions Permalink

Please try adding additional JVM argument to TeamCity startup script: -verbose:class
In this case it will start logging loaded and unloaded classes in console. Please try to collect this data for some time, then attach this log here.

BTW, 9.0.3 is already available.

0

Please sign in to leave a comment.