IIS7 Integrated vs Classic Pipeline - which uses more ASP.NET threads?

If you look at machine. Config, web. Config and applicationHost.

Config in IIS 7, you can see that the way static content is served does not change when you switch between classic and integrated pipeline. The only thing that changes is whether requests mapped to asp. Net pass through a managed module or the native ISAPI filter module The only thing that could affect performance is if you modify the default settings for authorization modules and any custom modules you've added to execute when handling requests for static content.

And even here the overhead is probably negligible Therefore a more appropriate benchmark would be IIS 6 vs IIS 7, and I suspect IIS 7 would be the clear winner.

If you look at machine. Config, web. Config and applicationHost.

Config in IIS 7, you can see that the way static content is served does not change when you switch between classic and integrated pipeline. The only thing that changes is whether requests mapped to asp. Net pass through a managed module or the native ISAPI filter module.

The only thing that could affect performance is if you modify the default settings for authorization modules and any custom modules you've added to execute when handling requests for static content. And even here the overhead is probably negligible. Therefore a more appropriate benchmark would be IIS 6 vs IIS 7, and I suspect IIS 7 would be the clear winner.

Try this... learn.iis.net/page.aspx/244/how-to-take-... This should answer a few of your questions.

I'd say you're right, but I' look at it from another perspective. Do you need to process the requests for the non-ASPX pages? For example, to log them, or to forbid the response if some condition is not met.

If you need this processing capability, use integrated pipeline. If you don't, use the classic pipeline.

I need to serve static content: CSS, JS, JPG, PNG, etc. These (especially images) account for a greater percentage of bandwidth than the ASPX page content. – frankadelic Feb 25 '10 at 22:50 But do you need any processing by . NET code for this static content?

– Timores Feb 26 '10 at 0:08 No, but my assumption here is that using integrated pipeline will cause static content to be delivered by ASP. NET, rather than directly by IIS. – frankadelic Feb 26 '10 at 0:36 This is the way I understand it, too, and what I was trying to explain in the answer :-) Use classic pipeline mode.

– Timores Feb 26 '10 at 0:54 in IIS7 asp. Net and IIS is so combined that the statement "delivered by ASP.NET, rather than directly by IIS" doesn't make much sense anymore. In IIS6 IIS used an ISAPI module to forward the request to the asp.

Net runtime, while in IIS7 asp.Net is a first class citizen and you don't have that overhead anymore. Like Chris Eldredge points out, regarding to static files there is no difference. – Pauli Østerø Feb 26 '10 at 20:42.

If you look at machine. Config, web. Config and applicationHost.

Config in IIS 7, you can see that the way static content is served does not change when you switch between classic and integrated pipeline. The only thing that changes is whether requests mapped to asp.net pass through a managed module or the native ISAPI filter module.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.