MVC-Mini Profiler vs DotTrace inconsistencies

I'm trying to find a bottleneck that I believe is inside our controllers (I suspect Unity IoC).

Using MVC-Mini-Profiler, I found a method that takes 500 ms to complete the simplest task.

However, after tracing this with DotTracer - it seems that it only takes 16ms to execute the thread ...

Has anyone come across this before?

Just to note - Debug mode is set to false in Web.Config

Dottracer

Mini profiler

+4
source share
1 answer

I found a solution to this problem. It turns out that everything was connected with the session.

Since I simultaneously shot 4 HTTP requests to the same server, the session object was blocked every time, which caused my requests to be queued and processed after the session object was unlocked.

Addendum:

[SessionState(SessionStateBehavior.Disabled)] 

for the controller as an attribute, forces MVC2 to go up to become networkless and therefore increases performance tenfold

(Answer from:

Why do multiple simultaneous AJAX calls with the same ASP.NET MVC action cause the browser to block? )

+2
source

All Articles