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 have a service which forwards messages from a local zeromq based network of services to a remote websocket server via the ws4py gevent websocket class.
It seems to be caused by the call to os.urandom in ws4py/messaging.py and the fact that the default rlimit on macosx is 256.
On high load, the os.urandom fails which brings me to my next question. Is websockets or ws4py gevent client bad for streaming continuous data or should os.random be replaced with something that works under high load. I assumed that gevent would make accesses to /dev/urandom concurrent.
The text was updated successfully, but these errors were encountered:
I have a service which forwards messages from a local zeromq based network of services to a remote websocket server via the ws4py gevent websocket class.
It seems to be caused by the call to os.urandom in ws4py/messaging.py and the fact that the default rlimit on macosx is 256.
On high load, the os.urandom fails which brings me to my next question. Is websockets or ws4py gevent client bad for streaming continuous data or should os.random be replaced with something that works under high load. I assumed that gevent would make accesses to /dev/urandom concurrent.
The text was updated successfully, but these errors were encountered: