我们最近部署了大约收到一个应用程序。超过3个月增长20万的页面浏览量使用IIS 6通配符映射设置，也没有性能问题。我们做了最主机我们的形象在CDN，但其他静态内容直接从网站上提供。

We recently deployed an app that received approx. 20 million page views over a 3 month period using the IIS 6 wildcard mapping setup and had no performance issues. We did host most of our images on a CDN, but other static content was served directly from the site.

有关它的价值，IIRC，在asp.net处理程序将通过进行处理的默认处理程序通过对静态文件类型回到IIS的请求。唯一的实用性能命中是在此过程中，一个工作线程被占用识别和传送请求的时间。但在所有的最极端的情况下，这是太微不足道的事。

For what it's worth, IIRC, the asp.net handler will pass requests for static file types back to IIS through a default handler for processing. The only practical performance hit is the time during that process that a worker thread is occupied identifying and transferring the request. In all but the most extreme scenarios, this is too trivial to matter.

作为一个额外的说明中，我们负荷测试之前去住我提到的，发现它可以每秒处理近2000个静态请求和每秒约700请求，涉及数据库活动的网页应用程序。该网站托管于4 IIS 6服务器之后了1GB的互联网管道ZXTM负载平衡器。

As an extra note, we load tested the application I mentioned prior to going live and found that it could handle nearly 2000 static requests per second and around 700 requests per second for pages that involved database activity. The site was hosted on 4 IIS 6 servers behind a ZXTM load balancer with a 1GB internet pipe.

下面是对整个静态文件处理业务一些好的建议的链接：

Here's a link with some good advice on the whole static file handling business:

http://msmvps.com/blogs/omar/archive/2008/06/30/deploy-asp-net-mvc-on-iis-6-solve-404-com$p$pssion-and-performance-problems.aspx