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
I'm testing the Go websocket client, but are having some issues. When subscribed to all trades (production feed):
Just receiving (no further processing) causes a CPU usage of 110-120%
After a while, the connection will close with either an 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:
arniwesth
changed the title
Go client inefficient?
Go client high CPU load
Aug 6, 2021
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.
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: