2

I'm trying to trace through a large .net website to find out what's taking 4 to 5 seconds to load. Normally I just put:

trace="true"

in the aspx page declaration and I'm able to somewhat narrow it down from there.

But the problem I have is that I need it to be more narrow of what's taking so long. Right now I'm only getting that between Begin PreRender and End PreRender it takes 5 seconds.

Before I start stepping through every line and writing tracing statements throughout this code, is there a simple way and an easy to use tool to get a very detailed log of one page's entire execution? It's only for my localhost, not production, and the more detail the better. I don't care if the log file is 50MB when its done, I'd just want to see what exact function is taking so long.

adam
  • 3,498
  • 6
  • 34
  • 46

4 Answers4

2

You can profile the code using the ANTS Performance Profiler.

They have a free 14 day trial on their website.

George Stocker
  • 57,289
  • 29
  • 176
  • 237
  • Wow, exactly what I was looking for and more. I only have Visual Studio 2008 so I can't use 2010's profiler. So far the 14 day trial has been working great (its too bad its $400 for just one user though) – adam Dec 27 '10 at 21:00
1

If you own the premium or ultimate edition of Visual Studio 2010, you can use the integrated profiler which can show you the methods where your program spends the most time in.

There are many .NET profilers from 3rd party vendors on the market, for example Jetbrains dotTrace.

Jan
  • 15,802
  • 5
  • 35
  • 59
0

I've used Eqatec and it has a free version.

Chad
  • 1,404
  • 1
  • 18
  • 29
0

You want visibility into why it's taking time. Tracing and measuring tools are a common way, but there's another.

The method I rely on is this. It sounds crude, but it's not. Here's a simple explanation.

If you want the statistical argument, look here.

Community
  • 1
  • 1
Mike Dunlavey
  • 40,059
  • 14
  • 91
  • 135