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 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 -D<name>=<value> JVM property (see below), or you can add TeamCity-specific properties in <TeamCity Data Directory>/config/internal.properties file. The file is Java properties file, to add property put <property name> = <property value> on a separate line. If you do not have the file, just create a new one.
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.
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.
If you run the server using the runAll or teamcity-server scripts or as a Windows service with TeamCity 7.1 and above, you can set the options via the environment variables:
Please make sure the environment variables are set for user you start TeamCity under. You might need to reboot the machine after the environment change for the changes to have effect.
Since TeamCity 7.1 you will need to set environment variables as described in Server is Run Via Shell Script to affect TeamCity run as a service.
For TeamCity 7.0 and previous versions please use the instructions below:
To change heap memory dedicated to the JVM change the "Maximum memory pool" setting.
Skip to end of metadata Go to start of metadata