Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@byte well the problem is that the lag kinda comes randomly... also it feels like when there are more than 1 events they get buffered and delayed. But the longest that came was around 15 seconds (from win PC -> win server -> linux PC) interesting though maybe it didn't switch to websockets then... Thanks anyways
-
@byte found a way to do it. Send a random (can be any) event continously like every 500ms then it's guaranteed to not be buffered by any of the OSs.
-
@notcool well for me it seems to be some buffering on the client's size as after the event there are no packets sent on the wire (yeah I've checked with wireshark XD) Well if I keep sending it works instantly.
When there are only 2 pages on Google you know you're in serious shit.
This is where US's bandwith is going
My dog learning nodejs.
So any fellow Socket.io dev here know how to reduce the delay of my app? When I send an event it sometimes takes like 10 seconds to send the data to the server then to 2 other clients using io.sockets.emit. I'm on LAN where the server and the sender client is connected with a switch then the receiver is on wifi which is connected to the same switch so it's not far away.
Anyways it uses WEBSOCKETS so it should be fast right???!?! Is windows keeping my packets back? (poor packets :( they just wanna arrive :( )
undefined
whysoslow
nodejs
damnson
socketio