how do i find what page is causing my performance prob?

  • Thread starter Thread starter kevin goff
  • Start date Start date
K

kevin goff

I am seeing that our CPU spikes for several minutes at 100% for the asp.net
process. This happens several times a day and seems to last for 10 min or
so and use a lot of memory. I'm trying to find out what page it is that is
causing these problems. How can i find out what pages are executing at the
time of the spike?

Thanks,
kevin goff
(e-mail address removed)
 
A quick way might be to check the IIS logs and see what requests were
happening at that time. The IIS logs are typically under
%windir%\system32\LogFiles.
 
I checked the logs. There are currently 20+ sites on this server and each
has it's own logs. Gathering the logs shows ~1000 possible requests that
fell within that time frame.

I'm thinking what I need to do here is to figure out what pages are
currently running when the problem happens. This would probably limit it to
< 20 since most pages are subsecond. The log files are written when the
request is made so I dont have a way to find out how long each request took
to execute.

This web site is running windows 2000. If anyone has any insight as to
whether an upgrade to 2003 would help with this issue (help with diagnosis)
I'd appreciate a post.

Thanks for your time.
Kevin
 
with 2003 you can put each site in its own app pool (aspnet worker process).
then when cpu get hot, use perfmon to see which site is using the cpu. you
should add also monitoring code to your pages.

-- bruce (sqlwork.com)


| I checked the logs. There are currently 20+ sites on this server and each
| has it's own logs. Gathering the logs shows ~1000 possible requests that
| fell within that time frame.
|
| I'm thinking what I need to do here is to figure out what pages are
| currently running when the problem happens. This would probably limit it
to
| < 20 since most pages are subsecond. The log files are written when the
| request is made so I dont have a way to find out how long each request
took
| to execute.
|
| This web site is running windows 2000. If anyone has any insight as to
| whether an upgrade to 2003 would help with this issue (help with
diagnosis)
| I'd appreciate a post.
|
| Thanks for your time.
| Kevin
|
|
|
| | >A quick way might be to check the IIS logs and see what requests were
| > happening at that time. The IIS logs are typically under
| > %windir%\system32\LogFiles.
| >
| > --
| > Scott
| > http://www.OdeToCode.com/blogs/scott/
| >
| > On Tue, 22 Mar 2005 10:07:06 -0600, "kevin goff"
| >
| >>I am seeing that our CPU spikes for several minutes at 100% for the
| >>asp.net
| >>process. This happens several times a day and seems to last for 10 min
or
| >>so and use a lot of memory. I'm trying to find out what page it is that
| >>is
| >>causing these problems. How can i find out what pages are executing at
| >>the
| >>time of the spike?
| >>
| >>Thanks,
| >>kevin goff
| >>[email protected]
| >>
| >>
| >
|
|
 
Thanks for all of your suggestions,

Hi kevin,

I think you can consider bruce's suggestion on using the application pool
to isolate your application if you're using IIS6. Also, if you can enable
trace on your web application, you can also lookup the Application Trace
which contains the event processing steps of each request( how much time it
spends on those events of every request). BTW, is the high CPU problems
occurs right after your application starts or after it has been running for
a period of time? Generally HIGH CPU utilization will be caused when
there're two many worker threads running concurrently which cause serious
thread context switching. Also, some page which use COM component may also
have such issue when the COM component is STA mode that need apartment
switch when perform method call.

Here is a certain blog article which provides some tips on Asp.net
performance issue TS, hope also helps:

http://blogs.msdn.com/srinathv/archive/2003/12/13/43350.aspx

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
 
Back
Top