Quick question - I've heard this two different ways and I'm looking for
some info.
In ASP.Net tuning, maxconnections defaults to 2, and MS recommends
(among other settings changes) you set it to 12. They go on to explain
that maxconnections only controls the http requests from asp.net
applications going _out_ of the server.
However, I've been told that in the following scenario:
You have a client app, an NLB web cluster with three web services.
Client App calls Web Service A on WebCluster1.
Web Service A calls Web Service B synchronously.
Web Service B calls Web Service C synchronously.
Web Service C finishes, B finishes, A finishes.
Normally local http requests do NOT count towards the maxconnections
limit (the local connection limit is something like 2B - the maximum
dword value on x86 or something).
But! I have been told that if the url is to the NLB IP (i.e.
http://webcluster1/webservice-B)
it DOES count against your max
connections, and as a result you should NOT use web services that call
any other web service synchronously on an AppCenter cluster.
Is that true, does calling http://webcluster1
locally rather than
http://localhost
(or machinename, or whatever) use up your
maxconnections, rather than be counted as a local connection?
I have not been able to find any do***entation on this one way or
another.
If I do a "route print" on a AppCenter server w/NLB, it does show the
NLB IP being routed to 127.0.0.1, but I also have a thrice-calling web
service that seems to have performance issues on an AppCenter NLB web
cluster when more than a couple clients hit the web service
simultaneously, and I'm being told you can't mix web services &
AppCenter like this.
|
