The
Windows Performance Monitor is a
general purpose performance monitoring tool which can be used to monitor
performance of windows and web applications. The tool can be customized to
monitor specific parameters like Memory Utilization, CPU Utilization, Disk I/O
etc of the system at any given point of time or over a specific time interval.
In this post we shall see on how to use the Performance Monitor tool monitor performance of an Asp.Net application based on the number of requests processed per second. This is just one of the counters, there a hundreds of such counters which can be used to measure various parameters of an Asp.Net application.
To measure the number of request processed by Asp.Net per second, use the following steps to configure the Performance Counter.
1. Open the Performance Monitor tool.
2. In the left navigation tree, expand Monitoring Tools, and then click Performance Monitor
3. The default counter starts running.
4. Delete the default counter by clicking the Delete (x) icon in the toolbar.
5. Click on the Add (+) icon to add a new Counter
6. In the popup select the Local Computer or the computer to be monitored
7. In the categories list, open the ASP.Net Applications and select the counter Requests/Sec.
8. Under Instances list select “All Instances”
9. Click the Add button to add the selected parameters to the new Counter
10. Click OK to close the settings window, and the new counter starts running automatically.
In this post we shall see on how to use the Performance Monitor tool monitor performance of an Asp.Net application based on the number of requests processed per second. This is just one of the counters, there a hundreds of such counters which can be used to measure various parameters of an Asp.Net application.
To measure the number of request processed by Asp.Net per second, use the following steps to configure the Performance Counter.
1. Open the Performance Monitor tool.
2. In the left navigation tree, expand Monitoring Tools, and then click Performance Monitor
3. The default counter starts running.
4. Delete the default counter by clicking the Delete (x) icon in the toolbar.
5. Click on the Add (+) icon to add a new Counter
6. In the popup select the Local Computer or the computer to be monitored
7. In the categories list, open the ASP.Net Applications and select the counter Requests/Sec.
8. Under Instances list select “All Instances”
9. Click the Add button to add the selected parameters to the new Counter
10. Click OK to close the settings window, and the new counter starts running automatically.
Allow
the counter to run, and start working on the application. In this case we are
trying to measure the number of requests sent to the server over a period of
time. Once you start using the application you can start seeing spiked in the
Graph, this indicates that asp.net has started receiving requests from the
clients.
This
report is very useful to determine load on a server, if the requests are high throughout
or over a major period of time, then this is an indication to decide on adding
hardware or scaling up the system configuration to meets the increasing number
of requests.
When the application is handled by multiple cluster/load-balanced servers, running the counter on all the nodes, helps us determine the load on each of the server nodes, again this reports can be used to decide on adding more nodes to the cluster to improve performance.
When the application is handled by multiple cluster/load-balanced servers, running the counter on all the nodes, helps us determine the load on each of the server nodes, again this reports can be used to decide on adding more nodes to the cluster to improve performance.
No comments:
Post a Comment