Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Socket.io benchmarking - how many messages can you send per second?

drewww.github.com

Post reply on HN
Print view View original

11–12 of 12 posts

Re: Socket.io benchmarking - how many messages can you send per second?

#11

Post by donpark »

Rauchg wrote: post #3

Socket.IO author here. You might be pleased to hear as well that our focus on the next few releases is heavy on performance and making load balancing trivial. We recently made the Socket.IO parser 300% faster. The new underlying websocket server is extremely fast (check the benchmarks at https://github.com/learnboost/websocket.io/ ), and optimizations to long-polling are coming as well.

Will there be 'websocket.io-client', high-performance server-side WebSockets client module, in the near future?

Re: Socket.io benchmarking - how many messages can you send per second?

#12

Post by donpark »

donpark wrote: post #11
Rauchg wrote: post #3

Socket.IO author here. You might be pleased to hear as well that our focus on the next few releases is heavy on performance and making load balancing trivial. We recently made the Socket.IO parser 300% faster. The new underlying websocket server is extremely fast (check the benchmarks at https://github.com/learnboost/websocket.io/ ), and optimizations to long-polling are coming as well.

Will there be 'websocket.io-client', high-performance server-side WebSockets client module, in the near future?

I noticed `websocket.io` is depends on a module called `easy-websocket` which is registered with NPM with description "lain and simple websocket client" but no where to be found on Github. Is `websocket.io` what we are supposed to be using as client?
Post reply on HN