Page Loading Extremely Slow, Intermittent Timeouts, Errors in logs
I'm not sure where to begin. I've been having lots of problems with extreme slowness ever since upgrading to 4.0. Loading any page takes a very long time. If a build is failing and I click on the link for that build, it can take minutes for the page to load. Builds are timing out sometimes after all of the tests are finished running. I have looked at the various logs and see errors but I don't know what they are all about.
For one build agent that times out, I get the following in the build logs before it times out:
In the teamcity-server.log I am constantly getting the error:
jetbrains.buildServer.SERVER - Failed to load finished build instance: Cannot find build promotion with ID 8187
In the build agent's error.log, I see the following, repeatedly:
[2009-01-07 15:54:47,158] WARN - org.apache.xmlrpc.XmlRpc - java.net.SocketTimeoutException: Read timed out
Haven't seen anything particularly interesting in the other logs.
I am currently using the internal database, have 3 build agents and the following environment variables set:
- TEAMCITY_AGENT_MEM_OPTS=-Xms512m -Xmx1024m -XX:MaxPermSize=256m
- TEAMCITY_SERVER_MEM_OPTS=-Xms512m -Xmx1024m -XX:MaxPermSize=256m
Help!
Please sign in to leave a comment.
Right now all of the build agents and the build server are on the same solaris box. I did get someone to install a mysql database so I just have to find the time to switch to it. I'll report back after I get that done. It probably won't be this week but maybe I'll catch a break.
Thanks again for your help.
--Melody
Build agents running on the same box where server is installed can really slowdown the server. Builds running on the agents eat CPU and can actively use disk, at the same time server performance highly depends on disk speed (especially this is true for HSQLDB). If it is not possible to move agents to other servers, probably it is possible to use different disks for agents and for .BuildServer?
As of last check there were no other servers available but there may be some new hardware available soon. We weren't having these problems with v3 so it just wasn't a priority. I'll see what's coming available and see if we can get the server separated from the agents.