I am doing stress tests on my ASP.Net MVC2 application, and I have set
<compilation debug="false" />
in web.config.
Simulating 200 connections in the IIS7, which hosts this application, the CPU load goes up to 100%. Simulated requests only access simple home page without the database operations.
Meanwhile, I run the dotTrace
to profile the application, which shows the page render procedure (like RenderControl
, RenderControlInternal
, etc.....) takes about 69% CPU time.
Is this normal? How many connections can an MVC2 application support for one machine?