You are viewing the documentation of TeamCity 9.x, which is not the most recently released version of TeamCity.
View this page in TeamCity 2018.x documentation or refer to the listing to choose the documentation corresponding to your TeamCity version.

Skip to end of metadata
Go to start of metadata

The Performance Monitor build feature allows you to get the statistics on the CPU, disk and memory usage during a build run on a build agent. The Performance Monitor supports Windows, Linux, Solaris and MacOS X operating systems. Note that the performance monitor reports the load of the whole operating system. It will not report proper results if you have more than one agent running on the same host, or an agent and a server installed on the same machine.



If you run your build agent as a Windows service, the user starting the agent must be a member of the Performance Monitor Users group to be able to monitor performance metrics. Users can be added to the group via the lusrmgr.msc command.

When enabled, each build has an additional tab called PerfMon on the build results page, where this statistics is presented as a graph. The CPU usage shows the average CPU load during the build, the Disk and Memory usage values are relative to the total disk and memory available on the agent machine. Clicking on a point in the graph displays the corresponding value (CPU in  screenshot below) as well as the build log with the highlighted fragment for the selected time.


For example, from the picture below it is clear that at some point the CPU and Disk usage is very low. This lasts for about 20 minutes. It seems that the tests executing at this time need some investigation, probably, most of the time they are blocked on some lock or wait for some event:



  • No labels