blocks|key|1360610|text|我们在一个将大量数据转储到输出的递归查询上遇到了这个问题--您是否仔细检查了所有内容是否都存在，并且不存在无限循环？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1360611|可能会尝试用一个页面来缩小范围--我们发现and在同样的情况下也没有太大的帮助--我们最终做的是运行网站，点击一个页面，观察CPU+-点击下一个页面，观察CPU+-非常有条不紊，非常耗时，但如果你通过一些代码跟踪找不到它，你可能就不走运了--|1360612|我们可以使用IIS日志文件追踪到一组可疑的页面-|1360613|希望这能有所帮助！|1360614|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

We had this on a recursive query that was dumping tons of data to the output - have you double checked everything does exit and no infinite loops exist?

Might try to narrow it down with a single page - we found ANTS to not be much help in that same case either - what we ended up doing was running the site hit a page watch the CPU - hit the next page watch CPU - very methodical and time consuming but if you cant find it with some code tracing you might be out of luck - 

We were able to use IIS log files to track it to a set of pages that were suspect - 

Hope that helps !

blocks|key|1145599|text|如果你的CPU达到了100%25并且一直保持在那里，你很可能会遇到死锁或者无限循环的情况。分析器似乎是查找无限循环的一个很好的选择。然而，跟踪死锁要困难得多。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1145600|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If your CPU is spiking to 100% and staying there, it's quite likely that you either have a deadlock scenario or an infinite loop. A profiler seems like a good choice for finding an infinite loop. Deadlocks are much more difficult to track down, however.

blocks|key|1360713|text|这并不是一个很好的答案，但您可能需要老办法，捕获IIS进程的映像快照并对其进行调试。你可能还想看看Tess+Ferrandez的博客--她是一个非常棒的微软升级工程师，她的博客专注于windows+ASP.NET的调试，但这个博客通常与windows调试相关。如果你选择ASP.NET标签(这就是我链接到的标签)，那么你会看到几个类似的项目。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1360714|entityMap|0|LINK|mutability|MUTABLE|url|http://blogs.msdn.com/tess/archive/tags/ASP.NET/default.aspx^0|1D|E|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

It's not much of an answer, but you might need to go old school and capture an image snapshot of the IIS process and debug it. You might also want to check out <a href="http://blogs.msdn.com/tess/archive/tags/ASP.NET/default.aspx" rel="noreferrer">Tess Ferrandez</a>'s blog - she is a kick a** microsoft escalation engineer and her blog focuses on debugging windows ASP.NET, but the blog is relevant to windows debugging in general. If you select the ASP.NET tag (which is what I've linked to) then you'll see several items that are similar.

blocks|key|1145701|text|Process Explorer是一款优秀的故障排除工具。您可以尝试使用它来查找CPU使用率高的问题。它可以让您深入了解应用程序的工作方式。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1145702|您还可以尝试使用Procdump转储进程并分析CPU上到底发生了什么。|1145703|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/Process_Explorer|1|http://en.wikipedia.org/wiki/Central_processing_unit|2|http://technet.microsoft.com/en-us/sysinternals/dd996900.aspx^0|0|G|0|14|3|1|0|8|8|2|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]|$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@$A|Z|B|10|1|11]]|C|$]]|$1|F|3|-4|5|6|7|12|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]|P|$5|I|J|K|C|$L|Q]]]]

<a href="https://en.wikipedia.org/wiki/Process_Explorer" rel="nofollow noreferrer">Process&nbsp;Explorer</a> is an excellent tool for troubleshooting. You can try it for finding the problem of high <a href="http://en.wikipedia.org/wiki/Central_processing_unit" rel="nofollow noreferrer">CPU</a> usage. It gives you an insight into the way your application works.

You can also try <a href="http://technet.microsoft.com/en-us/sysinternals/dd996900.aspx" rel="nofollow noreferrer">Procdump</a> to dump the process and analyze what really happened on the CPU.

blocks|key|1360794|text|如果您发现加载页面需要时间，请使用SharePoint的Developer+Dashboard查看哪个组件需要时间。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1360795|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/office/ff512745%2528v=office.14%2529.aspx^0|S|J|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

If you identify a page that takes time to load, use SharePoint's <a href="http://msdn.microsoft.com/en-us/library/office/ff512745%28v=office.14%29.aspx" rel="nofollow">Developer Dashboard</a> to see which component takes time.

blocks|key|1145803|text|这充其量只是一个猜测，但也许您的开发团队正在以调试模式而不是发布模式构建和部署应用程序。这将导致出现.pdb文件。这意味着在系统执行期间，应用程序将占用额外的资源来收集系统状态和调试信息，从而导致更多的处理器利用率。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1145804|因此，要确保它们是在发布模式下构建和部署就足够简单了。|1145805|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

This is a guess at best, but perhaps your development team is building and deploying the application in debug mode, in stead of release mode. This will cause the occurrence of .pdb files. The implication of this is that your application will take up additional resources to collect system state and debugging information during the execution of your system, causing more processor utilization.

So, it would be simple enough to ensure that they are building and deploying in release mode.

An ASP.NET web app running on IIS6 periodically shoots the CPU up to 100%. It's the W3WP that's responsible for nearly all CPU usage during these episodes. The CPU stays pinned at 100% anywhere from a few minutes to over an hour. 

This is on a staging server and the site is only getting very light traffic from testers at this point. 

We've running ANTS profiler on the server, but it's been unenlightening. 

Where can we start finding out what's causing these episodes and what code is keeping the CPU busy during all that time?

W3WP.EXE using 100% CPU - where to start?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

在IIS6上运行的ASP.NET web应用程序周期性地将CPU使用率提高到100%。在这些事件中，几乎所有的CPU使用量都是由W3WP负责的。CPU在几分钟到一个多小时的任何位置都保持100%不动。这是在一个临时服务器上，该站点在这一点上只从测试人员那里获得了非常少的流量。我们已经在服务器上运行了ANTS profi...

问使用100%cpu的W3WP.EXE -从哪里开始？
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用100%cpu的W3WP.EXE -从哪里开始？EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用100%cpu的W3WP.EXE -从哪里开始？
EN