ASP.NET MVC Performance

Question

What aspects of MVC performance affect the performance of your web application the most? Usually access to the database is indicated as the default culprit, but are there any other components that have an effect? Do you prioritize the number of concurrent clients, memory used on the server, response time, or something else?

This answer contains some very good general suggestions, but I am looking for features of where the infrastructure does not meet your expectations.

Answer 1

The ASP.NET MVC framework is excellent, and sites like this, which are its obvious examples. There is nothing in this that would affect the performance of my applications. It just works very well. What affects performance is bad code or the concept of poor architecture, but it is definitely not something we can blame for it. After spending years with ASP.NET web forms, I cannot say that MVC performance is worse or better, I can say that it has turned the painful experience of writing web applications into something that brings so much joy. I successfully run production applications with ASP.NET MVC 1.0 and have never experienced any problems.

In your question, you indicate access to the database =>, which is the problem that all web applications have and which is not an integral part of the structure used. In addition, in places with heavy traffic, using caching can improve performance, and ASP.NET MVC has some really good caching mechanisms.

So, all I can say is that you and the team providing this excellent infrastructure are doing very well.

Answer 2

Now that I understand who is asking this question, I better understand the question.

The biggest problem with MVC is that RenderPartial can be very slow when you use inline resources as views. If I remember, this was due to the fact that VirtualPathProvider does not work so well. We ended up trying to use memoization to speed up some calls, but ended up having to start writing directly to the presentation output stream.

I think that we faced the same problem as the lostechies guys, with a similar take on their built-in constructors, only we used it to generate grids.

http://www.lostechies.com/blogs/hex/archive/2009/06/14/opinionated-input-builders-part-7-more-on-performance-take-2.aspx