Open catinred2 opened 9 years ago
This is explained in the Guide.
http://zguide.zeromq.org/page:all#Asynchronous-Majordomo-Pattern
On Wed, Nov 12, 2014 at 8:22 AM, XMING notifications@github.com wrote:
I make a test on Majordomo example. mdclient log
debian:~/git/zguide/examples/C$ time ./mdclient 100000 requests/replies processed real 0m29.877s user 0m3.316s sys 0m4.352s
is there anything to improve the performace?
— Reply to this email directly or view it on GitHub https://github.com/imatix/zguide/issues/472.
@hintjens the async pattern performance is as twice as sync pattern. quite far from 100k.
any advice for improving service-oriented pattern performance? thanks.
Any request-reply pattern is going to be slow due to multiple hops and round trips. Also it is blocking for clients and workers so throughput performance is not usually a concern. If you absolutely need faster performance than remove the broker and send async requests and replies directly to workers.
On Wed, Nov 12, 2014 at 8:54 AM, XMING notifications@github.com wrote:
@hintjens https://github.com/hintjens the async pattern performance is as twice as sync pattern. quite far from 100k.
any advice for improving service-oriented pattern performance? thanks.
— Reply to this email directly or view it on GitHub https://github.com/imatix/zguide/issues/472#issuecomment-62682138.
I make a test on Majordomo example.
mdclient log
debian:~/git/zguide/examples/C$ time ./mdclient 100000 requests/replies processed real 0m29.877s user 0m3.316s sys 0m4.352s
is there anything to improve the performace?