1

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.

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?

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

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

enter image description here

JK.
  • 21,477
  • 35
  • 135
  • 214
  • Well, my friend, the extra time is most likely in methods not wrapped by the profiler ;) – Pluc Aug 20 '13 at 11:48
  • Mini profiler appears to automatically wrap every action that is called – JK. Aug 20 '13 at 12:08
  • Yes, actions. Is a MVC page request handling only a call to an action method? I doubt it. – Pluc Aug 20 '13 at 14:22
  • Is there are way to get mini profiler to include other stuff that happens? That was the gist of the question above. – JK. Aug 20 '13 at 21:22
  • The question wasn't about how to use MiniProfiler :) You should probably go to the main website (http://miniprofiler.com/) and read the getting started. – Pluc Aug 21 '13 at 11:15

1 Answers1

2

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.

JK.
  • 21,477
  • 35
  • 135
  • 214