这里给出的图表，我应该怎么看，以确定的瓶颈？正如你所看到的，请求平均负载下近14秒钟，大部分的时间是归因于新文物的分析数据的CLR。在某个特定页面的性能故障，它的属性大部分的时间来WebTransaction / .aspx页面中。

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.

推荐答案

我看到，该数据库也（橙色）readed这是接缝，所有页面的一个有延迟的，因为锁的会话页面的其余部分使在页面上。

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.

您还可以阅读： 更换ASP.Net的会议完全

我的建议是完全删除会议要求，如果这是不可能的，找一个其他的方式在某处保存在数据库中你的自我。

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.

其实在我的网页我已做了所有三种可能的选择。 1.我打电话与出会话页面。 2我已经完全自定义会话连接到用户cookie的值，和最后3我做了那些逃离会话线程和他们进行计算的背景，当他们完成我显示结果。

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.

在某些情况下，计算上的iframe进行调用页面没有会话，还有后来我显示结果。

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