-
Notifications
You must be signed in to change notification settings - Fork 185
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
Go client high CPU load #118
Labels
Comments
Yes, that's correct. I'm working currently on an improved go WS client as there a multiple issues with the current implementation which wasn't stress tested. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm testing the Go websocket client, but are having some issues. When subscribed to all trades (production feed):
110-120%
Unexpected EOF
or being closed because too many messages are buffered by the sender.When running the C# websocket client (targeting net5.0) on the same environment and subscribing to all trades, the CPU usage is
~20-40%
and it seems to be more stable.When running the Python websocket client on the same environment, the CPU usage is
~35-50%
I would have assumed the Go client to be at least as efficient as the C# client and more efficient than Python. Any thoughts on this?
The text was updated successfully, but these errors were encountered: