DebugDiag未完成分析 [英] DebugDiag not completing analysis

查看:110
本文介绍了DebugDiag未完成分析的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我一直在尝试为.NET Web应用程序找到较高的CPU使用率.我按照本文中的说明使用了DebugDiag工具: https://www.iis.net/learn/troubleshoot/performance-issues/troubleshooting-high-cpu-in-an-iis-7x-application-pool

已成功收集转储,但是当使用DebugDiag Analyzer分析转储时,其运行了数小时,但未完成.实际需要多长时间?

I have been trying to find high cpu usage, for a .NET web application. I used the DebugDiag tool as explained in this article: https://www.iis.net/learn/troubleshoot/performance-issues/troubleshooting-high-cpu-in-an-iis-7x-application-pool

The dump was successfully collected, but when the dump is analyzed using the DebugDiag Analyzer, its running for hours, without completing. How long does it actually takes?

没有指示何时完成.转储文件的大小约为6.6 GB,分析器在创建转储的同一台计算机上运行.

There is no indication when it will complete. The dump file size is around 6.6 GB and the analyzer is run on the same machine where the dump was created.

推荐答案

如果转储为6.6gb,我建议将其从有问题的计算机上卸下并在另一台计算机上运行.400mb的报告可能需要4到5分钟才能运行.我什至不想考虑一个6.6gb的硬盘需要运行多长时间.

If the dump is 6.6gb I'd recommend taking it off the machine in question and running it on another machine. A report of 400mb can take 4-5 minutes to run. I don't even want to think on how long a 6.6gb one would take to run.

这篇关于DebugDiag未完成分析的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆