my site is ASP.NET,C#, .net 4, using Umbraco 4, IIS 7.5 it has been working great for months but suddenly its taking ages just to load a single page and mostly not loading at all.
我的网站是ASP。NET, c#,。NET 4,使用Umbraco 4, IIS 7.5,它已经运行了好几个月了,但是突然间,它花了很长时间才加载一个页面,而且几乎没有加载。
The DB looks fine,
DB看起来很好,
I've restarted the site,
我重新启动,
recycled the APP pool,
回收应用程序池,
looked in the logs, it just looks like jibberish
从原木上看,它看起来像jibberish
Does anyone have any ideas as to how I can investigate further. No I am not asking you to fix my site or tell me why it is not working, I just want to know other methods for investigating the problem so I can get to the bottom of the issue.
有人知道我该如何进一步调查吗?不,我不是要你修复我的网站或告诉我为什么它不工作,我只是想知道调查这个问题的其他方法,这样我才能了解问题的真相。
IIS LOG:
IIS日志:
http://pastebin.com/msjzty7m
Thanks
谢谢
4 个解决方案
#2
1
I have a couple of suggestions:
我有几个建议:
- Set up the ELMAH error log and take a look if some unhandled expcetions.
- 设置ELMAH错误日志并查看是否有一些未处理的扩展。
- Set up mini profiler, maybe it is a bottle neck inside a new added script.
- 设置一个迷你轮廓线,也许是一个瓶子颈在一个新的增加的脚本。
- Use google PageSpeed Insights to analyze your pages.
- 使用谷歌显示的洞察力来分析你的页面。
#3
1
My first guess would be it is infact a data issue. Not that it's taking a long time to grab the data but to process it. I've had a few times now where a page is around 138Kb but took over 3 seconds to wait for the page before rendering. Basically this was cause it was running a 3 tier repeater (repeater inside repeater inside repeater) to create the menu system. So even though the site wasn't big it was taking time processing this menu before sending it out.
我的第一个猜测是,这实际上是一个数据问题。并不是说获取数据要花很长时间,而是要处理数据。我曾经有过几次页面大约是138Kb,但是在呈现之前花了3秒等待页面。基本上这是因为它运行一个三层中继器(中继器内部中继器)来创建菜单系统。所以,尽管这个网站并不大,但在发送之前,它需要时间来处理这个菜单。
Suggestions from me would be to comment out anything new that you've added before this date and bring stuff back in slowly till you find the problem part. After that you can look at caching. And if it's a module (.ascx) use @ Output Caching and that could help.
我的建议是把你在这个日期之前添加的任何新东西都注释掉,然后慢慢地把东西拿回来,直到你找到问题的部分。之后,您可以查看缓存。如果它是一个模块(.ascx),那么使用@输出缓存将会有所帮助。
#4
0
This is not loading at all... the online tools can not help, you need to investigate whats happens on the server.
这根本没有加载……在线工具帮不了什么忙,您需要调查服务器上发生了什么。
The tools for that is the process explorer from sysinternals to see what is running slow your server, then the autoruns to see what you loading with out your knowledge and also slow down your system, and the tcpView to see who is connected to your server.
其中的工具是sysinternals中的process explorer,它可以查看正在运行的内容,然后是autoruns,它可以查看您加载的内容,同时还可以减慢系统速度,tcpView可以查看谁连接到服务器。
#1
#2
1
I have a couple of suggestions:
我有几个建议:
- Set up the ELMAH error log and take a look if some unhandled expcetions.
- 设置ELMAH错误日志并查看是否有一些未处理的扩展。
- Set up mini profiler, maybe it is a bottle neck inside a new added script.
- 设置一个迷你轮廓线,也许是一个瓶子颈在一个新的增加的脚本。
- Use google PageSpeed Insights to analyze your pages.
- 使用谷歌显示的洞察力来分析你的页面。
#3
1
My first guess would be it is infact a data issue. Not that it's taking a long time to grab the data but to process it. I've had a few times now where a page is around 138Kb but took over 3 seconds to wait for the page before rendering. Basically this was cause it was running a 3 tier repeater (repeater inside repeater inside repeater) to create the menu system. So even though the site wasn't big it was taking time processing this menu before sending it out.
我的第一个猜测是,这实际上是一个数据问题。并不是说获取数据要花很长时间,而是要处理数据。我曾经有过几次页面大约是138Kb,但是在呈现之前花了3秒等待页面。基本上这是因为它运行一个三层中继器(中继器内部中继器)来创建菜单系统。所以,尽管这个网站并不大,但在发送之前,它需要时间来处理这个菜单。
Suggestions from me would be to comment out anything new that you've added before this date and bring stuff back in slowly till you find the problem part. After that you can look at caching. And if it's a module (.ascx) use @ Output Caching and that could help.
我的建议是把你在这个日期之前添加的任何新东西都注释掉,然后慢慢地把东西拿回来,直到你找到问题的部分。之后,您可以查看缓存。如果它是一个模块(.ascx),那么使用@输出缓存将会有所帮助。
#4
0
This is not loading at all... the online tools can not help, you need to investigate whats happens on the server.
这根本没有加载……在线工具帮不了什么忙,您需要调查服务器上发生了什么。
The tools for that is the process explorer from sysinternals to see what is running slow your server, then the autoruns to see what you loading with out your knowledge and also slow down your system, and the tcpView to see who is connected to your server.
其中的工具是sysinternals中的process explorer,它可以查看正在运行的内容,然后是autoruns,它可以查看您加载的内容,同时还可以减慢系统速度,tcpView可以查看谁连接到服务器。