Running Scheduled Task in Websokcets Or Scaling with multiple workers

[suryanarayanan035]

Running Scheduled Task in Websokcets Or Scaling with multiple workers

[aaugustin]

So, I thought of moving the pinging work to a separate worker. So my main server, will handle the connections and my worker will do the pinging. To do so, I have to serialize/pickle the websocket object which is not possible.

"worker" in this context is "asyncio coroutine". Coroutines share the same memory space. Therefore, you don't need to serialize/pickle.

(Besides, you cannot (easily) share sockets between processes. Therefore, generally speaking, serialize/pickle a network connection with the intent of sharing it never makes sense. If it's the same process, you don't need to serialize. If it's in a different process, you cannot share.)

Are you aware the websockets already does this for you and you can simply tune the parameters as you wish?

e.g. serve(ping_interval=10, ping_timeout=5) if you think that latency > 5s means the connection is dead