You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
10:12 <@Netshroud> xPaw: we probably could use Socket.Select to have one thread handle N connections, but I'd rather just switch to async methods and let the thread pool handle it (like websocket does)
Currently, each SK2 connection creates a new thread, so in extreme examples like steamstat.us monitoring, there's a thread for each CM connection (over 200 of them!).
I also noticed sending packets is done on the main thread, and not the thread created for the socket polling/reading.
The text was updated successfully, but these errors were encountered:
Currently, each SK2 connection creates a new thread, so in extreme examples like steamstat.us monitoring, there's a thread for each CM connection (over 200 of them!).
I also noticed sending packets is done on the main thread, and not the thread created for the socket polling/reading.
The text was updated successfully, but these errors were encountered: