IIS 和 w3wp 进程数
我在 Server 2008 上运行 IIS 7,并为应用程序使用一个 AppPool,该应用程序基本上只是 ASP.NET WebMethod 的集合。其中一些方法在返回之前会处理几个小时。
奇怪的是,有时当我同时启动多个请求时,IIS 会启动一个 w3wp 进程(并且似乎在请求之间共享它),而其他时候它会启动多个 w3wp 进程(每个请求 1 个进程)。
在观察这一点时,我总是小心地使用任务管理器并查看所有用户的进程。谁能解释这种不一致的行为?
I'm running IIS 7 on Server 2008, with a single AppPool for an application which is basically just a collection of ASP.NET WebMethods. Some of these methods process for hours before they return.
What's weird, is that sometimes when I launch multiple simultaneous requests IIS spins up a single w3wp process (and seems to share it amongst the requests) and other times it spins up multiple w3wp processes (1 for each request).
I am always careful to use task mgr and view processes for all users when observing this. Can anyone explain this inconsistent behavior?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
默认情况下,每个应用程序池都有 1 个 w3wp 进程,但在网络园中,每个应用程序池可以存在多个 w3wp 进程。
编辑:有关的更多信息网络花园
By default each app pool gets 1 w3wp process, but in a web garden multiple w3wp processes can exist per app pool.
Edit: A little more info about web gardens
也许是时候重新考虑您的网络花园了。 Scott Forsyth 有一个有趣的 11 分钟视频日志,解释了为什么网络花园会适得其反:http://dotnetslackers.com/articles/iis/Why-You-Shouldnt-Use-Web-Gardens-in-IIS-Week-24.aspx
链接到他的文章在他的 VLog 中提到:
IIS6 和 IIS7 的调整建议 - 阅读整篇文章:http://support.microsoft .com/kb/821268
更多信息 http://blogs.msdn.com/b/tmarq/archive/2007/07/21/asp-net-thread-usage-on-iis-7-0-and-6 -0.aspx
他的底线是,如果您遇到可以通过网络花园解决的性能问题,请使用网络花园作为一个很好的拐杖,直到解决潜在的性能问题(通常是资源争用)。
It may be time to re-think your web-garden. Scott Forsyth has an interesting 11 minute vLog on why webgardens are counterproductive: http://dotnetslackers.com/articles/iis/Why-You-Shouldnt-Use-Web-Gardens-in-IIS-Week-24.aspx
Links to articles he mentions in his VLog:
Tuning recommendations for IIS6 and IIS7 -- read the whole article: http://support.microsoft.com/kb/821268
Further information http://blogs.msdn.com/b/tmarq/archive/2007/07/21/asp-net-thread-usage-on-iis-7-0-and-6-0.aspx
His bottom line is if you have performance problems that are resolved by web gardens—use the web gardens as a great crutch until the underlying performance issue (usually resource contention) is resolved.