Performance Troubleshooting with Windows Resource Monitor Microsoft Sql Server


articles >> performance tuning >> Performance Troubleshooting with Windows Resource Monitor …

There is a handy little tool in Windows Server 2008 R2 that can help system administrators and DBAs better diagnose server performance issues. It’s called the Resource Monitor. Resource Monitor is also present in Windows Server 2008, but its interface is not as good as that in R2 and it does not offer the same features present in the latest version.

One thing administrators do when investigating an unresponsive or slow server is to bring up the Task Manager and have a quick look at the performance tab. It gives an overall status of the CPU and the RAM in the machine. Looking at the graphs, one can quickly see which of these resources are being locked up. Usually the next step is to go to the Processes tab and sort the list of processes by that resource. Looking through the sorted list then gives a starting point for troubleshooting the relevant application.

Resource monitor goes one step further than the Task Manager and offers some extra features:

Resource monitor gives a broad overview of the status of the server as well as look at the utilisation of CPU, RAM, Disk and Network resources individually.Ability to filter out individual processes and see how that process is utilising these four resources. Task Manager does not give you this functionality.Ability to look through the wait chain of an unresponsive program and see what other processes it’s depending on.Ability to find what process or service is accessing a file or registry key or DLL: this is much like the information SysInternals gives you.Resource monitor offers a better insight into server memory usage.

Now one thing to remember is that Resource Monitor should be used what it’s meant for: initial diagnosis. It does not replace other performance monitoring tools like Perfmon. For example, if you find SQL Server is using up 99% of CPU, you would want to check if it’s affecting other three resources as well. You will then probably want to open up the “Top Queries by Average CPU Time” or “Activity – Top Sessions” report in SQL Server Management Studio.

There are three ways you can bring up the Resource Monitor. You can go to Start menu and choose All programs > Accessories and then click on the Resource Monitor program under System Tools folder. Alternately, you can type “resmon” in the search text box and press enter. Finally, you can click on the “Resource Monitor…” button in the Performance tab of the Windows Task Manager (see figure below).

The Resource Monitor Interface

As the program starts, you will see Resource Monitor has five tabs. The first one – called Overview – gives you just that – an overall resource usage pattern of the server. The tab is divided into multiple sections or “tables”. The first table lists the complete list of processes running in the machine and it’s called the “key table”. If you navigate to the other four tabs, you will see a key table at the top of each of them. Each of these key tables show the list of processes accessing the resource associated with that tab. The key table in the Overview tab shows the list of all process running in the machine.

The column names of the key tables will vary between different tabs, but there are two columns that remain constant: Image and PID. Image is the name of the actual executable running the process and PID is the Process ID, a unique identification number for the process.

Directly below the key table are the detailed tables. The detailed tables provide additional information related to the processes. Again, their content will vary between different tabs.

var idcomments_acct = ’62089e20c30196b091933230f42f0718′;var idcomments_post_id;var idcomments_post_url;

View the original article here

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>