[zeromq-dev] Multicore Magic

Brian Candler B.Candler at pobox.com
Tue Apr 27 12:46:53 CEST 2010

On Mon, Apr 26, 2010 at 11:00:39PM +0200, Pieter Hintjens wrote:
> On Mon, Apr 26, 2010 at 10:57 PM, Martin Sustrik <sustrik at 250bpm.com> wrote:
> >> Are signals as fast as, or slower than inproc?
> >
> > They are slower.
> Any other mechanism for inter-process communication?
> Seems so unfair that processes are penalised for not being threads... :-)

1. That's the whole point of processes. They are isolated, and can't stomp
on each other's memory space, intentionally or accidentally.

2. There's a big difference between latency and throughput. Many apps aren't
particularly sensitive to the former.

3. For those apps which do care about a few extra microseconds latency, I
suggest you're not going to want to write them in Python anyway :-)

Standard advice: build system first, measure performance, then if required
identify hotspots and tune.  In many cases you'll discover the hotspots are
not where you first thought they might be.



More information about the zeromq-dev mailing list