[zeromq-dev] max_app_threads = 512
sustrik at 250bpm.com
Wed Jun 16 07:36:13 CEST 2010
Matt Weinstein wrote:
>>> == many threads == queue -- one thread -- outbound socket
>> Yes. In theory you can use it that way. Obviously the performance will
>> be poor and no fair-queueing will be done.
> Yes, you're probably right.
> How about lockless queues (pipes) and round-robin scheduling, similar
> to what you're doing. I can just wake up my service thread with a
> single condition_variable and do the scan and forward.
> Are there other performance implications / does that sound workable?
> Or am I missing something?
I would expect the performance impact to be associated with migrating
the pipes among OS threads. Cache synchronisation is expensive.
More information about the zeromq-dev