|You are viewing documentation of TeamCity 6.5.x, which is not the most recent released version of TeamCity. Please refer to the listing to choose another version.|
Various aspects of TeamCity behavior can be customized through a set options passed on TeamCity server start. These options fall into two categories: affecting Java Virtual Machine (JVM) and affecting TeamCity behavior.
In this section:
TeamCity internal properties
TeamCity has some properties that are not exposed to UI and are meant for debug use only. If you need to set such a property (e.g. asked by TeamCity support), you can set it either as
If you need to pass additional JVM options to a TeamCity server (e.g. -D options mentioned at Reporting Issues or any non-"-D" options like -X...), the approach will depend on the way the server is run. If you run the server using Windows service, please refer to #TeamCity Server is Run as Windows Service, if you are using
For general notes on the memory settings, please refer to Setting Up Memory settings for TeamCity Server.
You will need to restart the server for the changes to take effect.
Server is Run Via Shell Script
If you run the server using the
TeamCity Server is Run as Windows Service
To edit JVM server options run Tomcat's service configuration editor by executing the command
To change heap memory dedicated to the JVM change the "Maximum memory pool" setting.