MVC Miniprofiler，哪里的所有额外的时间去了？ [英] MVC Miniprofiler, where did all the extra time go?

问题描述

我使用MVC迷你探查发现为什么一个非常基本的页面渲染非常慢：当本地运行它需要700毫秒来呈现只用HTML的12KB。

I'm using MVC Mini Profiler to find why a extremely basic page is quite slow to render: when run locally it takes 700 ms to render just 12kb of html.

这表明，所有的动作都是微不足道的（他们甚至不显示，除非我点击显示琐碎的按钮），最长的就是2.4毫秒。但从开始时间数字跃升为每个这些所谓的琐碎的行动大约100毫秒。什么是利用这个时间呢？是否有一个miniprofiler选项，可以帮助显示其中使用这个时间呢？

It shows that all of the actions are trivial (they don't even show unless I click the show trivial button), the longest is just 2.4 ms. But the "time from start" number jumps by around 100ms for each of these trivial actions called. What is using this time? Is there a miniprofiler option that can help show where this time was used?

编辑：额外的时间可能是在<一个发生href=\"http://blog.stevensanderson.com/blogfiles/2007/ASPNET-MVC-Pipeline/ASP.NET%20MVC%20Pipeline.pdf\"相对=nofollow称号=MVC管道> MVC管道 - 有什么办法来分析这个

The extra time is possibly occurring in the MVC Pipeline - is there any way to profile this?

编辑＃2：试图precompile的意见与＆LT; MvcBuildViews＆GT;真＆LT; / MvcBuildViews＆GT; 并没有得到改善的性能。

EDIT #2: Trying to precompile the views with <MvcBuildViews>true</MvcBuildViews> has not improved the performance

推荐答案

原来，正确的答案是从MiniProfiler 1.9升级到2.1，因为该版本可以分析的MVC管道的多个部分。

It turns out that the correct answer was to upgrade from MiniProfiler 1.9 to 2.1 because that version can profile more parts of the MVC pipeline.

这篇关于MVC Miniprofiler，哪里的所有额外的时间去了？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！