Book Image

Learning Continuous Integration with TeamCity

Book Image

Learning Continuous Integration with TeamCity

Overview of this book

Table of Contents (19 chapters)
Learning Continuous Integration with TeamCity
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Tweaking the TeamCity JVM


TeamCity is a JVM application, and its memory usage can be tweaked like any other JVM application. For large production uses, the defaults may not work, and hence a few tweaks in the heap and PermGen memory allocated to TeamCity may be needed.

Much of the tweaking can be done by passing the appropriate flags, -Xmx (heap space) and -XX:MaxPermSize (PermGen space), to the JVM.

There is no one size fits all solutions here. The exact values to be used will vary from installation to installation based on usage, number of build configurations and projects, and so on. It is recommended that you use a minimum of 750m for the heap space (-Xmx750m) and 270m for the PermGen space (-XX:MaxPermSize=270m) and then raise it from there as needed.

These flags can be passed to the JVM used to run the server using the TEAMCITY_SERVER_MEM_OPTS environment variable.

Note

If TeamCity runs with a 32-bit JVM (the default through a Windows installer), it is limited to 1.2 GB of heap memory....