This is the name or IP address with which the process is communicating. If this number is approaching 100% and stays there on a regular basis, you likely have network congestion issues and should add more network capacity.īelow this header information, you will find the following new metric: This metric wraps up all total utilization into a single, easily accessible metric that can help you determine exactly how loaded your network really is. This is a useful data point, but the metric next to it is the one that provides you with really good information. This box shows the current total network utilization in Mbps (megabits per second). In particular, the two boxes next to the heading offer the most impactful, immediately useful metrics. This section of the Resource Monitor window provides more useful troubleshooting information. In Figure A, you can see that the processes named FSEContentScanner64.exe are receiving quite a bit of information from the network. The information in this section isn't particularly useful for troubleshooting except to show you which processes are consuming the most network resources. Average total network activity (in bytes) that the process has generated in the past minute. Average number of bytes per second that the process has received from the network in the past minute. Average number of bytes per second that the process has sent over the network in the past minute. This is useful if you want to use other utilities to manage processes, or you want to easily match up processes with Task Manager. The ID number associated with the process. This is the name of the process that is actively using the disk. You see the name of the executable and a number of performance statistics. This section of the Resource Monitor window shows a list of all of the running processes that are using disk resources. I don't repeat metrics if one type of metric appears in multiple areas, I only list it once. In the sections below, I provide details for each metric. At the right side of the window are a number of graphs, each depicting a key network-based performance metric.
Occupying most of the window is the statistics area, which I'll be explaining in depth. Let's start with an overall look at the console.
( Note: Like all of our other servers, this server is running as a virtual machine under VMware vSphere 4.1.)Ī look at Resource Monitor in Windows Server 2008 R2 (Click the image to enlarge.) As such, this server has significant need for network resources that operate within acceptable boundaries. This figure shows a Resource Monitor view from a production server running Windows Server 2008 R2 and Exchange Server 2010 with all Exchange roles installed. In this installment of my four-part series, I'll discuss the various network-related metrics that you can view with Resource Monitor, explain the graphs you see in the tool, and provide some context around each metric.įor the purposes of this post, we'll use the screenshot in Figure A.
In my TechRepublic series on Microsoft's Resource Monitor tool, I have covered the ways by which you can receive real-time performance metrics related to storage performance and CPU utilization.