经典 ASP 和通配符映射
我们已启用现有经典 ASP 站点的通配符映射，以通过 aspnet_isapi.dll 进行处理。从那时起，网站的性能就下降了？ .asp 文件在由 IIS 提供服务之前是否经过编译？非常感
谢乔蒂什·乔治的任何帮助
We have enabled the wildcard mapping for an existing classic ASP site to handle through aspnet_isapi.dll. Ever since then, the performance of the site has dropped? Does the .asp files get compiled before it served by IIS? Any help is greatly appreciated
Jyothish George
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
哈？你在你的服务器上做了这个。您应该知道性能是否下降。完成后，您就可以访问自己的服务器日志文件和性能计数器了。
由于 ASp 不是一种起始语言，因此它不会被编译。有问题的语言（可能/可能是 VBScript）由 Windows Active Scripting Host 处理...并且对于主要语言（您可以有多种）...这不是编译的。我可以，但我不知道任何一种编译语言。
您使用什么服务器版本？
Häh? You did that on your server. You should KNOW whether the performance dropped or not. Afte rall, you are the guy with access to your own servers logfiles and performance counters.
Since ASp is not a language to start with, it is not compiled. The language in question (possibly / likely VBScript) is handled by the Windows Active Scripting Host... and for the major languages (you can have various)... this is not compiled. I could be, but I know of not a single compiled language.
What server version are you using?
启用通配符映射将通过 aspnet_isapi.dll 推送所有文件，甚至包括 .gif、.css、.jpg、.js 等。这可能就是您的性能下降的地方。
您可能需要考虑将所有静态文件移动到未启用通配符映射的子目录中。
Enabling wildcard mapping will PUSH all files even .gifs, .css, .jpgs, .js etc through the aspnet_isapi.dll. This is probably where your degradation in performance is being seen.
You may want to consider moving all static files into a sub directory that does not have wildcard mapping enabled.
我是 IIS4 和 IIS5 上 ASP 某些部分的程序经理，所以我知道一些关于这些东西的事情！
是的，您可能会产生性能影响，因为您告诉 IIS 通过 ISAPI 路由更多文件请求。当 IIS 收到请求时，它有两个选项 - 绕过所有中间代码并直接从磁盘访问文件并为用户提供服务。这非常非常快并且允许缓存。第二个选项是将其传递给某些代码（ISAPI）进行处理，然后可能提供结果。这是一个慢得多的代码路径。添加通配符映射意味着更多请求将通过 ISAPI 路径。因此，潜在的性能下降。
最好的措施是禁用通配符映射并测量性能；然后打开它并重新测量性能。如果出现性能下降，请考虑限制映射的文件。例如，映射 foo*.bar 可能不会导致太多性能下降；但.b肯定会的。
希望有帮助！
I was the program manager for some parts of ASP on IIS4 and IIS5, so I know a couple of things about this stuff!!
Yes, you can have a perf impact becuase you're telling IIS to route more file request through an ISAPI. When IIS gets a request it has two options - bypass all intermediate code and access the file directly from disk and serve to the user. This is very very fast and allows for caching. The second option is to pass it to some code (an ISAPI) for processing and then potentially serve the result. This is a much slower code path. Adding wildcard mapping means more request will go thru the ISAPI path. Hence a potential perf drop.
The best action is to disable wildcard mapping and measure perf; then turn it on and re-measure perf. If there is a perf drop consider limiting which files are mapped. For example, mapping foo*.bar is probably not going to lead to much perf degradation; but .b most certainly will.
Hope that helps!