[zeromq-dev] [PATCH] Scalability improvements for large amounts of connections

Pieter Hintjens ph at imatix.com
Mon Oct 11 17:33:33 CEST 2010


On Mon, Oct 11, 2010 at 5:12 PM, Martin Lucina <mato at kotelna.sk> wrote:

> I agree that "socket migration" should be documented. However, IMHO 99.9%
> of users have no idea what a "full memory barrier" is or why they should
> care.

Indeed.  Let's start with the use cases.  There are three afaik:

1. Trying to share a socket between multiple threads. Dismissed as bad practice.
2. Erlang-style moving of active sockets between threads.  For
advanced users, can be covered by "ensure full memory barrier".
3. Creating sockets in parent threads.  Quite common use case, and the
only one that should be explicitly supported or documented IMO.

For case 3 it should IMO either 'just work' when the socket is created
but never used in the parent thread (doing an implicit memory barrier
after creation, for example).

-
Pieter Hintjens
iMatix - www.imatix.com



More information about the zeromq-dev mailing list