什么perfmon计数器可用于识别ASP.NET瓶颈？

Question

Given the chart here, what should I be looking at to identify the bottleneck? As you can see, requests are averaging nearly 14 seconds under load and the bulk of that time is attributed to the CLR in New Relic's profiling data. In the performance breakdown for a particular page, it attributes the bulk of the time to the WebTransaction/.aspx page.

Answer 1

I see that the database is readed also (the orange) and this is seams that one of all pages have delay the rest of pages because of the lock that session make on the pages.

you can read also : Replacing ASP.Net's session entirely

My suggestion is totally remove the session calls and if this is not possible, find an other way to save them somewhere in database by your self.

Actually in my pages I have made all three possible options. 1. I call the page with out session. 2 I have made totally custom session that are values connected to the user cookie, and last 3. I have made threads that are run away from the session and they make calculations on background, when they finish I show the results.

In some cases the calculations are done on iframe that call a page without session and there later I show the results.

Answer 2

在Pro版本中，您可以使用“事务跟踪”，它可以帮助确定问题的确切位置。