Re: IIS Maximum number of concurrent requests
From: Pat [MSFT] (patfilot_at_online.microsoft.com)
Date: 09/17/04
- Next message: Joe: "FrontPage run-time component page"
- Previous message: Pat [MSFT]: "Re: IISState log help"
- In reply to: Yves Tilkin: "Re: IIS Maximum number of concurrent requests"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 16 Sep 2004 19:34:08 -0700
You are correct. ThreadGating may prevent the full 25 from being used
though (it will queue earlier if the CPU is very busy).
Pat
"Yves Tilkin" <YvesTilkin@discussions.microsoft.com> wrote in message
news:DAE36834-D0BC-4F6C-A25D-4B00AE753535@microsoft.com...
> What is happening is the thing you describe in the second paragraph. The
> requests are waiting for the DB queries to return. As we are aware that
> 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), all having the status executing. The
> 26th request would then get the status queued. Is my thinking here correct
> or
> are there other things to keep in mind as this is currently not how it
> works
> in our case.
>
> Yves
>
> "Pat [MSFT]" wrote:
>
>> If these are ASP pages, then you can have #CPU * 25 concurrent requests.
>> If
>> you enable the ThreadGate, then IIS will block any additional ASP pages
>> from
>> running if the CPU usage is too high. All of this is highly dependent on
>> what the ASP pages actually do. If 10 concurrent requests are driving
>> the
>> CPU to 99%, then you are probably doing something in a loop that eats a
>> lot
>> of CPU cycles (e.g. iterative string concatenation) and increasing the
>> concurrent numbers won't help much. The more efficient your code, the
>> more
>> concurrent pages your machine can handle.
>>
>> When you make a DB query (assuming it is to a remote DB), the running ASP
>> page will block (the thread goes into a Wait state pending a return from
>> the
>> DB). In which case, 0 CPU is being used.
>>
>> Pat
>>
>>
>> "Yves Tilkin" <Yves Tilkin@discussions.microsoft.com> wrote in message
>> news:0BC6BCD2-EA99-4D17-8F89-BF098AC95800@microsoft.com...
>> > I'm looking for some advice on performance settings of IIS. We have an
>> > ASP
>> > application that creates Com+ components that read data out of a
>> > database.
>> > Some of these data retrieval requests can take some time (about 5
>> > minutes).
>> > Because of this it can happen that IIS needs to handle a lot of
>> > requests
>> > (about 20 to 30) which we assume IIS can easily handle as long as
>> > system
>> > resources are available. What happens is that when IIS executes about
>> > 10
>> > requests (can be less), all extra requests get queued. This when CPU is
>> > 99%
>> > idle and plenty of memory is available. I've already experimented with
>> > settings like AspThreadGateEnabled and others but it does not make any
>> > difference (I would think handling about 30 requests should work with
>> > the
>> > default settings). The machine on which we ran this was a PIV 3Ghz, 1GB
>> > ram
>> > running Windows Server 2000.
>> >
>> > Any help/suggestions would be appreciated?
>> > Thanks,
>> > Yves
>>
>>
>>
- Next message: Joe: "FrontPage run-time component page"
- Previous message: Pat [MSFT]: "Re: IISState log help"
- In reply to: Yves Tilkin: "Re: IIS Maximum number of concurrent requests"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
