Have Geek Brain

Asp.net mvc findpartialview performance

I have an ASP.NET MVC application that uses the AreaViewEngine suggested by Phil Haack here . It works great, but the app seems sluggish, so I did some profiling with dotTrace. I pushed the app to our dev server, changed the debug flag to false in web.config (compilation debug = "false"), ran the profiler and used jmeter to generate several thousand hits. What I found is below:

alt text http://i44.tinypic.com/av6e1c.jpg

Please note that VirtualPathProviderViewEngine.FindPartialView took over 320 seconds. I can't figure out what the underlying code is causing the problem, but I suspect it's related to the problem mentioned here here .

The blog post states that running in release mode will cause the view path resolution to be cached, but that doesn't seem to be the case (or if it is, something else is taking a long time in the FindPartialView function.

Any thoughts?

Edit:

I never found the cause of the problem, but I ended up downloading the MVC source code for release 1.0 and it works great. There must be a mismatch between the binary being installed and the 1.0 source code. or something related to my installation (although the problem showed up on multiple machines).

0


a source to share


1 answer


One thing you can do to help performance when using RenderPartial () or View () is to return the path to the view so it doesn't look for it. When you only specify a file name, it should identify that file name only and then look for the view in the folder list.



0


a source






More articles:


All Articles