Re: w3wp.exe takes 100% processor

From: Pat [MSFT] (patfilot_at_online.microsoft.com)
Date: 12/28/04

Next message: David Wang [Msft]: "Re: Uploading Site Changes / How To"
Previous message: J. Knapp: "RE: Taking forever to start processing"
In reply to: tapman: "Re: w3wp.exe takes 100% processor"
Next in thread: tapman: "Re: w3wp.exe takes 100% processor"
Reply: tapman: "Re: w3wp.exe takes 100% processor"
Messages sorted by: [ date ] [ thread ]

Date: Tue, 28 Dec 2004 09:47:34 -0800

Be careful when using a stress test. Most stress runs that I have seen are
actually Denial of Service attacks.

A typical web user will request 1 asp page every 60 seconds. So, to test
500 users, you would use 500/60 ~ 9 (rounding up) non-pausing users or
configure the stress tool to delay 60 seconds between requests. If you have
a financial services app, the ratio is 1 req/100 sec. For content only
(think x-box.com) it's closer to 1/35 sec. Testing 500 users (no pause) is
actually testing 3000 users in real life. You can check your site using
Perfmon to get the ratio that would represent real-world for you
(ASP:Requests/Sec, Web:Current Connections). Note that ASP requests are not
the same rate as GET requests. A single ASP request can generate 20+ GET
requests (images, etc.).

>From the log, only one thread was actually running, which implies that you
have ASP sessions enabled and that the script is executing under a single
session.

Pat\

"tapman" <tapman@discussions.microsoft.com> wrote in message
news:3B3C21F9-AF04-481E-91FE-23D622D181DF@microsoft.com...
> Dear Pat,
>
> Thanks for the reply. The CPU utilisation of w3wp rises when users are
> increased to more than 30-35 and all of them use this test.asp file only.
>
> Since I had cpu utilisation of w3wp, I created test.asp with only one sql
> query which simply puts query as "select * from table name" where table
> has
> no records. All the page does is returns "found" or "none" text. It is a
> very
> simple sql query coded in ASP which, when run in query analyzer does not
> take
> any cpu utilisation.
>
> The log I gave you is when 500 users are connected to it. (For all this
> testing I make use of Microsoft Web Application Stress Tool which is
> configured to send 500 requests to test.asp page only.)
>
> If instead of this test.asp, I use any other pages to be browsed by this
> Tool, it does not take more than 15-20 users. Beyond that, the cpu of w3wp
> takes maximum.
>
> The system I am using for testing is Pentium 4 2.8 GHz Hyper threading. I
> don't think it is incapable of handling more than 20 users who browse
> different content of web site.
>
> All web site content is in ASP. A small comparison of test.asp with other
> pages, I can tell you that other pages have atleast 5-6 queries to
> database
> each. That also, complex ones and not as simple as "select * from
> tablename".
> This itself shows why I only chose to use simple ASP page as test.asp to
> test
> and check whether problem is with ASP pages and it's coding or with w3wp
> itself.
>
> If it was bad programming, it would have reflected in test.asp and in this
> case w3wp should not have had so much of high cpu utilisation. I tested
> with
> html content and it worked fine for almost 3000 users.
>
> Hence I can deduce that something is there in server processing ASP
> content
> which is problematic. Queries which I run on ASP pages, if I run on SQL
> Query
> analyzer, never generate so much of load.
>
> To furthur make sure of this problem, I used another test machine to be
> SQL
> server and configured DSNs accordingly so that test.asp queries are not
> run
> on this server and are run on other database server. In this case also,
> the
> database processor utilisation was normal while this server showed 100%
> cpu
> utilisation by w3wp. The log I have given you are taken in abovementioned
> environment.
>
> Thanks & Regards,
>
> Tapan Maniar.
>
> "Pat [MSFT]" wrote:
>
>> Thread 87 is the only one doing any work. It has used 2 seconds of CPU:
>>
>> Thread ID: 87
>> System Thread ID: 7cc
>> Kernel Time: 0:0:0.609
>> User Time: 0:0:2.406 <--CPU time used since thread creation
>>
>> So, it is possible that the page running on that thread
>> (D:\SAFFRONART\AUCTION\AUCTIONW04\TEST.ASP) is the cause of the issue.
>> But
>> for a 100% CPU issue, I usually expect the thread times to be much
>> higher.
>>
>> How long had the CPU been at 100% when you took the log? You may have to
>> do
>> a few to determine the culprit. Just look at the thread times and find
>> the
>> one with the most CPU. If you consistently see the same page associated
>> with the CPU issue, then that is probably where the problem is.
>>
>>
>> Pat
>>
>> "tapman" <tapman@discussions.microsoft.com> wrote in message
>> news:5B37D66C-6E81-4CFF-B2CB-F86F86E9802C@microsoft.com...
>> > iisstate log part 2
>> >
>> >
>> >
>> > Thread ID: 82
>> > System Thread ID: 62c
>> > Kernel Time: 0:0:0.468
>> > User Time: 0:0:2.234
>> > Thread Status: Thread is in a WAIT state.
>> > Thread Type: Idle ASP thread
>> > # ChildEBP RetAddr
>> > 00 07e9fdcc 77f4372d SharedUserData!SystemCallStub+0x4
>> > 01 07e9fdd0 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
>> > 02 07e9fe78 77d076f5 kernel32!WaitForMultipleObjectsEx+0x11a
>> > 03 07e9fed4 77d077f5 USER32!RealMsgWaitForMultipleObjectsEx+0x13f
>> > 04 07e9fef0 756342a4 USER32!MsgWaitForMultipleObjects+0x1d
>> > 05 07e9ff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x1e3
>> > 06 07e9ffb8 77e4a990 msvcrt!_endthreadex+0x95
>> > 07 07e9ffec 00000000 kernel32!BaseThreadStart+0x34
>> >
>> >
>> >
>> >
>> > Thread ID: 83
>> > System Thread ID: 630
>> > Kernel Time: 0:0:0.437
>> > User Time: 0:0:2.781
>> > Thread Status: Thread is in a WAIT state.
>> > Thread Type: Idle ASP thread
>> > # ChildEBP RetAddr
>> > 00 07edfdcc 77f4372d SharedUserData!SystemCallStub+0x4
>> > 01 07edfdd0 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
>> > 02 07edfe78 77d076f5 kernel32!WaitForMultipleObjectsEx+0x11a
>> > 03 07edfed4 77d077f5 USER32!RealMsgWaitForMultipleObjectsEx+0x13f
>> > 04 07edfef0 756342a4 USER32!MsgWaitForMultipleObjects+0x1d
>> > 05 07edff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x1e3
>> > 06 07edffb8 77e4a990 msvcrt!_endthreadex+0x95
>> > 07 07edffec 00000000 kernel32!BaseThreadStart+0x34
>> >
>> >
>> >
>> >
>> > Thread ID: 84
>> > System Thread ID: 61c
>> > Kernel Time: 0:0:0.609
>> > User Time: 0:0:2.578
>> > Thread Status: Thread is in a WAIT state.
>> > Thread Type: Idle ASP thread
>> > # ChildEBP RetAddr
>> > 00 07f1fdcc 77f4372d SharedUserData!SystemCallStub+0x4
>> > 01 07f1fdd0 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
>> > 02 07f1fe78 77d076f5 kernel32!WaitForMultipleObjectsEx+0x11a
>> > 03 07f1fed4 77d077f5 USER32!RealMsgWaitForMultipleObjectsEx+0x13f
>> > 04 07f1fef0 756342a4 USER32!MsgWaitForMultipleObjects+0x1d
>> > 05 07f1ff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x1e3
>> > 06 07f1ffb8 77e4a990 msvcrt!_endthreadex+0x95
>> > 07 07f1ffec 00000000 kernel32!BaseThreadStart+0x34
>> >
>> >
>> >
>> >
>> > Thread ID: 85
>> > System Thread ID: 7a4
>> > Kernel Time: 0:0:0.375
>> > User Time: 0:0:2.546
>> > Thread Status: Thread is in a WAIT state.
>> > Thread Type: Idle ASP thread
>> > # ChildEBP RetAddr
>> > 00 081dfdcc 77f4372d SharedUserData!SystemCallStub+0x4
>> > 01 081dfdd0 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
>> > 02 081dfe78 77d076f5 kernel32!WaitForMultipleObjectsEx+0x11a
>> > 03 081dfed4 77d077f5 USER32!RealMsgWaitForMultipleObjectsEx+0x13f
>> > 04 081dfef0 756342a4 USER32!MsgWaitForMultipleObjects+0x1d
>> > 05 081dff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x1e3
>> > 06 081dffb8 77e4a990 msvcrt!_endthreadex+0x95
>> > 07 081dffec 00000000 kernel32!BaseThreadStart+0x34
>> >
>> >
>> >
>> >
>> > Thread ID: 86
>> > System Thread ID: 7a8
>> > Kernel Time: 0:0:0.562
>> > User Time: 0:0:2.578
>> > Thread Status: Thread is in a WAIT state.
>> > Thread Type: Idle ASP thread
>> > # ChildEBP RetAddr
>> > 00 0821fdcc 77f4372d SharedUserData!SystemCallStub+0x4
>> > 01 0821fdd0 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
>> > 02 0821fe78 77d076f5 kernel32!WaitForMultipleObjectsEx+0x11a
>> > 03 0821fed4 77d077f5 USER32!RealMsgWaitForMultipleObjectsEx+0x13f
>> > 04 0821fef0 756342a4 USER32!MsgWaitForMultipleObjects+0x1d
>> > 05 0821ff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x1e3
>> > 06 0821ffb8 77e4a990 msvcrt!_endthreadex+0x95
>> > 07 0821ffec 00000000 kernel32!BaseThreadStart+0x34
>> >
>> >
>> >
>> >
>> > Thread ID: 87
>> > System Thread ID: 7cc
>> > Kernel Time: 0:0:0.609
>> > User Time: 0:0:2.406
>> > Thread Type: SQL Query. Possible ASP page
>> > Executing Page: D:\SAFFRONART\AUCTION\AUCTIONW04\TEST.ASP
>> >
>> > # ChildEBP RetAddr
>> > 00 0825eb98 02d5cdb2 sqloledb!CRowsetProps::CalculateSupport+0x77
>> > 01 0825ebb4 02d58f5c sqloledb!CRowsetProps::FindCapableCC+0x9e
>> > 02 0825ec24 02d59216 sqloledb!CCommand::Execute+0x715
>> > 03 0825ec64 0291a141 sqloledb!CImpICommandText::Execute+0xf3
>> > 04 0825eca4 02919da8 msado15!CConnection::Execute+0x9b
>> > 05 0825ee64 02919c47 msado15!_ExecuteAsync+0x17e
>> > 06 0825ee74 029199ee msado15!ExecuteAsync+0x1f
>> > 07 0825ef40 02919bee msado15!CQuery::Execute+0xa25
>> > 08 0825efa0 0294da97 msado15!CCommand::_Execute+0x147
>> > 09 0825f018 029486a5 msado15!CConnection::OpenRecordset+0xd7
>> > 0a 0825f158 029316ac msado15!CConnection::Execute+0x3f5
>> > 0b 0825f3dc 7348b427 msado15!CConnection::Invoke+0x8ba
>> > 0c 0825f430 7347f39c vbscript!CatchIDispatchInvoke+0x46
>> > 0d 0825f47c 7346368c vbscript!IDispatchInvoke+0x95
>> > 0e 0825f590 73462f95 vbscript!InvokeDispatch+0x138
>> > 0f 0825f5b4 73465d5b vbscript!InvokeByName+0x40
>> > 10 0825f890 73463c33 vbscript!CScriptRuntime::Run+0x2581
>> > 11 0825f994 73463d42 vbscript!CScriptEntryPoint::Call+0x65
>> > 12 0825f9f8 73464081 vbscript!CSession::Execute+0xb6
>> > 13 0825fa48 734640ee vbscript!COleScript::ExecutePendingScripts+0x14a
>> > 14 0825fa64 709e5e87 vbscript!COleScript::SetScriptState+0x14e
>> > 15 0825fa90 709e5ee1 asp!CActiveScriptEngine::TryCall+0x17
>> > 16 0825facc 709e5f21 asp!CActiveScriptEngine::Call+0x31
>> > 17 0825fae0 709e6227 asp!CallScriptFunctionOfEngine+0x21
>> > 18 0825fb18 709e6393 asp!ExecuteRequest+0x138
>> > 19 0825fb60 709e5573 asp!Execute+0x16a
>> > 1a 0825fbb0 709e5726 asp!CHitObj::ViperAsyncCallback+0x3ec
>> > 1b 0825fbd0 75633107 asp!CViperAsyncRequest::OnCall+0x8c
>> > 1c 0825fbec 77204c67
>> > comsvcs!CSTAActivityWork::STAActivityWorkHelper+0x30
>> > 1d 0825fc38 7720539a ole32!EnterForCallback+0xc0
>> > 1e 0825fd98 771e03a4 ole32!SwitchForCallback+0x194
>> > 1f 0825fdc4 771c7e10 ole32!PerformCallback+0x52
>> > 20 0825fe48 77207984
>> > ole32!CObjectContext::InternalContextCallback+0x140
>> > 21 0825fe68 756332b3 ole32!CObjectContext::DoCallback+0x1a
>> > 22 0825fed4 756337ad comsvcs!CSTAActivityWork::DoWork+0x137
>> > 23 0825fee8 75633f71 comsvcs!CSTAThread::DoWork+0x14
>> > 24 0825ff04 7563423b comsvcs!CSTAThread::ProcessQueueWork+0x30
>> > 25 0825ff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x17a
>> > 26 0825ffb8 77e4a990 msvcrt!_endthreadex+0x95
>> > 27 0825ffec 00000000 kernel32!BaseThreadStart+0x34
>> >
>> >
>> >
>> >
>> > Thread ID: 88
>> > System Thread ID: 7c8
>> > Kernel Time: 0:0:0.609
>> > User Time: 0:0:2.640
>> > Thread Status: Thread is in a WAIT state.
>> > Thread Type: Idle ASP thread
>> > # ChildEBP RetAddr
>> > 00 0829fdcc 77f4372d SharedUserData!SystemCallStub+0x4
>> > 01 0829fdd0 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
>> > 02 0829fe78 77d076f5 kernel32!WaitForMultipleObjectsEx+0x11a
>> > 03 0829fed4 77d077f5 USER32!RealMsgWaitForMultipleObjectsEx+0x13f
>> > 04 0829fef0 756342a4 USER32!MsgWaitForMultipleObjects+0x1d
>> > 05 0829ff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x1e3
>> > 06 0829ffb8 77e4a990 msvcrt!_endthreadex+0x95
>> > 07 0829ffec 00000000 kernel32!BaseThreadStart+0x34
>> >
>> >
>> >
>> >
>> > Thread ID: 89
>> > System Thread ID: 64c
>> > Kernel Time: 0:0:0.406
>> > User Time: 0:0:2.578
>> > Thread Status: Thread is in a WAIT state.
>> > Thread Type: Idle ASP thread
>> > # ChildEBP RetAddr
>> > 00 0851fdcc 77f4372d SharedUserData!SystemCallStub+0x4
>> > 01 0851fdd0 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
>> > 02 0851fe78 77d076f5 kernel32!WaitForMultipleObjectsEx+0x11a
>> > 03 0851fed4 77d077f5 USER32!RealMsgWaitForMultipleObjectsEx+0x13f
>> > 04 0851fef0 756342a4 USER32!MsgWaitForMultipleObjects+0x1d
>> > 05 0851ff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x1e3
>> > 06 0851ffb8 77e4a990 msvcrt!_endthreadex+0x95
>> > 07 0851ffec 00000000 kernel32!BaseThreadStart+0x34
>> >
>> >
>> >
>> >
>> > Thread ID: 90
>> > System Thread ID: 67c
>> > Kernel Time: 0:0:0.421
>> > User Time: 0:0:2.234
>> > Thread Status: Thread is in a WAIT state.
>> > Thread Type: Idle ASP thread
>> > # ChildEBP RetAddr
>> > 00 0855fdcc 77f4372d SharedUserData!SystemCallStub+0x4
>> > 01 0855fdd0 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
>> > 02 0855fe78 77d076f5 kernel32!WaitForMultipleObjectsEx+0x11a
>> > 03 0855fed4 77d077f5 USER32!RealMsgWaitForMultipleObjectsEx+0x13f
>> > 04 0855fef0 756342a4 USER32!MsgWaitForMultipleObjects+0x1d
>> > 05 0855ff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x1e3
>> > 06 0855ffb8 77e4a990 msvcrt!_endthreadex+0x95
>> > 07 0855ffec 00000000 kernel32!BaseThreadStart+0x34
>> >
>> >
>> >
>> >
>> > Thread ID: 91
>> > System Thread ID: 524
>> > Kernel Time: 0:0:0.484
>> > User Time: 0:0:2.703
>> > Thread Status: Thread is in a WAIT state.
>> > Thread Type: Idle ASP thread
>> > # ChildEBP RetAddr
>> > 00 0859fdcc 77f4372d SharedUserData!SystemCallStub+0x4
>> > 01 0859fdd0 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
>> > 02 0859fe78 77d076f5 kernel32!WaitForMultipleObjectsEx+0x11a
>> > 03 0859fed4 77d077f5 USER32!RealMsgWaitForMultipleObjectsEx+0x13f
>> > 04 0859fef0 756342a4 USER32!MsgWaitForMultipleObjects+0x1d
>> > 05 0859ff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x1e3
>> > 06 0859ffb8 77e4a990 msvcrt!_endthreadex+0x95
>> > 07 0859ffec 00000000 kernel32!BaseThreadStart+0x34
>> >
>> >
>> >
>> >
>> > Thread ID: 92
>> > System Thread ID: 8b4
>> > Kernel Time: 0:0:0.421
>> > User Time: 0:0:2.187
>> > Thread Status: Thread is in a WAIT state.
>> > Thread Type: Idle ASP thread
>> > # ChildEBP RetAddr
>> > 00 085dfdcc 77f4372d SharedUserData!SystemCallStub+0x4
>> > 01 085dfdd0 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
>> > 02 085dfe78 77d076f5 kernel32!WaitForMultipleObjectsEx+0x11a
>> > 03 085dfed4 77d077f5 USER32!RealMsgWaitForMultipleObjectsEx+0x13f
>> > 04 085dfef0 756342a4 USER32!MsgWaitForMultipleObjects+0x1d
>> > 05 085dff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x1e3
>> > 06 085dffb8 77e4a990 msvcrt!_endthreadex+0x95
>> > 07 085dffec 00000000 kernel32!BaseThreadStart+0x34
>> >
>> >
>> >
>> >
>> > Thread ID: 93
>> > System Thread ID: 930
>> > Kernel Time: 0:0:0.593
>> > User Time: 0:0:2.468
>> > Thread Status: Thread is in a WAIT state.
>> > Thread Type: Idle ASP thread
>> > # ChildEBP RetAddr
>> > 00 0889fdcc 77f4372d SharedUserData!SystemCallStub+0x4
>> > 01 0889fdd0 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
>> > 02 0889fe78 77d076f5 kernel32!WaitForMultipleObjectsEx+0x11a
>> > 03 0889fed4 77d077f5 USER32!RealMsgWaitForMultipleObjectsEx+0x13f
>> > 04 0889fef0 756342a4 USER32!MsgWaitForMultipleObjects+0x1d
>> > 05 0889ff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x1e3
>> > 06 0889ffb8 77e4a990 msvcrt!_endthreadex+0x95
>> > 07 0889ffec 00000000 kernel32!BaseThreadStart+0x34
>> >
>> >
>> >
>> >
>> > Thread ID: 94
>> > System Thread ID: 914
>> > Kernel Time: 0:0:0.500
>> > User Time: 0:0:2.156
>> > Thread Status: Thread is in a WAIT state.
>> > Thread Type: Idle ASP thread
>> > # ChildEBP RetAddr
>> > 00 088dfdcc 77f4372d SharedUserData!SystemCallStub+0x4
>> > 01 088dfdd0 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
>> > 02 088dfe78 77d076f5 kernel32!WaitForMultipleObjectsEx+0x11a
>> > 03 088dfed4 77d077f5 USER32!RealMsgWaitForMultipleObjectsEx+0x13f
>> > 04 088dfef0 756342a4 USER32!MsgWaitForMultipleObjects+0x1d
>> > 05 088dff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x1e3
>> > 06 088dffb8 77e4a990 msvcrt!_endthreadex+0x95
>> > 07 088dffec 00000000 kernel32!BaseThreadStart+0x34
>> >
>> >
>> >
>> >
>> > Thread ID: 95
>> > System Thread ID: 334
>> > Kernel Time: 0:0:0.453
>> > User Time: 0:0:2.109
>> > Thread Status: Thread is in a WAIT state.
>> > Thread Type: Idle ASP thread
>> > # ChildEBP RetAddr
>> > 00 0891fdcc 77f4372d SharedUserData!SystemCallStub+0x4
>> > 01 0891fdd0 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
>> > 02 0891fe78 77d076f5 kernel32!WaitForMultipleObjectsEx+0x11a
>> > 03 0891fed4 77d077f5 USER32!RealMsgWaitForMultipleObjectsEx+0x13f
>> > 04 0891fef0 756342a4 USER32!MsgWaitForMultipleObjects+0x1d
>> > 05 0891ff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x1e3
>> > 06 0891ffb8 77e4a990 msvcrt!_endthreadex+0x95
>> > 07 0891ffec 00000000 kernel32!BaseThreadStart+0x34
>> >
>> >
>> >
>> >
>> > Thread ID: 96
>> > System Thread ID: 59c
>> > Kernel Time: 0:0:0.546
>> > User Time: 0:0:2.640
>> > Thread Status: Thread is in a WAIT state.
>> > Thread Type: Idle ASP thread
>> > # ChildEBP RetAddr
>> > 00 0895fdcc 77f4372d SharedUserData!SystemCallStub+0x4
>> > 01 0895fdd0 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
>> > 02 0895fe78 77d076f5 kernel32!WaitForMultipleObjectsEx+0x11a
>> > 03 0895fed4 77d077f5 USER32!RealMsgWaitForMultipleObjectsEx+0x13f
>> > 04 0895fef0 756342a4 USER32!MsgWaitForMultipleObjects+0x1d
>> > 05 0895ff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x1e3
>> > 06 0895ffb8 77e4a990 msvcrt!_endthreadex+0x95
>> > 07 0895ffec 00000000 kernel32!BaseThreadStart+0x34
>> >
>> >
>> >
>> >
>> > Thread ID: 97
>> > System Thread ID: 728
>> > Kernel Time: 0:0:1.953
>> > User Time: 0:0:0.296
>> > Thread Type: HTTP Listener
>> > # ChildEBP RetAddr
>> > 00 09a3ff28 77f430c7 SharedUserData!SystemCallStub+0x4
>> > 01 09a3ff2c 77e430bc ntdll!ZwRemoveIoCompletion+0xc
>> > 02 09a3ff58 5a302360 kernel32!GetQueuedCompletionStatus+0x27
>> > 03 09a3ff90 5a302531 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x31
>> > 04 09a3ffa4 5a301d27 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x21
>> > 05 09a3ffb8 77e4a990 W3TP!THREAD_MANAGER::ThreadManagerThread+0x35
>> > 06 09a3ffec 00000000 kernel32!BaseThreadStart+0x34
>> >
>> >
>> >
>> >
>> > Thread ID: 98
>> > System Thread ID: 98c
>> > Kernel Time: 0:0:0.390
>> > User Time: 0:0:2.0
>> > Thread Status: Thread is in a WAIT state.
>> > Thread Type: Idle ASP thread
>> > # ChildEBP RetAddr
>> > 00 09bbfdcc 77f4372d SharedUserData!SystemCallStub+0x4
>> > 01 09bbfdd0 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
>> > 02 09bbfe78 77d076f5 kernel32!WaitForMultipleObjectsEx+0x11a
>> > 03 09bbfed4 77d077f5 USER32!RealMsgWaitForMultipleObjectsEx+0x13f
>> > 04 09bbfef0 756342a4 USER32!MsgWaitForMultipleObjects+0x1d
>> > 05 09bbff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x1e3
>> > 06 09bbffb8 77e4a990 msvcrt!_endthreadex+0x95
>> > 07 09bbffec 00000000 kernel32!BaseThreadStart+0x34
>> >
>> >
>> >
>> >
>> > Thread ID: 99
>> > System Thread ID: a18
>> > Kernel Time: 0:0:0.375
>> > User Time: 0:0:1.625
>> > Thread Status: Thread is in a WAIT state.
>> > Thread Type: Idle ASP thread
>> > # ChildEBP RetAddr
>> > 00 09bffdcc 77f4372d SharedUserData!SystemCallStub+0x4
>> > 01 09bffdd0 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
>> > 02 09bffe78 77d076f5 kernel32!WaitForMultipleObjectsEx+0x11a
>> > 03 09bffed4 77d077f5 USER32!RealMsgWaitForMultipleObjectsEx+0x13f
>> > 04 09bffef0 756342a4 USER32!MsgWaitForMultipleObjects+0x1d
>> > 05 09bfff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x1e3
>> > 06 09bfffb8 77e4a990 msvcrt!_endthreadex+0x95
>> > 07 09bfffec 00000000 kernel32!BaseThreadStart+0x34
>> >
>> >
>> >
>> >
>> > Thread ID: 100
>> > System Thread ID: a2c
>> > Kernel Time: 0:0:1.671
>> > User Time: 0:0:0.406
>> > Thread Type: HTTP Listener
>> > # ChildEBP RetAddr
>> > 00 09c3ff28 77f430c7 SharedUserData!SystemCallStub+0x4
>> > 01 09c3ff2c 77e430bc ntdll!ZwRemoveIoCompletion+0xc
>> > 02 09c3ff58 5a302360 kernel32!GetQueuedCompletionStatus+0x27
>> > 03 09c3ff90 5a302531 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x31
>> > 04 09c3ffa4 5a301d27 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x21
>> > 05 09c3ffb8 77e4a990 W3TP!THREAD_MANAGER::ThreadManagerThread+0x35
>> > 06 09c3ffec 00000000 kernel32!BaseThreadStart+0x34
>> >
>> >
>> >
>> >
>> > Thread ID: 101
>> > System Thread ID: a50
>> > Kernel Time: 0:0:1.484
>> > User Time: 0:0:0.531
>> > Thread Type: HTTP Listener
>> > # ChildEBP RetAddr
>> > 00 09dbff28 77f430c7 SharedUserData!SystemCallStub+0x4
>> > 01 09dbff2c 77e430bc ntdll!ZwRemoveIoCompletion+0xc
>> > 02 09dbff58 5a302360 kernel32!GetQueuedCompletionStatus+0x27
>> > 03 09dbff90 5a302531 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x31
>> > 04 09dbffa4 5a301d27 W3TP!THREAD_POOL_DATA::ThreadPoolThread+0x21
>> > 05 09dbffb8 77e4a990 W3TP!THREAD_MANAGER::ThreadManagerThread+0x35
>> > 06 09dbffec 00000000 kernel32!BaseThreadStart+0x34
>> >
>> >
>> >
>> >
>> > Thread ID: 102
>> > System Thread ID: a6c
>> > Kernel Time: 0:0:0.437
>> > User Time: 0:0:2.140
>> > Thread Status: Thread is in a WAIT state.
>> > Thread Type: Idle ASP thread
>> > # ChildEBP RetAddr
>> > 00 09ebfdcc 77f4372d SharedUserData!SystemCallStub+0x4
>> > 01 09ebfdd0 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
>> > 02 09ebfe78 77d076f5 kernel32!WaitForMultipleObjectsEx+0x11a
>> > 03 09ebfed4 77d077f5 USER32!RealMsgWaitForMultipleObjectsEx+0x13f
>> > 04 09ebfef0 756342a4 USER32!MsgWaitForMultipleObjects+0x1d
>> > 05 09ebff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x1e3
>> > 06 09ebffb8 77e4a990 msvcrt!_endthreadex+0x95
>> > 07 09ebffec 00000000 kernel32!BaseThreadStart+0x34
>> >
>> >
>> >
>> >
>> > Thread ID: 103
>> > System Thread ID: a7c
>> > Kernel Time: 0:0:0.281
>> > User Time: 0:0:1.890
>> > Thread Status: Thread is in a WAIT state.
>> > Thread Type: Idle ASP thread
>> > # ChildEBP RetAddr
>> > 00 09effdcc 77f4372d SharedUserData!SystemCallStub+0x4
>> > 01 09effdd0 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
>> > 02 09effe78 77d076f5 kernel32!WaitForMultipleObjectsEx+0x11a
>> > 03 09effed4 77d077f5 USER32!RealMsgWaitForMultipleObjectsEx+0x13f
>> > 04 09effef0 756342a4 USER32!MsgWaitForMultipleObjects+0x1d
>> > 05 09efff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x1e3
>> > 06 09efffb8 77e4a990 msvcrt!_endthreadex+0x95
>> > 07 09efffec 00000000 kernel32!BaseThreadStart+0x34
>> >
>> >
>> >
>> >
>> > Thread ID: 104
>> > System Thread ID: a84
>> > Kernel Time: 0:0:0.312
>> > User Time: 0:0:1.765
>> > Thread Status: Thread is in a WAIT state.
>> > Thread Type: Idle ASP thread
>> > # ChildEBP RetAddr
>> > 00 09f3fdcc 77f4372d SharedUserData!SystemCallStub+0x4
>> > 01 09f3fdd0 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
>> > 02 09f3fe78 77d076f5 kernel32!WaitForMultipleObjectsEx+0x11a
>> > 03 09f3fed4 77d077f5 USER32!RealMsgWaitForMultipleObjectsEx+0x13f
>> > 04 09f3fef0 756342a4 USER32!MsgWaitForMultipleObjects+0x1d
>> > 05 09f3ff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x1e3
>> > 06 09f3ffb8 77e4a990 msvcrt!_endthreadex+0x95
>> > 07 09f3ffec 00000000 kernel32!BaseThreadStart+0x34
>> >
>> >
>> >
>> >
>> > Thread ID: 105
>> > System Thread ID: a8c
>> > Kernel Time: 0:0:0.328
>> > User Time: 0:0:1.921
>> > Thread Status: Thread is in a WAIT state.
>> > Thread Type: Idle ASP thread
>> > # ChildEBP RetAddr
>> > 00 09f7fdcc 77f4372d SharedUserData!SystemCallStub+0x4
>> > 01 09f7fdd0 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
>> > 02 09f7fe78 77d076f5 kernel32!WaitForMultipleObjectsEx+0x11a
>> > 03 09f7fed4 77d077f5 USER32!RealMsgWaitForMultipleObjectsEx+0x13f
>> > 04 09f7fef0 756342a4 USER32!MsgWaitForMultipleObjects+0x1d
>> > 05 09f7ff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x1e3
>> > 06 09f7ffb8 77e4a990 msvcrt!_endthreadex+0x95
>> > 07 09f7ffec 00000000 kernel32!BaseThreadStart+0x34
>> >
>> >
>> >
>> >
>> > Thread ID: 106
>> > System Thread ID: ad0
>> > Kernel Time: 0:0:0.406
>> > User Time: 0:0:1.515
>> > Thread Status: Thread is in a WAIT state.
>> > Thread Type: Idle ASP thread
>> > # ChildEBP RetAddr
>> > 00 0a23fdcc 77f4372d SharedUserData!SystemCallStub+0x4
>> > 01 0a23fdd0 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
>> > 02 0a23fe78 77d076f5 kernel32!WaitForMultipleObjectsEx+0x11a
>> > 03 0a23fed4 77d077f5 USER32!RealMsgWaitForMultipleObjectsEx+0x13f
>> > 04 0a23fef0 756342a4 USER32!MsgWaitForMultipleObjects+0x1d
>> > 05 0a23ff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x1e3
>> > 06 0a23ffb8 77e4a990 msvcrt!_endthreadex+0x95
>> > 07 0a23ffec 00000000 kernel32!BaseThreadStart+0x34
>> >
>> >
>> >
>> >
>> > Thread ID: 107
>> > System Thread ID: acc
>> > Kernel Time: 0:0:0.437
>> > User Time: 0:0:1.687
>> > Thread Status: Thread is in a WAIT state.
>> > Thread Type: Idle ASP thread
>> > # ChildEBP RetAddr
>> > 00 0a27fdcc 77f4372d SharedUserData!SystemCallStub+0x4
>> > 01 0a27fdd0 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
>> > 02 0a27fe78 77d076f5 kernel32!WaitForMultipleObjectsEx+0x11a
>> > 03 0a27fed4 77d077f5 USER32!RealMsgWaitForMultipleObjectsEx+0x13f
>> > 04 0a27fef0 756342a4 USER32!MsgWaitForMultipleObjects+0x1d
>> > 05 0a27ff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x1e3
>> > 06 0a27ffb8 77e4a990 msvcrt!_endthreadex+0x95
>> > 07 0a27ffec 00000000 kernel32!BaseThreadStart+0x34
>> >
>> >
>> >
>> >
>> > Thread ID: 108
>> > System Thread ID: af0
>> > Kernel Time: 0:0:0.265
>> > User Time: 0:0:1.640
>> > Thread Status: Thread is in a WAIT state.
>> > Thread Type: Idle ASP thread
>> > # ChildEBP RetAddr
>> > 00 0a2bfdcc 77f4372d SharedUserData!SystemCallStub+0x4
>> > 01 0a2bfdd0 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
>> > 02 0a2bfe78 77d076f5 kernel32!WaitForMultipleObjectsEx+0x11a
>> > 03 0a2bfed4 77d077f5 USER32!RealMsgWaitForMultipleObjectsEx+0x13f
>> > 04 0a2bfef0 756342a4 USER32!MsgWaitForMultipleObjects+0x1d
>> > 05 0a2bff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x1e3
>> > 06 0a2bffb8 77e4a990 msvcrt!_endthreadex+0x95
>> > 07 0a2bffec 00000000 kernel32!BaseThreadStart+0x34
>> >
>> >
>> >
>> >
>> > Thread ID: 109
>> > System Thread ID: b0c
>> > Kernel Time: 0:0:0.328
>> > User Time: 0:0:1.953
>> > Thread Status: Thread is in a WAIT state.
>> > Thread Type: Idle ASP thread
>> > # ChildEBP RetAddr
>> > 00 0a2ffdcc 77f4372d SharedUserData!SystemCallStub+0x4
>> > 01 0a2ffdd0 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
>> > 02 0a2ffe78 77d076f5 kernel32!WaitForMultipleObjectsEx+0x11a
>> > 03 0a2ffed4 77d077f5 USER32!RealMsgWaitForMultipleObjectsEx+0x13f
>> > 04 0a2ffef0 756342a4 USER32!MsgWaitForMultipleObjects+0x1d
>> > 05 0a2fff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x1e3
>> > 06 0a2fffb8 77e4a990 msvcrt!_endthreadex+0x95
>> > 07 0a2fffec 00000000 kernel32!BaseThreadStart+0x34
>> >
>> >
>> >
>> >
>> > Thread ID: 110
>> > System Thread ID: b14
>> > Kernel Time: 0:0:0.546
>> > User Time: 0:0:1.937
>> > Thread Status: Thread is in a WAIT state.
>> > Thread Type: Idle ASP thread
>> > # ChildEBP RetAddr
>> > 00 0a33fdcc 77f4372d SharedUserData!SystemCallStub+0x4
>> > 01 0a33fdd0 77e41bfa ntdll!NtWaitForMultipleObjects+0xc
>> > 02 0a33fe78 77d076f5 kernel32!WaitForMultipleObjectsEx+0x11a
>> > 03 0a33fed4 77d077f5 USER32!RealMsgWaitForMultipleObjectsEx+0x13f
>> > 04 0a33fef0 756342a4 USER32!MsgWaitForMultipleObjects+0x1d
>> > 05 0a33ff84 77bc91ed comsvcs!CSTAThread::WorkerLoop+0x1e3
>> > 06 0a33ffb8 77e4a990 msvcrt!_endthreadex+0x95
>> > 07 0a33ffec 00000000 kernel32!BaseThreadStart+0x34
>> >
>> >
>> >
>> >
>>
>>
>>

Next message: David Wang [Msft]: "Re: Uploading Site Changes / How To"
Previous message: J. Knapp: "RE: Taking forever to start processing"
In reply to: tapman: "Re: w3wp.exe takes 100% processor"
Next in thread: tapman: "Re: w3wp.exe takes 100% processor"
Reply: tapman: "Re: w3wp.exe takes 100% processor"
Messages sorted by: [ date ] [ thread ]

Relevant Pages

Re: IIS Maximum number of concurrent requests
... If these are ASP pages, then you can have #CPU * 25 concurrent requests. ... > I'm looking for some advice on performance settings of IIS. ...
(microsoft.public.inetserver.iis)
Re: IIS Maximum number of concurrent requests
... queries should be as fast as possible, some might take about 5 minutes. ... Still, in this case, I would expect it to be possible to launch 25 ASP ... requests (because it's a single CPU), ...
(microsoft.public.inetserver.iis)
Re: IIS Maximum number of concurrent requests
... ThreadGating may prevent the full 25 from being used ... > Still, in this case, I would expect it to be possible to launch 25 ASP ... > requests (because it's a single CPU), ...
(microsoft.public.inetserver.iis)
What Impact Do Static HashTables and Classes have on the CPU?
... Under real world stress this ... app is handling 5 get requests per CPU per second. ... CPU does not increase it remains at 5 per CPU. ...
(microsoft.public.dotnet.languages.csharp)
Re: Long-running ASP page using ServerXMLHTTP...
... If you are using Sessions it's normal that all requests for a single session ... Updating the cache itself can be done from your ASP page itself, ... > are allowed to execute while we are waiting for the response from the 3rd ...
(microsoft.public.inetserver.asp.db)