Filtered articles: "Performance Monitor"

In the course of the last months, I have been working on a guide through the process of performance analysis. The poster introduces the individual subsystems and provides a step-by-step guide through important metrics and explains how to read the signs of a bottleneck. Read on for an excerpt from the poster.

In the course of the last six months, I have published nine articles about performance monitoring, why it is a crucial task and how the different subsystems of the operating system. To wrap up this series, this article offers an overview of the topics covered in the individual articles as well as a summary of my recommendations.

After a lot of theory about performance monitoring, this article demonstrates how the Windows Performance Monitor can be used to log to a database - even from multiple machines.

Most of you have probably used Performance Monitor before. It allows you to monitor performance metrics (local and remote) in real-time and to log performance data from multiple machines for later analysis. In this article, I will focus on the latter because collecting and analysing performance data from multiple machines is a time consuming task.

In my experience, terminal servers are not properly monitored resulting in administrators not knowing how a farm performs – neither concerning the peak performance nor the trend of the handled load. This leads to an inaccurate and often inadequate sizing of the terminal server environment because only rough estimates arise from such a negligence.

In this series of articles, I'd like to expand on the topic and stressing why monitoring is important for all environment (including terminal servers), what needs to be monitored and how is can be achieved.