什么是通配符映射通过IIS 6.0的所有请求的性能影响？ [英] What are the performance implications of wildcard mapping all requests through IIS 6.0?
问题描述
我感兴趣的是使用 UrlRewriter.NET ，并在有关IIS 6.0上WIN2K3，他们说通过ASP.NET ISAPI的所有请求映射。<配置页面 / p>
这很好，但我想知道如果任何人有好坏东西，说这样的表现明智？是我的Web服务器将通过执行此操作将拖累其膝盖还是会多出一个小小的阶梯上去的服务器负载？
我的服务器目前有房间了喘息的机会，所以一些性能损失预计和可接受的。
通配符映射确实对性能有很大的影响，主要是因为它使用应用程序的线程池不是页面请求的处理，但是对于所有的内容。让我们假设你有一个常用的页面如图像，CSS和JavaScript至少10个额外的资源 - 那么你阻挡通过直接从池服务于静态内容的其他潜在的请求。在asp.net更多信息IIS 6线程可以发现这里
走了过来（我是如何做到的）一种方式是无法通配符映射到持有静态内容的文件夹 - 之后您会收到唯一有效的应用程序的请求，你会在普通情况下做的。
要取消映射的静态目录的方法是创建他们每个人的应用程序，然后执行取消映射，之后撤消应用程序创建的事情。你可以找到的史蒂夫·桑德森的博客。
I am interested in using UrlRewriter.NET and noticed in the config page for IIS 6.0 on Win2k3, that they say to map all requests through the ASP.NET ISAPI.
That's fine, but I am wondering if anyone has good or bad things to say about this performance wise? Is my web server going to be dragged down to its knees by doing this or will it be more of a small step up in server load?
My server currently has room to breathe now, so some performance hit is expected and acceptable.
Wildcard mapping does have a huge impact on performance, mostly because it uses the app thread pool not for page request processing, but for all the content. Let's assume you have a usual page with at least 10 additional resources like images, css and javascript - then you're blocking other potential request by serving the static content directly from the pool. More info on asp.net IIS 6 threading can be found here.
One way to go over it (how i did it) is to unable wildcard mapping to the folders that hold the static content - after that you'll receive only valid app request as you would do in an ordinary situation.
The way to unmap the static directories is to create an application of each one of them and then do the unmapping, and after that to undo the application creating thing. You can find more details on Steve Sanderson's blog.
这篇关于什么是通配符映射通过IIS 6.0的所有请求的性能影响？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
