Tracing

[Mike Gleason jr Couturier]

Hi,

I traced my pages and everytime the slowest part is the "PreInit" (~0.02s)
when everything else is negligible (~0.00002)
(http://localhost:0000/trace.axd)

How can I know a little more what's happening in the PreInit?

Thanks!

 

[Holg]

I traced my pages and everytime the slowest part is the "PreInit" (~0.02s)
when everything else is negligible (~0.00002)
(http://localhost:0000/trace.axd)

How can I know a little more what's happening in the PreInit?

You cant see more there if you dont Trace manually some additional
information.

Context.Trace.Write("Doing something")

Our you could set a breakpoint and walk though. Look if there are some
initializations that you can optimize.

Holg

 

[Gregory A. Beamer]

Hi,

I traced my pages and everytime the slowest part is the "PreInit"
(~0.02s) when everything else is negligible (~0.00002)
(http://localhost:0000/trace.axd)

How can I know a little more what's happening in the PreInit?

Thanks!

Much of the ASP.NET bits are loaded in PreInit, as this is where the
"dynamic" magic happens. It is fairly normal to see some time here.

Just curious: Does a second hit to the same page reduce the time in
PreInit, as I would think you have some JIT going on about this time
that would be reduced after you hit the page once. Just a thought.

As for tracing what is going on, it is a bit complex, since you are
examining time consumed by the ASP.NET bits (unless you have coded your
own Page_PreInit event handler).

Peace and Grace,

 

[Mike Gleason jr Couturier]

Thanks to both of you

I downloaded the trial of Red-Gate Ants profiler. Amazing

I have found out that most of the time were spent in Html.ActionLinks(...)
(I use .NET MVC Framework 1.0)

I would never have suspected that it would affect performance (it is because
it's called so many times per request)

I'm now caching those... saw a 20% increase in pages served per seconds

Thanks

Mike Gleason jr Couturier