[zeromq-dev] Design advise

Claudio Carbone erupter at libero.it
Fri Dec 28 20:21:15 CET 2012

My stupid idea is a "man-in-the-middle":
Put a loop in your queue doing a round-robin on the request pool.
Like forwarding 5 reqs for each client each turn: if a client sends a lot of requests, it just has to wait until the next loop.

By the way shouldn't the router already be doing some loadbalancing ?
I'm really not a super zmq expert.

-- Sent from my ParanoidAndroid Galaxy Nexus with K-9 Mail.

Nishant Mittal <nmittal at rblt.com> wrote:

>In my use case,
>- I have a queue (a proxy with ROUTER in the front and DEALER in the
>- Client has a DEALER socket that connects to the ROUTER in the proxy
>above. not using as I want the client to be able to send multiple jobs
>without waiting for a response
>- Worker has a REP socket that connects to the DEALER in the proxy
>- this is working great, however, a design goal is to not let 1 client
>block other clients from sending and receiving responses which is what
>happening at the moment. If the first client sends a lot of requests
>the second client started sending its requests then first all the
>of the first client are served and then the second.
>How can I improve this design so if 1st client sent 10000 requests and
>2nd came along and sent 1 request, it doesn't have to wait for the
>requests to finish?
>I guess one solution would be to lower the high watermark so the 1st
>would be blocked from sending more but feel that would hurt
>zeromq-dev mailing list
>zeromq-dev at lists.zeromq.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20121228/9ceb87dc/attachment.htm>

More information about the zeromq-dev mailing list