There's also the option to init messages from an existing buffer, which prevents memcpy overhead etc. often associated with marshalling. See :
http://api.zeromq.org/3-2:zmq-msg-init-data This works pretty well with garbage collectors in most languages as well. Flag the String or similar object as "in use" before init, remove object flag in the callback function. On Thu, Oct 10, 2013 at 3:44 PM, Pieter Hintjens <[email protected]> wrote: > First off, don't ever believe anyone's claim of performance if you can > try yourself. > > Second, marshalling can go from very expensive to very cheap but it > depends on the data you use, and the marshalling technology. It's got > nothing to do with ZeroMQ. However, with ZeroMQ you are free to study > the cost of marshalling and choose or build the design that works best > for you. > > Lastly, "faster" is very slippery. How large are your messages, how > many do you send per second, to how many peers? > > -Pieter > > > > > On Thu, Oct 10, 2013 at 3:22 PM, crocket <[email protected]> wrote: > > Someone pointed out that ZeroMQ was great at communicaton between two or > > more languages but that for communications in one language, internal > > messaging solutions like akka and clojure.core.async would be a lot > faster. > > > > He said marshalling was expensive. > > > > I looked into core.async, and I found it uses queues for asynchronicity. > > > > How would one compare core.async and ZeroMQ? > > > > _______________________________________________ > > 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 >
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
