0

I am working on website performance and need a little bit of help determining a slow spot. Below is a snapshot of a typical request to the home page. Obviously I can speed up the SQL a bit, but where can I look to see what took the first step (http://168.62.16.83:80) 168ms?

Does anyone have any advice, or blog post that explains what goes on behind the scenes, and tips on optimizing it? Or is this just the time it took to download all the static content?

enter image description here

  • I got that sql to sub 50ms, but I'm still stumped on the first step. I am in RELEASE mode, and debug=false in config. –  May 10 '12 at 16:46

1 Answers1

1

The most effective way to find stuff like this is use a traditional profiler like ants, dotTrace or the built in one. (see also)

As to where the time, it is possible you have an expensive spot in Application_BeginRequest or during authentication.

Community
  • 1
  • 1
Sam Saffron
  • 128,308
  • 78
  • 326
  • 506
  • For the record the apparent slowness was due to the Azure cache. I had my website deployed in west coast region, and the cache in the north central. Whoops!. Moving them to the same data center cut off 150ms off that request. It also made the sql call another 20ms faster. woot! –  May 11 '12 at 20:06