Code Climber和这篇博客文章提供了提高应用程序性能的详细方法。

编译后的查询将提高应用程序的性能，但它与ASP没有任何共同之处。净MVC。它将加速每一个db应用程序，所以它不是真正的MVC。

一件非常简单的事情是在访问页面所需的数据时进行异步思考。无论是从web服务、文件、数据库还是其他东西读取，都尽可能使用异步模型。虽然它不一定会帮助任何一个页面更快，但它会帮助您的服务器整体性能更好。

在您嚷嚷着优化客户端时，不要忘记数据库层。我们有一个应用程序在一夜之间从5秒加载到50秒。

在检查中，我们做了一大堆模式更改。一旦我们刷新统计数据，它突然变得像以前一样灵敏。

另外，如果你使用NHibernate，你可以为查询打开和设置二级缓存，并添加到查询范围和超时。并且有踢屁股的EF, L2S和NHibernate分析器- http://hibernatingrhinos.com/products/UberProf。这将有助于调优您的查询。

我还要补充一点:

Use Sprites: Sprites are a great thing to reduce a request. You merge all your images into a single one and use CSS to get to good part of the sprite. Microsoft provides a good library to do it: Sprite and Image Optimization Preview 4. Cache Your server object: If you have some references lists or data which will change rarely, you can cache them into memory instead of querying database every time. Use ADO.NET instead of Entity Framework: EF4 or EF5 are great to reduce development time, but it will be painful to optimize. It's more simple to optimize a stored procedure than Entity Framework. So you should use store procedures as much as possible. Dapper provides a simple way to query and map SQL with very good performance. Cache Page or partial page: MVC provides some easy filter to cache page according to some parameters, so use it. Reduce Database calls: You can create a unique database request that returns multiple objects. Check on Dapper website. Always have a clean architecture: Have a clean n-tiers architecture, even on a small project. It will help you to keep your code clean, and it will be easier to optimize it if needed. You can take a look at this template "Neos-SDI MVC Template" which will create a clean architecture for you with lots of performance improvements by default (check MvcTemplate website).

使用捆绑和缩小还可以帮助您提高性能。它基本上减少了页面加载时间。