Performance is the overall effectiveness of how data moves through the system. Of course, it is important to select the proper hardware (processor, memory, disk system, and network) to satisfy the expected performance goals. Without the proper hardware, hardware bottlenecks can limit the effectiveness of software.
When a component limits performance, that component is known as a bottleneck. What you do to relieve one bottleneck may cause other bottlenecks. For example, one of the most common bottlenecks is the amount of memory a system has. By increasing the memory, you can often increase the overall performance of a system (up to a point). However, when you add more RAM, the RAM needs to be fed more data from the disk, and now the disk becomes the bottleneck or the processor cannot keep up with the additional data. Overall, the system may become faster, but if your performance is still not where you want it to be, you need to then look for the possibility of another bottleneck.
You cannot identify performance problems by just taking a quick look at performance. Instead, you need a baseline, which can be created by analyzing the performance when the system is running normally and within design specifications. Then when a problem occurs, you compare the current performance to your baseline to see what is different. Since performance can also change gradually over time, it is highly recommended that you baseline your server regularly so that you can chart your performance measures and identify trends.
Then, you will know when the server needs to be upgraded or replaced or the workload of the server reduced.There are several tools available with Windows that enable you to analyze performance. They include:
• Task Manager
• Performance Monitor
• Resource Monitor
This lesson is a part of Monitoring and Troubleshooting Servers chapter from 98-365 Windows Server Administration Fundamentals Prep course. More lessons in this chapter are
The Practice tests included in this course are: