IIS 6 - Slow Response Time

[Roseanne]

We are experiencing very slow response time in our web app. We run IIS 6 - windows 2003.

I ran iisstate.

Here's what I got. Any ideas??

Opened log file 'F:\iisstate\ou tput\IISState-812.log'

*************** ********
Starting new log output
IISState version 3.3.1

Tue Mar 13 08:26:17 2007

OS = Windows 2003 Server
Executable: w3wp.exe
PID = 812

Note: Thread times are formatted as HH:MM:SS.ms

*************** ********




Thread ID: 0
System Thread ID: d50
Kernel Time: 0:0:0.62
User Time: 0:0:0.62
Thread Status: Thread is in a WAIT state.
Thread Type: HTTP Compression Thread
# ChildEBP RetAddr
00 0006fc08 7c822124 ntdll!KiFastSys temCallRet
01 0006fc0c 77e6bad8 ntdll!NtWaitFor SingleObject+0x c
02 0006fc7c 77e6ba42 kernel32!WaitFo rSingleObjectEx +0xac
03 0006fc90 5a36467a kernel32!WaitFo rSingleObject+0 x12
04 0006fca0 5a366e63 w3dt!WP_CONTEXT ::RunMainThread Loop+0x10
05 0006fca8 5a3af41d w3dt!UlAtqStart Listen+0x2d
06 0006fcb8 5a3bc259 w3core!W3_SERVE R::StartListen+ 0xbd
07 0006ff0c 0100187c w3core!UlW3Star t+0x26e
08 0006ff44 01001a23 w3wp!wmain+0x22 a
09 0006ffc0 77e523e5 w3wp!wmainCRTSt artup+0x12b
0a 0006fff0 00000000 kernel32!BasePr ocessStart+0x23




Thread ID: 1
System Thread ID: d04
Kernel Time: 0:0:0.15
User Time: 0:0:0.0
Thread Type: Other
# ChildEBP RetAddr
00 00a3ff9c 7c821364 ntdll!KiFastSys temCallRet
01 00a3ffa0 7c81fe26 ntdll!NtDelayEx ecution+0xc
02 00a3ffb8 77e6608b ntdll!RtlpTimer Thread+0x47
03 00a3ffec 00000000 kernel32!BaseTh readStart+0x34




Thread ID: 2
System Thread ID: d0c
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Possible ASP page. Possible DCOM activity
Executing Page: ASP.dll symbols not found. Unable to locate ASP page.
Continuing with other analysis.

No remote call being made

# ChildEBP RetAddr
00 00abfe18 7c821c54 ntdll!KiFastSys temCallRet
01 00abfe1c 77c7538c ntdll!ZwReplyWa itReceivePortEx +0xc
02 00abff84 77c5778f RPCRT4!LRPC_ADD RESS::ReceiveLo tsaCalls+0x198
03 00abff8c 77c5f7dd RPCRT4!RecvLots aCallsWrapper+0 xd
04 00abffac 77c5de88 RPCRT4!BaseCach edThreadRoutine +0x9d
05 00abffb8 77e6608b RPCRT4!ThreadSt artRoutine+0x1b
06 00abffec 00000000 kernel32!BaseTh readStart+0x34




Thread ID: 3
System Thread ID: 380
Kernel Time: 0:0:0.156
User Time: 0:0:0.156
Thread Type: HTTP Listener
# ChildEBP RetAddr
00 00cbff24 7c821bf4 ntdll!KiFastSys temCallRet
01 00cbff28 77e66142 ntdll!NtRemoveI oCompletion+0xc
02 00cbff54 5a30249e kernel32!GetQue uedCompletionSt atus+0x29
03 00cbff8c 5a3026bc W3TP!THREAD_POO L_DATA::ThreadP oolThread+0x33
04 00cbffa0 5a301db9 W3TP!THREAD_POO L_DATA::ThreadP oolThread+0x24
05 00cbffb8 77e6608b W3TP!THREAD_MAN AGER::ThreadMan agerThread+0x39
06 00cbffec 00000000 kernel32!BaseTh readStart+0x34




Thread ID: 4
System Thread ID: d14
Kernel Time: 0:0:0.140
User Time: 0:0:0.140
Thread Type: HTTP Listener
# ChildEBP RetAddr
00 00cfff24 7c821bf4 ntdll!KiFastSys temCallRet
01 00cfff28 77e66142 ntdll!NtRemoveI oCompletion+0xc
02 00cfff54 5a30249e kernel32!GetQue uedCompletionSt atus+0x29
03 00cfff8c 5a3026bc W3TP!THREAD_POO L_DATA::ThreadP oolThread+0x33
04 00cfffa0 5a301db9 W3TP!THREAD_POO L_DATA::ThreadP oolThread+0x24
05 00cfffb8 77e6608b W3TP!THREAD_MAN AGER::ThreadMan agerThread+0x39
06 00cfffec 00000000 kernel32!BaseTh readStart+0x34




Thread ID: 5
System Thread ID: 838
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: HTTP Listener
# ChildEBP RetAddr
00 00d3ff24 7c821bf4 ntdll!KiFastSys temCallRet
01 00d3ff28 77e66142 ntdll!NtRemoveI oCompletion+0xc
02 00d3ff54 5a30249e kernel32!GetQue uedCompletionSt atus+0x29
03 00d3ff8c 5a3026bc W3TP!THREAD_POO L_DATA::ThreadP oolThread+0x33
04 00d3ffa0 5a301db9 W3TP!THREAD_POO L_DATA::ThreadP oolThread+0x24
05 00d3ffb8 77e6608b W3TP!THREAD_MAN AGER::ThreadMan agerThread+0x39
06 00d3ffec 00000000 kernel32!BaseTh readStart+0x34




Thread ID: 6
System Thread ID: 33c
Kernel Time: 0:0:0.0
User Time: 0:0:0.15
Thread Type: HTTP Listener
# ChildEBP RetAddr
00 00d7ff24 7c821bf4 ntdll!KiFastSys temCallRet
01 00d7ff28 77e66142 ntdll!NtRemoveI oCompletion+0xc
02 00d7ff54 5a30249e kernel32!GetQue uedCompletionSt atus+0x29
03 00d7ff8c 5a3026bc W3TP!THREAD_POO L_DATA::ThreadP oolThread+0x33
04 00d7ffa0 5a301db9 W3TP!THREAD_POO L_DATA::ThreadP oolThread+0x24
05 00d7ffb8 77e6608b W3TP!THREAD_MAN AGER::ThreadMan agerThread+0x39
06 00d7ffec 00000000 kernel32!BaseTh readStart+0x34




Thread ID: 7
System Thread ID: c04
Kernel Time: 0:0:0.0
User Time: 0:0:0.31
Thread Type: HTTP Listener
# ChildEBP RetAddr
00 00dbff24 7c821bf4 ntdll!KiFastSys temCallRet
01 00dbff28 77e66142 ntdll!NtRemoveI oCompletion+0xc
02 00dbff54 5a30249e kernel32!GetQue uedCompletionSt atus+0x29
03 00dbff8c 5a3026bc W3TP!THREAD_POO L_DATA::ThreadP oolThread+0x33
04 00dbffa0 5a301db9 W3TP!THREAD_POO L_DATA::ThreadP oolThread+0x24
05 00dbffb8 77e6608b W3TP!THREAD_MAN AGER::ThreadMan agerThread+0x39
06 00dbffec 00000000 kernel32!BaseTh readStart+0x34




Thread ID: 8
System Thread ID: bdc
Kernel Time: 0:0:0.281
User Time: 0:0:0.218
Thread Type: HTTP Listener
# ChildEBP RetAddr
00 00dfff24 7c821bf4 ntdll!KiFastSys temCallRet
01 00dfff28 77e66142 ntdll!NtRemoveI oCompletion+0xc
02 00dfff54 5a30249e kernel32!GetQue uedCompletionSt atus+0x29
03 00dfff8c 5a3026bc W3TP!THREAD_POO L_DATA::ThreadP oolThread+0x33
04 00dfffa0 5a301db9 W3TP!THREAD_POO L_DATA::ThreadP oolThread+0x24
05 00dfffb8 77e6608b W3TP!THREAD_MAN AGER::ThreadMan agerThread+0x39
06 00dfffec 00000000 kernel32!BaseTh readStart+0x34




Thread ID: 9
System Thread ID: d18
Kernel Time: 0:0:0.343
User Time: 0:0:0.234
Thread Type: HTTP Listener
# ChildEBP RetAddr
00 00e3ff24 7c821bf4 ntdll!KiFastSys temCallRet
01 00e3ff28 77e66142 ntdll!NtRemoveI oCompletion+0xc
02 00e3ff54 5a30249e kernel32!GetQue uedCompletionSt atus+0x29
03 00e3ff8c 5a3026bc W3TP!THREAD_POO L_DATA::ThreadP oolThread+0x33
04 00e3ffa0 5a301db9 W3TP!THREAD_POO L_DATA::ThreadP oolThread+0x24
05 00e3ffb8 77e6608b W3TP!THREAD_MAN AGER::ThreadMan agerThread+0x39
06 00e3ffec 00000000 kernel32!BaseTh readStart+0x34




Thread ID: 10
System Thread ID: d1c
Kernel Time: 0:0:0.296
User Time: 0:0:0.125
Thread Type: HTTP Listener
# ChildEBP RetAddr
00 00e7ff24 7c821bf4 ntdll!KiFastSys temCallRet
01 00e7ff28 77e66142 ntdll!NtRemoveI oCompletion+0xc
02 00e7ff54 5a30249e kernel32!GetQue uedCompletionSt atus+0x29
03 00e7ff8c 5a3026bc W3TP!THREAD_POO L_DATA::ThreadP oolThread+0x33
04 00e7ffa0 5a301db9 W3TP!THREAD_POO L_DATA::ThreadP oolThread+0x24
05 00e7ffb8 77e6608b W3TP!THREAD_MAN AGER::ThreadMan agerThread+0x39
06 00e7ffec 00000000 kernel32!BaseTh readStart+0x34




Thread ID: 11
System Thread ID: d20
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Status: Thread is in a WAIT state.
Thread Type: Other
# ChildEBP RetAddr
00 00f3fcec 7c822114 ntdll!KiFastSys temCallRet
01 00f3fcf0 7c83acfd ntdll!NtWaitFor MultipleObjects +0xc
02 00f3ffb8 77e6608b ntdll!RtlpWaitT hread+0x161
03 00f3ffec 00000000 kernel32!BaseTh readStart+0x34




Thread ID: 12
System Thread ID: d34
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Status: Thread is in a WAIT state.
Thread Type: HTTP Compression Thread
# ChildEBP RetAddr
00 01abfa84 7c822124 ntdll!KiFastSys temCallRet
01 01abfa88 77e6bad8 ntdll!NtWaitFor SingleObject+0x c
02 01abfaf8 77e6ba42 kernel32!WaitFo rSingleObjectEx +0xac
03 01abfb0c 5a3b8147 kernel32!WaitFo rSingleObject+0 x12
04 01abffb8 77e6608b w3core!HTTP_COM PRESSION::Compr essionThread+0x 126
05 01abffec 00000000 kernel32!BaseTh readStart+0x34




Thread ID: 13
System Thread ID: d3c
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Possible ASP page. Possible DCOM activity
Executing Page: ASP.dll symbols not found. Unable to locate ASP page.
Continuing with other analysis.

No remote call being made

# ChildEBP RetAddr
00 01affe18 7c821c54 ntdll!KiFastSys temCallRet
01 01affe1c 77c7538c ntdll!ZwReplyWa itReceivePortEx +0xc
02 01afff84 77c5778f RPCRT4!LRPC_ADD RESS::ReceiveLo tsaCalls+0x198
03 01afff8c 77c5f7dd RPCRT4!RecvLots aCallsWrapper+0 xd
04 01afffac 77c5de88 RPCRT4!BaseCach edThreadRoutine +0x9d
05 01afffb8 77e6608b RPCRT4!ThreadSt artRoutine+0x1b
06 01afffec 00000000 kernel32!BaseTh readStart+0x34




Thread ID: 14
System Thread ID: 278
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Other
# ChildEBP RetAddr
00 01b3ff8c 7c821364 ntdll!KiFastSys temCallRet
01 01b3ff90 7c815267 ntdll!NtDelayEx ecution+0xc
02 01b3ffb8 77e6608b ntdll!RtlpIOWor kerThread+0x3f
03 01b3ffec 00000000 kernel32!BaseTh readStart+0x34




Thread ID: 15
System Thread ID: da0
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Other
# ChildEBP RetAddr
00 01c2fd90 7c821364 ntdll!KiFastSys temCallRet
01 01c2fd94 77e41ea7 ntdll!NtDelayEx ecution+0xc
02 01c2fdfc 77e424c1 kernel32!SleepE x+0x68
03 01c2fe0c 791bf4f9 kernel32!Sleep+ 0xf
04 01c2ffb8 77e6608b mscorsvr+0xf4f9
05 01c2ffec 00000000 kernel32!BaseTh readStart+0x34
GetContextState failed, 0x8007001F
GetContextState failed, 0x8007001F
GetContextState failed, 0x8007001F




Thread ID: 16
System Thread ID: 0
Kernel Time: 0:0:3.312
User Time: 0:0:53.265
GetContextState failed, 0x8007001F

[kenobewan]

IISState is a really old tool you should consider using Debug Diag. Do you have an actual memory dump?

When W3wp.exe spikes to 100%, this generally points to a infinite loop in your code somewhere or an AV (access violation). Are you using On Error Resume Next in your code? If so, comment all instances of this line of code & you should start to see where the problems lie. Also, does the server CPU stay spiked or does it return to normal levels on its own? Does an IISReset fix the problem? Check the versions of anything that you are running as some products are known to be very buggy under IIS 6.

What I would suggest you do is download & use Debug Diag to grab a memory dump and then run an analysis on the memory dump - see this article on using Debug Diagnostics:
Using the Debug Diagnostics Tool

[Roseanne]

Will do - thanks