Support more than one write/read at a time (improve performance)

[AaronO]

Right now since we toggle readable/writable everytime to synchronize reads/writes, I suspect that's damaging the performance of socket-io.stream.

Would be great if we could do something smarter rather than simply toggling. I think it would dramatically improve performance.

[nkzawa]

+1

I'm also sure that we can do better for performance.

[AaronO]

Do you have any good thoughts on this ?

I'm really busy lately (with business) unfortunately :/

I've tried out a few things in the https://github.com/nkzawa/socket.io-stream/tree/fix/performance-issues branch.

Feel free to check it out.

Right now I feel that socket.io-stream is only doing one read/write at a time, and you can really feel it the end user experience, which kind of makes it suck a little.

This is a massive issue, that would dramatically improve the library if we can solve it.

So lets get it fixed ! :)

[nkzawa]

I'm also busy recently because I'm taking a vacation and am traveling :)
I'll check the detail when I went back.

Anyway, it's better to take benchmark test first, IMO.

[dotnetwise]

so you back from vacation?

[nkzawa]

I will check #13 again.

[nkzawa]

I noticed that writing multiple times at a time makes the module incompatible to Stream API.
A different approach is to send a bigger chunk at a time by using the highWaterMark option.

BTW on upcoming socket.io v1.0, we can directly send a number of binary data at once.
I think we can improve performance then.