We have a Remoting.NET 2.0 server running in Single-Call mode in IIS7. It has two APIs, for example:
- DoLongRunningCalculation () - contains many database queries and can take a lot of time.
- HelloWorld () - just returns "Hello World".
We tried to emphasize testing the remote server (on a machine running Windows 7) in the worst case, randomly exposing it to two API calls and found that if we go beyond 10 client requests, the response from HelloWorld (which is usually less than 0.1 s) begins to last longer and longer for many seconds. Our goal is that we do not want to have long remote calls to block short calls. Here are the performance counters for ASP.NET v2.0.50727, if we have 20 client threads:
- Queue Requests: 0
- Requests Fulfillment: (Maximum: 10)
- Workflows: 0
- Pipe instance mode: (maximum: 10)
- Requests in the application queue: 0
maxConcurrentRequestsPerCPU "5000" Thomas: ASP.NET IIS 7.0 6.0, . , , 10.
, :
.