CODEWITHSUNDEEP
asp.netperformancetrace
Jeremy Boyd
Jeremy Boyd

Reputation: 5405

ASP.Net MVC Tracing Shows 75 seconds I can't account for

I noticed long render times for a page with a user's account on one of my company's websites. I turned tracing on locally and accessed his account from my development machine, and it as 75 seconds of rendering that I can't find. I added tracing through both the master and child aspx files, but even after the last bit of code (a foreach) in the child page is called, there is another 75 seconds of something happening.

Trace results.

Half a second makes sense (cleaning up something, I don't know what), but 75 makes NO sense.

Trace Results

Upvotes: 3

Views: 142

Answers (2)

Jon Davis
Jon Davis

Reputation: 6763

Make sure you've closed every object you've instantiated that has an IDisposable interface.

Upvotes: 0

Mathias F
Mathias F

Reputation: 15901

I think you realy have some code in the views that takes some time, but the 76 seconds might be spent by ASP.NET MVC rendering itself.

This can happen when you have a couple Html helpers (typically action links) that use routing and you have a good amount of entries in the routing table. Try to render the page with most of the helpers removed to check if this is the case.

Upvotes: 2

Related Questions