高 CPU 和大量计时器
我发现我的服务器上的 CPU 很高。我进行了故障转储并启动了 Windbg。
我正在关注，但不知道该怎么做：
From !runaway Top 5 thread related to CPU`enter code here` Thread Time 33:1758 0 days 0:08:58.109 24:128c 0 days 0:05:09.531 25:15b0 0 days 0:04:53.281 23:a94 0 days 0:04:50.343 26:bf8 0 days 0:04:48.984
来自！threadpool
0:000> !threadpool CPU utilization 100% Worker Thread: Total: 18 Running: 17 Idle: 1 MaxLimit: 400 MinLimit: 4 Work Request in Queue: 4 AsyncTimerCallbackCompletion TimerInfo@159b81b8 AsyncTimerCallbackCompletion TimerInfo@185e48a8 Unknown Function: 6a2aa293 Context: 3a1bc2e0 -------------------------------------- Number of Timers: 30 -------------------------------------- Completion Port Thread:Total: 1 Free: 1 MaxFree: 8 CurrentLimit: 0 MaxLimit: 400 MinLimit: 4 0:000> !threads ThreadCount: 56 UnstartedThread: 0 BackgroundThread: 56 PendingThread: 0 DeadThread: 0 Hosted Runtime: no
有人可以帮助我吗？
I am seeing high CPU on my server. I took a crash dump and fired up windbg.
I am getting following but not sure what to make of it:
From !runaway Top 5 thread related to CPU`enter code here` Thread Time 33:1758 0 days 0:08:58.109 24:128c 0 days 0:05:09.531 25:15b0 0 days 0:04:53.281 23:a94 0 days 0:04:50.343 26:bf8 0 days 0:04:48.984
from !threadpool
0:000> !threadpool CPU utilization 100% Worker Thread: Total: 18 Running: 17 Idle: 1 MaxLimit: 400 MinLimit: 4 Work Request in Queue: 4 AsyncTimerCallbackCompletion TimerInfo@159b81b8 AsyncTimerCallbackCompletion TimerInfo@185e48a8 Unknown Function: 6a2aa293 Context: 3a1bc2e0 -------------------------------------- Number of Timers: 30 -------------------------------------- Completion Port Thread:Total: 1 Free: 1 MaxFree: 8 CurrentLimit: 0 MaxLimit: 400 MinLimit: 4 0:000> !threads ThreadCount: 56 UnstartedThread: 0 BackgroundThread: 56 PendingThread: 0 DeadThread: 0 Hosted Runtime: no
Can anybody help me with this?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
单个转储是没有用的。您需要捕获多个挂起转储，每个转储间隔一分钟，然后使用 !runaway 找到罪魁祸首。之后！CLRStack 和 kb 可以向您显示有关该线程的更多信息。
A single dump is useless. You need to capture several hang dumps with one minute interval each, and then use !runaway to find the culprit. After that !CLRStack and kb can show you more info about that thread.