Hi Tim,
Thread 1 did spend long user time but unfortunately the log didn't
capture any clues of its high CPU's reason. The call stack just shows
the thread created a new I/O completion port listening thread and was
pending for a receiveing packet. You will find this is a very general
call stack of an ASP.net process.
00 0088ff50 77f5c024 SharedUserData!SystemCallStub+0x4
01 0088ff54 77e7594a ntdll!NtRemoveIoCompletion+0xc
02 0088ff80 792e9b2f KERNEL32!GetQueuedCompletionStatus+0x27
03 0088ffb4 77e7d33b
mscorwks!ThreadpoolMgr::CompletionPortThreadStart+0x49
04 0088ffec 00000000 KERNEL32!BaseThreadStart+0x37
GetQueuedCompletionStatus
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/filei
o/base/getqueuedcompletionstatus.asp
I suggest you check the site's IIS log and try to determine if all
aspx pages are with the same low performace problem(check the
time-taken column) or it only occurs on some specific pages, which
should be helpful to narrow down this issue.
Best regards,
WenJun Zhang
Microsoft Online Support
This posting is provided "AS IS" with no warranties, and confers no
rights.
Get Secure! -
www.microsoft.com/security >> Stay informed about: High CPU % - looking for direction