IIS7 Integrated Pipeline Mode Slower Than Classic

We are launching a complex 64-bit ASP.NET 2.0 application based on the W2008 R2 standard, and stress tests performed using Team Team Team Team 2008 showed that the integrated pipeline mode is 30% slower than the classic mode.

We have significantly complicated the application tracing, and it seems that the integrated mode is uniformly slower than the classic one. That is, there is no single point that causes delays in integrated mode.

This is the exact opposite of everything Microsoft says about the integrated pipeline, so there may be something completely wrong with the integrated mode or server configuration. But we did not find any settings that could affect this. Some complaints that Sharepoint and reporting services are slower in integrated mode can be found, but our application does not use them, so this is most likely unrelated.

Any ideas that might lead to poor performance or debugging this issue?

+4
source share
2 answers

I would look at how to enable tracking and see where your performance is slower. there is a good article here:

http://www.west-wind.com/weblog/posts/9827.aspx

Hope this helps.

0
source

Have you considered using streams in perfmon?

I have not tested this myself, but I assume that Integrated Pipeline will use more ASP.NET workflows, since all requests are passed to the managed handler.

Here you can find more information:

http://msdn.microsoft.com/en-us/library/ff650682.aspx

See my question here:

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

0
source

All Articles