title: SignalR connections skewing response time in IIS using ARR
body: <p>We are using application request routing with 5 servers running IIS 7.5 and have just recently implemented a messaging system using SignalR in our application.</p>
  
  <p>The SignalR connections are working as we expect (with the only drawback being that a message sent from one server doesn't get activated on the other 4).</p>
  
  <p>The problem(?) we are having is that the Response Time of some requests on IIS that are shown in the load balancer (ARR) are coming up as 2-3 minutes sometimes, which I am assuming are because of connections using something like long-polling.</p>
  
  <p>Our ARR is set to load balance using lowest response time, but it seems like this metric will be completely incorrect because of these SignalR connections. Is there any way to fix these connections so they don't get used in the ARR calculation for response time? Are we stuck having to move the SignalR messages to a separate server to avoid this type of thing (which admittedly would solve other things as well)?</p>