socket.emit method will delay a little bit

[caichunjian520]

I am working on an iOS drawing app that send each of the drawing point to server, or get the drawing point from server (real-time shared canvas). It works smoothly when get the point using socket.on. But when I use socket.emit to send each point to server, it will send about 0.1-0.3 seconds delay and the server will get a chunk of point at one time. This will cause something I don't want happen (other clients draw the point not smoothly).

I think maybe there are some configurations I didn't set when initialize the socket manager.

Anyone can help me solve the issue? Thanks

[nuclearace]

How many points are you sending per-second? One thing you could try doing is using the raw emit views that were added. These bypass a destructuring operation that otherwise has to happen for each emit. And depending on the size/nesting of the objects you were sending, might have some impact on performance.

[caichunjian520]

Thanks for your reply. There are about 40-60 points per-second when I draw and send to server. But if I saved all points (hundreds of points) of a pre-defined canvas on the device and send the points to server, the server will get all the points within 3 seconds.

As I draw on the screen with my finger, each time when the app get a new point, it will call socket.io function, it works very smoothly on website , but not on iOS. (I do exactly the same logic both on website and iOS app)

To make it simpler, I make a button to click and send 100 strings to server, so socket.emit function will be called 100 times. Still not smoothly.

I also changed socket.emit to socket.rawEmitView.emit you mentioned. The issue is still exist.

[nuclearace]

I'm not sure in that case. I've not done heavy stress testing on the client, but sending that many messages that quickly might run into some overhead. You can use the new emits with completion handlers to get a very rough idea of how long it takes to send a message.