max concurrent request

First, are we talking about an ISAPI or CGI? CGI implies an expensive
process creation on every request, something non-existent for ISAPI,
amortized.

Also, when talking about performance, maximum concurrent requests is NOT
what is important. For example, processing of 2000 requests with a
concurrency of 10 will likely be far faster than processing all 2000
simultaneously. Why? Thread context switching is going to be costly in the
2000 simultaneous case.

Finally, maximum concurrent requests usually exaggerate any bottlenecks in
custom ISAPI/CGI code, such as lock contention. Perf analysis helps figure
this out instead of asking "what is the maximum number of concurrent
requests in IIS6?"

So, if you really want to look for better performance, you will need to
provide far more information for help than asking for "maximum concurrent
requests".

--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Vikramaditya Singh" <vicksjaipur.TakeThisOut@rediffmail.com> wrote in message
news:uIpG047yDHA.1924@TK2MSFTNGP10.phx.gbl...
i want to know maximum no of concurrent request iis 6 can handle
effiecently. As we are into publishing result and often get bad server
performance during important results.

Thanks