TeamCity Memory Monitor

TeamCity server checks available memory on a regular basis and warns if amount of available memory is too low. There are several warning types reported:

Low pool memory

Is reported when memory usage in a single memory pool is more than 90% after garbage collection. High server activity could cause such memory usage.

Low PermGen memory

Is reported when more than 95% of PermGen memory pool is used. Usually high PermGen usage is not a problem as it mostly isn't used for data. However PermGen overflow could crash TeamCity server so it's recommended to increase PermGen size. Contact with TeamCity team if the warning is still showing after pool increase.

Low total memory

Is reported when more than 90% of total memory is in use for the last 5 minutes and more than 20% of CPU resources are being spent on garbage collection. Lasting memory lack could result in performance degradation and server unstability as well.

Heavy GC overload

Is reported when memory cleaning takes in average more than 50% of CPU resources. It usually means really heavy problems with memory resulting in high performance degradation.

Customization

Several Configuring TeamCity Server Startup Properties could be used to customize the Monitor:

teamCity.memoryUsageMonitor.poolNames sets up pool names to track. Case sensitive comma separated string is accepted

teamCity.memoryUsageMonitor.warningThreshold allows to set up minimal warning threshold. Affects all tracked memory pools except PermGen

teamCity.memoryUsageMonitor[<Pool name>].warningThreshold could be used to modify single memory pool threshold (including PermGen). Spaces should be escaped or changed to '_' signs

teamCity.memoryUsageMonitor.gcWarningThreshold allows to set up allowed percentage of resources to spent for cleaning the memory