IIS deteriorates

Hi folks,



We have an occasional problem that occurs with IIS on our web server.



It doesn't happen very often but requires an IIS Reset when it does. IIS
response deteriorates but no errors written to logs. Symptoms are odd
because there's a collateral effect with a SQL Servers performance
deteriorating that doesn't make sense, as soon as as IISRESET is performed
SQL performance increases again.



The IIS crash / hang agent doesn't pick anything up as IIS doesn't actually
crash.



Has anybody come across this before?



Thanks



Paul

Re: IIS deteriorates

"Paulo" wrote in message
news:Osn94$THIHA.6068@TK2MSFTNGP02.phx.gbl...
> Hi folks,
>
>
>
> We have an occasional problem that occurs with IIS on our web server.
>
>
>
> It doesn't happen very often but requires an IIS Reset when it does. IIS
> response deteriorates but no errors written to logs. Symptoms are odd
> because there's a collateral effect with a SQL Servers performance
> deteriorating that doesn't make sense, as soon as as IISRESET is performed
> SQL performance increases again.
>
>
>
> The IIS crash / hang agent doesn't pick anything up as IIS doesn't
actually
> crash.
>
>
>
> Has anybody come across this before?
>
>

ASP or ASP.NET?

If you have an number of ASP/ASP.NET pages waiting for large and/or
intensive SQL Server queries to complete you would be running out of worker
threads thereby slowing down the IIS server. When you IISRESET the threads
waiting for SQL results a killed, SQL detects this and discards the query
processes its running, hence you see corelation between IIS and SQL
performance.

--
Anthony Jones - MVP ASP/ASP.NET

Re: IIS deteriorates

On Nov 2, 4:03 am, "Paulo" wrote:
> Hi folks,
>
> We have an occasional problem that occurs with IIS on our web server.
>
> It doesn't happen very often but requires an IIS Reset when it does. IIS
> response deteriorates but no errors written to logs. Symptoms are odd
> because there's a collateral effect with a SQL Servers performance
> deteriorating that doesn't make sense, as soon as as IISRESET is performed
> SQL performance increases again.
>
> The IIS crash / hang agent doesn't pick anything up as IIS doesn't actually
> crash.
>
> Has anybody come across this before?
>
> Thanks
>
> Paul



IIS has no relation to SQL, so their performance should not be
associated.

If they are associated, I would start checking:
1. Are IIS and SQL on the same machine. If so, is there anything that
could tie up common resources, like CPU, RAM, or HardDisk -- like anti-
virus scans locking files used by IIS/SQL applications, or a run-away
IIS application chewing up CPU/RAM that SQL needs (or vice versa)
2. If IIS and SQL are on different machines, then I would focus on the
network connectivity between IIS and SQL. As well as the IIS
application talking to SQL (as Anthony notes) which may be queuing for
legitimate (or illegimate) reasons


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//