Last post Feb 14, 2014 05:06 AM by kjohann
Feb 13, 2014 10:40 AM|kjohann|LINK
I was wondering if someone could give me some insight as to how SignalR handles idle connections. I've run a test where I connected 4500 clients to my application. The application runs on a dual core (old) HP pc with Windows Server 2012 R2 and IIS8. I understand
that serving a WebSocket connection isn't the most resource consuming task in the world, but still. 4500 clients should, in my opinion, have given a little more than the 2% peaks that turn up every now and then (which I'm guessing is heartbeats).
I've run the same test with Socket.IO as well - it shows the same behavior. So the second thing I'm wondering is if it isn't something SignalR does, but rather how WebSockets really works. This may be the wrong forum for that question though..
Feb 13, 2014 12:07 PM|BrockAllen|LINK
Idle connections are just memory in the server.
Feb 14, 2014 05:06 AM|kjohann|LINK
Ok - That makes sense I guess..