Running Count Vs True Count

Re: maxWorkerThreads Vs w3wp thread count.

• Blackjack Running Count Vs True Count
• Running Count Vs True Count

I'm doing a comparison of Dijkstra's and BFS, on both adjacency lists and adjacency matrices. I'm testing all four variations as shortest path algorithms, and clocking their running time over unwei. True Count Vs Running Count. The Running Count is only going to tell the player whether there are fewer or more high cards in the deck compared to the.

Sep 26, 2007 01:12 PM nakul LINK

Hi Benson

Thanks for your response.

I have verified that the machine has a single processor. Also, if I understand correctly, is MaxWorkerThreads the maximum number of worker threads that all w3wp processes can use?

Blackjack Running Count Vs True Count

Example. If I have 2 asp.net apps running under different application pools, there would be 2 instances of w3wp processes(1 per application pool). If the MaxWorkerThreads is set to 20, does it imply that these w3wp processes have a pool of 20 threads they an can use? If yes, doesn't this imply that asp.net can handle a max of 20 concurrent requests since at any given time only 20 workers threads would available?

Running Count Vs True Count

Here's what I am getting to-

I create a client application to load test my web service. Basically the client spans 500 threads and each of these threads call the web service. I am monitoring the 'Web ServiceCurrent Connections' performance counter on the server hosting the web service. The counter does not seem to indicate concurrent connections - its value fluctuates between 5 and 30. I am also monitoring 'Web ServierPost Requests' counter and it seems to working fine - it spikes close to 500 each time I run the client. I was under the impression that the 'Web ServicveCurrent Connections' counter should reach close to 500 each time i turn the client - There is a brief period when the counter was behaving as per my expectation.

Note- Asp.NetRequests in Applicatin Queue shows a value of 0. I guess this means that requests are being processing concurrently. But the Current Connections counter does not imply this.