Diagnosing runaway CPU in a .Net production application

前端 未结 10 677
野性不改
野性不改 2021-02-01 10:12

Does anyone know of a tool that can help me figure out why we are seeing runaway CPU in a managed app?

What I am not looking for:

相关标签:
10条回答
  • 2021-02-01 10:46

    Use the Managed debugger. Helped me before. Just a few files needed. You could probably just see what is happening (perhaps exception handling stuck in a loop).

    0 讨论(0)
  • 2021-02-01 10:48

    It does sound like you need a real profiler, but I thought I'd just throw this out there: PerfMon. It comes with windows, you can setup a perfmon profile that you can send to the user, they can capture and send you the log.

    Here's a couple links I've kept around every time I need a perfmon refresher: TechNet magazine from 2008 and a post from the Advanced .NET Debugging blog.

    0 讨论(0)
  • 2021-02-01 10:48

    The worse a problem is, the easier it is to find by this technique.

    There is a tool you can get, called Stackshot, that might help in your case. Look here and here.

    0 讨论(0)
  • 2021-02-01 10:49

    I think you should look at memory and disk usage as well. If a machine runs out of memory and needs to start using virtual memory (on the disk drive), you'll see a spike in CPU and disk activity. In such conditions what looks like a CPU bottleneck is actually a memory bottleneck.

    0 讨论(0)
提交回复
热议问题