-
Notifications
You must be signed in to change notification settings - Fork 471
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Investigate async TCP connection #665
Labels
Milestone
Comments
Pretty sure that's intentional, it's done on whatever thread triggered the action. We don't queue them up for the socket reader thread. |
This is probably no longer really relevant with websockets. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: