Number of Websockets on a single page

I am building a complex HTML 5 application that takes advantage of Websockets. I am getting to the point where I have a lot of different types of data that gets updated in real time on the screen.

I want to know if it is going to be better for me to have fewer Websockets that are more complex, or a lot of simple Websockets open per page.

I added http://github.com/TooTallNate/Java-WebSocket web socket server to my Grails Application.

Right now I am going down the path of using a lot of simple web sockets for each task. I know using more sockets will use more memory on the server side but also more s开发者_如何学Cockets means more concurrent processing.

Does anyone have any advice on how I can balance this.

Thanks for any tips in advance. Keith Blanchard

I think it is hard to make any reasonable statements about websockets without measuring the actual performance in specific browsers.

My inclination would be to have a single websocket per client. There are some pretty hard limits on capacity server-side when doing IO ... relatively easily to saturate the channel when you have many connections (something that can bite heavily ajaxified systems as well).

Again, need to really measure to make intelligent statements about this.

Websocket-per-client would also make the application much more manageable ... depends on your actual use-case, but "more concurrency" is not necessarily better and can make managing state incredibly complex.

I personally did some benchmark on this one, and the results are:

10 websockets on a single page will cause page a little unresponsive when data coming in from each socket.

50 websockets on a single page will cause an unbearable freeze on the web.

So somewhere around 10 or less than 10 would be your upper limit.