In continuation to last question - My site goes slow and stops access certain services externally if we check the Process monitor we see that it is normally due to the ‘w3p.exe’ process – which is the background process for running the website – it regularly reaches 99/100% - killing the process/restarting the WebPublishing service reolves tis – my webhost says this can only be due to bad coding ....can someone comment on this ??…
继续上一个问题 - 如果我们检查进程监视器,我的网站运行缓慢并停止访问外部某些服务我们发现它通常是由于'w3p.exe'进程 - 这是运行网站的后台进程 - 它定期达到99/100% - 杀死进程/重新启动WebPublishing服务reis tis - 我的webhost说这只能是由于编码错误....有人可以评论这个吗?...
Wanted to know any monitoring software which traces IIS & freely available ...
想知道跟踪IIS和免费提供的任何监控软件......
2 个解决方案
#1
If you are using Asp.Net then you can use the built in Asp.Net tracing to find out things like the size of your viewstate and the where the time is spent while rendering a page. There are various ways of enabling this depending on what your needs are: see http://authors.aspalliance.com/aspxtreme/webapps/tracefunctionality.aspx
如果您使用的是Asp.Net,那么您可以使用内置的Asp.Net跟踪来查找视图状态的大小以及渲染页面时花费的时间。根据您的需求,有多种方法可以实现此目的:请参阅http://authors.aspalliance.com/aspxtreme/webapps/tracefunctionality.aspx
#2
99% CPU is not going to occur if you have an inefficient page or two. 99% CPU utilization happens when you have a bug. If it does not happen on your local server, but only in the hosted environment, then you will have to resort to the old school detective approaches. Tracing, removing portions of code, and so on - til you find the source of the problem.
如果您的页面效率低下,则不会发生99%的CPU。当您遇到错误时,会发生99%的CPU利用率。如果它不在您的本地服务器上发生,但仅在托管环境中发生,那么您将不得不求助于旧学校的侦探方法。跟踪,删除部分代码等等 - 直到找到问题的根源。
#1
If you are using Asp.Net then you can use the built in Asp.Net tracing to find out things like the size of your viewstate and the where the time is spent while rendering a page. There are various ways of enabling this depending on what your needs are: see http://authors.aspalliance.com/aspxtreme/webapps/tracefunctionality.aspx
如果您使用的是Asp.Net,那么您可以使用内置的Asp.Net跟踪来查找视图状态的大小以及渲染页面时花费的时间。根据您的需求,有多种方法可以实现此目的:请参阅http://authors.aspalliance.com/aspxtreme/webapps/tracefunctionality.aspx
#2
99% CPU is not going to occur if you have an inefficient page or two. 99% CPU utilization happens when you have a bug. If it does not happen on your local server, but only in the hosted environment, then you will have to resort to the old school detective approaches. Tracing, removing portions of code, and so on - til you find the source of the problem.
如果您的页面效率低下,则不会发生99%的CPU。当您遇到错误时,会发生99%的CPU利用率。如果它不在您的本地服务器上发生,但仅在托管环境中发生,那么您将不得不求助于旧学校的侦探方法。跟踪,删除部分代码等等 - 直到找到问题的根源。