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
{{ message }}
This repository has been archived by the owner on Jan 21, 2021. It is now read-only.
I couldn't really get any numbers for fan-in because in my test, multiple producers proved difficult as you couldn't bind to the same uri more than once... Unfortunately this means this implementation will require locking in the application bridge itself because zmq sockets are not thread safe.
So if you have to lock on both sides anyway, the inproc queue is in fact slower. I can see how it would be much faster for a specific use case where you know you have (say) 2 threads which need to receive messages and that's it, but for a mamaQueue implementation, you have to write for the general case, and when you do that, wombatQueue actually works out faster so we'll be sticking with that for the bridge.
See http://api.zeromq.org/4-0:zmq-inproc for details. Will need performance tested against existing wombatQueue to see if it's an improvement.
The text was updated successfully, but these errors were encountered: