"Axel R." <[email protected]> writes: > @Brett: You wrote: > > Not reliability per se but messages will not be recv()'ed in the order > that they were send()'ed when zeromq is configured with more "I/O" > threads than the default. > > This is a little concerning: how increasing the number of threads results in > out-of-order delivery, unless > the default is 1? What are the circumstance where messages should be expected > to arrive out-of-order?
I think there is no need to worry. The default is that messages are ordered. Normally, applications should/would not even know there is a "knob" to add more I/O threads. Only if one is trying to push beyond 20-25 Gbps through a single TCP transport is this even worth considering. IMO, if this high level of performance is truly required one is doing something sophisticated enough to either deal with out-of-order or to find another way to get multiple TCP transport streams while keeping order (eg, multiple processes). -Brett.
signature.asc
Description: PGP signature
_______________________________________________ zeromq-dev mailing list [email protected] https://lists.zeromq.org/mailman/listinfo/zeromq-dev
