To do so, you could use the excellent PAL tool ( ) which gives a predefined list of counters to monitor based on the selected product. Now you know how to define your key values, you need to know how to collect them. Once you've determined the threshold limit before degradation and the threshold where everything is working well, you just must collect the performance counters and you'll get your key values. By doing a progressive load test, you should be able to identify when the application performance is degraded. Thus, it's essential to define those key values before putting your application in production. However, as every web-application and hence every IIS Server, will behave differently depending on what will be executed, obviously the threshold for which performance will be impacted will vary a lot. One regular question posed to our team deals with the performance counters set-up to ensure IIS and ASP.Net application(s) are working properly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |