Geek Answers Handbook

IIS Express Delivery Requests Run 4 Times Longer to Complete

I uploaded the WCAT results on Windows 7, the same as the script so that ts: includes XSL in zip . sorry.

Here is what I noticed:

  • IIS Express has lower requests per second, and general transactions are serviced than regular IIS.
  • IIS Express performs up to 100 requests at a time, while regular IIS on Windows 7 is limited to 10 as it was designed.
  • IIS Express uses a 30% processor, possibly due to additional requests that it processes at the same time.
  • But on average, express requests take much longer ... up to 4 times longer. see "Runtime Counter" and time analysis (first and last byte).

IIS Express can only beat IIS in the total number of requests, because it can process more requests at a time!

Theories of what is happening:

  • Could the fact that IIS prints every request on the command line window even with the trace set does not slow it down?
  • I also noticed many additional modules registered in IIS express applicationhost.config that are not in IIS applicationhost.config . Can there be problems with additional debugging / tracing modules?
  • I noticed that IIS express does not have FileCache and HTTPCache . Maybe that's why?

I hope asp.net experts can clarify how these results are possible if IIS express is not limited.

+7
source share
2 answers

By default, query tracing is enabled for IIS Express. You can see some increase in performance if you disable it. (set enabled = "false" for the traceFailedRequestsLogging object in applicationhost.config)

+9
source

Connecting dots: http://forums.iis.net/p/1175052/1969390.aspx#1969390 . The same question was asked on the iis.net forum, and this sparked a lively discussion.

Just to clarify, IIS Express primarily means a web development tool that provides an add-on functionality over the Cassini development server. Performance was not a top priority for this version. It is true that IIS Express has no connection restrictions, but compatibility with XP has proven costly.

  • For applications with predominantly dynamic content, IIS express overhead should be acceptable.
  • for sites with a lot of static content, the lack of http.sys kernel caching, as well as user-mode caching, will make great functionality.

Try redirecting stdout to nul. It will slightly improve your spirit.

+4
source

More articles:


All Articles