I have a .net application that following an inbound request needs to make multiple subsequent outbound HTTP requests. During periods of high load an increase in response time occurs. This was having a serious detrimental effect on our application. Like many others before me we to counteracted this by increasing the maxConnection value from the default to the MS recommended value (12 * #CPU) which in our case is 96. This allows IIS to make upto 96 requests to a single address at any one time.
<system.net>
<connectionManagement>
<add address = "*" maxconnection = "96" />
</connectionManagement>
</system.net>
Thankfully our application is now responding well even under peak usage. What I would like to know now is considering previously we were hitting the limit of 2 concurrent requests per min. What tools/monitoring can I use to figure out how close we are to the new threshold of 96?