I have a problem trying to limit the agent's memory usage.
As far as I can say, you can limit the memory usage by setting the parameter TEAMCITY_AGENT_MEM_OPTS in the agent's startup script like 'agent.sh'.
I have set it to: TEAMCITY_AGENT_MEM_OPTS="-Xms128m -Xmx256m"
Unfortunately it looks like the agent is ignoring the parameters and I wonder how this is possible, because I thought the parameters define the limitation of the used VM. As I can see the agent is using 680MB, starting with a usage of 180 and increasing the usage until 680.
Under the circumstances the memory usage is limited to 1GB and and it's not possible to start any build configuration at all, because the agent wants to address some more memory to fullfill it's job.
First of all I wonder how the agent is able to grab more memory then I told it to. Second I wonder why the agent adresses additional memory, starting a build configuration.
Neverthless it looks like we got some minimum requirements I can't fullfill with my server and I wonder why...
I can start a tomcat with restricted requirements like 128MB but no build agent... hm... strange...