Fresh install and server load jumps to over 7
I'm evaluating TeamCity and installed it on a brand new Mac Mini. Once the server and a single agent are started, the load jumps to over 7 or 8:
9:25 up 2 days, 17:56, 4 users, load averages: 8.50 8.07 8.20
If I unload the server via launchctl, the load returns to 1.
top shows the TeamCity Java process taking over 30% of the processor even though it is idle. I have confirmed no builds are running. I do have one task set to build on checkin. I have disabled that trigger but the load stays the same.
I have attached the log and thread dump, any ideas or things I can try to isoalte the problem? I like what I see so far, but will have to resort to Jenkins if I can't fix this.
Attachment(s):
teamcity_logs.tar.gz
Please sign in to leave a comment.
<deleted>
According to logs and thread dump server is mostly idle.
load is over 7 and the box is incredibly sluggish, unless I run this:
sudo launchctl unload ./jetbrains.teamcity.server.plist
at which point load drops to 1.
The java process using 40% cpu constantly is tomcat:
/Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/Home/bin/java -Djava.util.logging.config.file=/Users/admin/TeamCity/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -server -Xmx512m -XX:MaxPermSize=270m -Dlog4j.configuration=file:/Users/admin/TeamCity/bin/../conf/teamcity-server-log4j.xml -Dteamcity_logs=../logs/ -Djava.awt.headless=true -Djava.endorsed.dirs=/Users/admin/TeamCity/endorsed -classpath /Users/admin/TeamCity/bin/bootstrap.jar:/Users/admin/TeamCity/bin/tomcat-juli.jar -Dcatalina.base=/Users/admin/TeamCity -Dcatalina.home=/Users/admin/TeamCity -Djava.io.tmpdir=/Users/admin/TeamCity/temp org.apache.catalina.startup.Bootstrap start
Please take several thread dumps while server is running and using 40% of cpu.
Here are 4 dumps while:
PID COMMAND %CPU TIME #TH #WQ #PORT #MREG MEM RPRVT PURG CMPRS VPRVT VSIZE
89 java 43.6 08:13:59 105 0 254 1247 481M 518M 0B 3952K 690M 3537M
and pid 89 is:
/Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/Home/bin/java -Djava.util.logging.config.file=/Users/admin/TeamCity/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -server -Xmx512m -XX:MaxPermSize=270m -Dlog4j.configuration=file:/Users/admin/TeamCity/bin/../conf/teamcity-server-log4j.xml -Dteamcity_logs=../logs/ -Djava.awt.headless=true -Djava.endorsed.dirs=/Users/admin/TeamCity/endorsed -classpath /Users/admin/TeamCity/bin/bootstrap.jar:/Users/admin/TeamCity/bin/tomcat-juli.jar -Dcatalina.base=/Users/admin/TeamCity -Dcatalina.home=/Users/admin/TeamCity -Djava.io.tmpdir=/Users/admin/TeamCity/temp org.apache.catalina.startup.Bootstrap start
If you'd like me to run VisualVM or some other diagnostics tool I'd be more than happy to.
Thanks for your time,
J.D.
Attachment(s):
dumps.tar.gz
New thread dumps also show that TeamCity does nothing. It is not clear why java.exe shows high CPU usage.
We have similar request in our tracker: http://youtrack.jetbrains.com/issue/TW-34699
I profiled cpu, threads, disk io, etc using Instruments (the XCode profiler) and can share that file if someone there has Instruments and wants to take a look.