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)
"kevin goff" <ke********@nospam.nospam> wrote in message
news:ek**************@TK2MSFTNGP12.phx.gbl...
| 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
|
|
|
| "Scott Allen" <sc***@nospam.odetocode.com> wrote in message
| news:67********************************@4ax.com...
| >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"
| > <ke********@nospam.nospam> wrote:
| >
| >>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
| >>ke********@nospam.nospam
| >>
| >>
| >
|
|
