Hi, Basically there's only length field overhead (1 or 8 byte) when we use multipart messages.
Sure it requires more iteration in the ZMQ core, but it should be neglect. So I prefer a structure that I could build a program easier to understand. 20~30 multipart messages might be more hard to program not because of performance reason. Thanks Min On May 23, 2013, at 7:05 AM, Davide Faconti <[email protected]> wrote: > Hi, > > I have a question that, probably is a bit naive. > I have a published that send complex data (an easy to serialize struct, that > is about 200 bytes, but I guess this is not relevant). > > I publish this data in a non periodic way, in other words sometimes I have to > deliver 10-20 samples of this data to the subscriber. Let's use N to refer to > the number of data samples I want to send. > > I have two way to do that: > > 1) Either I publish N messages. > 2) I use multipart messages provided by ZMQ; one message the message as N > parts. > > Is one of these two ways more efficient in terms of, let's say latency or > speed? > > Thanks in advance. > > -- > Davide Faconti > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
