DebugDiag资料显示长期运行的自 [英] DebugDiag shows long Running Since
问题描述
我们的应用程序池回收，每天数次。我是pretty确保它是因为它击中了内存限制。我也pretty确保它不应该打〜3GB的内存限制。我试着使用的WinDbg来分析内存转储，但收效甚微。以后我可能会再试。但是使用DebugDiag资料给我上的数据一些不错的视觉效果，并且已经导致了一些变化，降低了它的回收次数。有我有点困惑和担心的一个报告是HttpContext的报告。它显示了一些输出是这样的：
Our app pool recycles several times a day. I'm pretty sure it's because it hits the memory limit. I'm also pretty sure that it should NOT hit the memory limit of ~3GB. I tried using WinDbg to analyze the memory dump, with little success. I might try again later. However using DebugDiag gives me some nice visualizations on the data and already lead to some changes that have reduced the number of times it recycles. One report that has me a bit confused and worried is the HttpContext Report. It shows some output like this :
HttpContext Timeout Completed RunningSince ThreadId ReturnCode Verb RequestPath+QueryString
0x02374c94 110 Sec No 995 Sec --- 302 GET /Loans/Details/529146/517006
0x02472a44 110 Sec No 993 Sec --- 200 GET /Login ReturnUrl=%2fLoans%2fDetails%2f529146%2f517006
0x024d2f94 110 Sec No 979 Sec --- 302 POST /Loans/UpdateDealer
0x025773c0 110 Sec No 951 Sec --- 302 GET /Applicants
0x025d6bb4 110 Sec No 951 Sec --- 200 GET /Login ReturnUrl=%2fApplicants
0x025f5adc 110 Sec No 935 Sec --- 302 GET /Applicants/Details/537358
0x02654708 110 Sec No 935 Sec --- 200 GET /Login ReturnUrl=%2fApplicants%2fDetails%2f537358
0x026b1bb4 110 Sec No 926 Sec --- 200 POST /Loan/InsertLoanChecklistItem
0x027710dc 110 Sec No 914 Sec --- 200 GET /Applicants
0x02779320 110 Sec No 915 Sec --- 302 POST /Login ReturnUrl=%2fApplicants
0x02797448 110 Sec No 914 Sec --- 200 GET /Loans/Details/523729/526198
0x02867070 110 Sec No 911 Sec --- 200 POST /Loans/UpdateAmount
有，当然，在报告中多出很多线路。难道我真的已经运行995秒（约15分钟）请求，仍然没有完成？他们只是挂在那里？他们在等待着别的东西来完成？我不知道我还能相信它，更不用说启动诊断吧。别人可以给我一些见解如何跨preT这些数据？
There are, of course, many many more lines in the report. Do I really have requests that have been running for 995 seconds (~15 minutes) and are still not complete? Are they just hung there? are they waiting for something else to finish? I'm not sure I can even believe it, let alone start diagnosing it. Can someone else give me some insight into how to interpret this data?
推荐答案
经过长期的研究，我得到了解决，而不是精确解后，但它可以帮助。
After a long research I got the solution, not exact solution, but it can help.
由于列中的长时间运行表明从那里它的第一个请求开始的时间。
这并不意味着请求时间是完成任何用户的任何单个请求。
所以，在这里没有什么可担心这个数字高。
The long running since column indicate the time from where its first request start. It does not mean the request time is to complete any single request for any user. So, here nothing to worry on this high number.
编辑：
http://blogs.msdn.com/b/yunjin /archive/2005/08/25/456355.aspx
http://blogs.msdn.com/ b /运劲/存档/ 2005/08/29 / 457150.aspx
<一个href=\"http://social.msdn.microsoft.com/Forums/en/vsdebug/thread/17f783cd-d5af-4146-ab46-be80e62da750\" rel=\"nofollow\">http://social.msdn.microsoft.com/Forums/en/vsdebug/thread/17f783cd-d5af-4146-ab46-be80e62da750
和内存泄漏我会建议使用WinDbg。
WinDbg的参考：
And for memory leak I would recommend to use WinDbg. WinDbg ref:
的http://blogs.msdn.com/b/alejacma/archive/2009/06/30/sos-cheat-sheet-net-2-0-3-0-3-5.aspx
http://geekswithblogs.net/.NETonMyMind/archive/ 2006年/ 03/14 / 72262.aspx
这篇关于DebugDiag资料显示长期运行的自的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
