How to debug?

[Arjen]

Hi,

Last week I realized that my web application is getting slower and
slower.
When I hit a button - the browser starts loading - and after two
seconds I get my page.

Now I want to know where the problem lies. The (built in vs.net)
webserver? The web application? The database? I don't know.

I start hitting the debug button in vs.net but - hmmm - I don't realy
see what's going on.

What is the best way to see what the web application is doing when I
hit some webpages of my application? How can I get a list of currently
executed functions (with timestamp)?

Something like this would be very nice!

Hope somebody can help me with this.
Thanks!
Arjen

 

[Mischa Kroon]

What is the best way to see what the web application is doing when I
hit some webpages of my application? How can I get a list of currently
executed functions (with timestamp)?

Enable tracing

http://msdn2.microsoft.com/en-us/library/0x5wc973.aspx
or
http://msdn2.microsoft.com/en-us/library/94c55d08.aspx

This will show you directly what is going on and when.

 

[Guest]

Hi
From your question, i assume that your app was performing well before last
week, and now its performance is slightly gowing down. If that is the case,
there can be many reasons to it.

1. At the time you noted this performance slowdown, probably the web server
would have taken more load, and servicing many apps. So, try to check on the
stats again.
2. Probably your application is now getting huge set of datas from the
database, as against the datas you would have been getting very little
previously.
So, the data retrieval process taking longer time might be causing this
problem.
Also when you have huge set of datas with you in memory, then that could
also lead to performance issues.

Well, as you debug, you could easily step through the code, where you have
data retrievals and see how much time it occupies.

Prem

 

[Arjen]

Okay, thanks!
I have one webpage which loads modules (think about the I Buy Spy
portal).

Each page loads in 0.01 second. This sounds okay to me.
(0,0137254874572048 --> trace show seconds or not?)

When I look to the details then I see that the begin and end load takes
the most time.

aspx.page Begin Load 0,000612927061958992 0,000023
aspx.page End Load 0,122701767962129 0,122089

That it has to do something in the begin load sounds okay, but I have
no idea what it is doing in the end load. Suggestions?



Still I cannot understand why it takes so long to see the page. I hit a
page, have to wait five seconds, and then see my new page. I did a test
with the windows clock. I hit a page at the sixth of a minute (trace
information also says, first hit sixth second). After that it takes
five seconds to get the page back (I count/read the second with the
windows clock). But the trace info shows at the end render
0,222307863150205.
(Or is 0,2 --> 2 seconds???)

Hope somebody can give me some direction.

Thanks!
Arjen