Replies: 1 comment 6 replies
-
No, it's not. The |
Beta Was this translation helpful? Give feedback.
-
|
That's weird indeed. What is the reason of the disconnection? |
Beta Was this translation helpful? Give feedback.
-
It only happen when the incoming message is huge. Other time, when the messages are less than 1k per second, it is working fine. Not using proxy. |
Beta Was this translation helpful? Give feedback.
-
I get ping timeout or error timeout. I can confirm server resource itself is not the problem. I am running the same script in the same server with different port and serving only small amount of clients (less than 100), it is running well, sending messages on time, and doesn't drop the clients. Suspect some ubuntu param or nodejs socket io param that need to be tweaked to handle more messages per client, but I am running out of idea. |
Beta Was this translation helpful? Give feedback.
-
|
Probably Socket.io is busy transferring your app data, so pings do not get through, timeout as a result. Test with longer timeout or/and phase sending data with small pause between. |
Beta Was this translation helpful? Give feedback.
-
|
Is there any logs / warning / error logs that tell you the clients has been dropped by socket io ? |
Beta Was this translation helpful? Give feedback.
-
Is maxHttpBufferSize actually related to number of clients ?
EG, if I have 1000 clients connected, sending 1 message of 1KB at 1 time.
that would easily exceed 1MB as per defined in maxHttpBufferSize default value.
https://stackoverflow.com/a/12978658/309740
Here, it stated that the buffer is actually related to the message to be sent to the number of clients.
But in socket io documentation, https://socket.io/docs/v4/server-options/
it stated that "how many bytes a single message can be".
That could be confusing. So who is right ?
Beta Was this translation helpful? Give feedback.
All reactions