我应该注意什么关键性能监视器ASP.NET应用程序 [英] What key performance monitors should I watch for ASP.NET application

问题描述

我有每天收到500万请求的网站。在沉重的日子里，页面需要大约10秒返回。我也得到了内存不足异常。我一直在阅读提高从Microsoft .NET应用程序性能和可伸缩性看到有很多指标，我可以看的。我的问题是：

I have a site that receives 5 million request per day. On heavy days, the pages take about 10 seconds to return. I also get out of memory exceptions. I've been reading the Improving .NET Application Performance and Scalability from Microsoft and see there are a lot of metrics I could watch. My question is:

什么是最基本的柜台，我应该看这种意愿：

What are the most basic counters I should be watching that will :

• 告诉我哪里有10秒花了


• 告诉我哪里内存被
  用吗？

这是一个ASP.NET 2.0应用程序与IIS6上运行Win2003的

this is an ASP.NET 2.0 app running on Win2003 with IIS6

推荐答案

由于每天的请求数约为5万条记录，而且越来越多，

Since the number of requests per day is about 5 million records, and growing,

我建议如下：

获取的Fiddler并获取每页请求及其转身时间的数量的读数。做到这一点的，第一个请求和连续请求。你最好应采样数据为5第一请求和采样数据，并从中得出结论之前连续5个请求。

Get Fiddler and get the readings of the number of requests per page and their turn around time. Do this for, first request and Consecutive requests. You should ideally sample the data for 5 first requests and 5 consecutive requests before sampling the data and drawing conclusions from it.

的参数，以从中读取是：

The parameters to read from it are:

• 多少要求每页都
  发生了什么？


• 其中有多少可以
  缓存？


• 的瓶颈资源？

要识别服务器端和身边转的时候，我会建议Ayendes，Rhino.HttpModule或成才，我不记得确切。它给出了一个页面的周转时间在服务器侧

To identify server side turn aroud time, I would suggest Ayendes, Rhino.HttpModule or someting, i don't remember exactly. It gives the turnaround time of a page at the server side.

的参数，以从中读取是：

The parameters to read from it are:

• 它是一个服务器端的问题还是客户端问题？

在这之后，你应该在一个明确的立场至于是否是一个客户端的问题，或者服务器端的问题。有DOEN，那么你可以集中精力的参数。

After this, you should be in a clear position as to whether it is a client side issue or a server side issue. Having doen that, then you can concentrate on the parameters.

在最后一个音符，我想你可以用任何更改您的code做了。因为，你所提出的建议在负载下，周转时间为10秒左右。你看，浏览器无法在要求的时间超过6（+/- 2）资源。因此，负荷下的东西加载Web服务器。模拟的情况，看到了请求计数，团队基础系统，应该帮助。此外， IIS报道下，可以提供在服务器端的请求。看看他们。他们可能会给你一个清晰的画面。

On last note, I think you can do away with any changes to your code. Because, you are suggesting that under load, the turnaround time is around 10 seconds. See, the browser cannot request more than 6(+/- 2) resources at a time. So, something under load is loading your web server. Simulate the situation and see the request count, Team Foundation System, should help. Also, IIS reports , might provide the requests on the server side. Have a look at them. They might give you a clear picture.

希望这会有所帮助。

这篇关于我应该注意什么关键性能监视器ASP.NET应用程序的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！