Re: [zeromq-dev] not binging to all LISTEN port

2014-09-23 Thread Pieter Hintjens
I'm not going to ask why you are trying to do something so... wrong. Presumably you have good reasons. Disregarding netstat, can clients connect on the other ports, or not? On Tue, Sep 23, 2014 at 12:25 AM, Mohit Anchlia mohitanch...@gmail.com wrote: I have a code that binds zeromq socket to

Re: [zeromq-dev] not binging to all LISTEN port

2014-09-23 Thread Mohit Anchlia
Can you please explain more about what is it that I am doing wrong? I am just trying to create many multithreaded workers for the incoming requests. On Tue, Sep 23, 2014 at 3:48 AM, Pieter Hintjens p...@imatix.com wrote: I'm not going to ask why you are trying to do something so... wrong.

Re: [zeromq-dev] not binging to all LISTEN port

2014-09-23 Thread Bob Clarke
I think his main point is, Why are you using so many sockets? A single ZeroMQ socket can handle a tremendous volume of messages. Your brief code sample shows a REP socket, so can I guess that the other is a REQUEST? Switching to DEALER/ROUTER would get you the request/reply pattern you seem to

Re: [zeromq-dev] not binging to all LISTEN port

2014-09-23 Thread Mohit Anchlia
Thanks! Is using so many sockets essentially a bad idea? How and when do I know that I am saturating one dealer/router? On Tue, Sep 23, 2014 at 9:47 AM, Bob Clarke optiongu...@gmail.com wrote: I think his main point is, Why are you using so many sockets? A single ZeroMQ socket can handle a

Re: [zeromq-dev] not binging to all LISTEN port

2014-09-23 Thread Bob Clarke
You would run performance tests in your environment to see how many of your messages a single socket can handle. On Tue, Sep 23, 2014 at 10:53 AM, Mohit Anchlia mohitanch...@gmail.com wrote: Thanks! Is using so many sockets essentially a bad idea? How and when do I know that I am saturating

Re: [zeromq-dev] not binging to all LISTEN port

2014-09-23 Thread Mohit Anchlia
I was more of referring to debugging overload issues in prod. that we might not have been able to catch in performance environment. How can I tell that router/dealer is overloaded and need more router/dealers? On Tue, Sep 23, 2014 at 10:10 AM, Bob Clarke optiongu...@gmail.com wrote: You would

Re: [zeromq-dev] not binging to all LISTEN port

2014-09-23 Thread Gregg Irwin
Hi Mohit, MA I was more of referring to debugging overload issues in prod. MA that we might not have been able to catch in performance MA environment. How can I tell that router/dealer is overloaded and MA need more router/dealers? While it's always good to test, if you provide a rough hardware

Re: [zeromq-dev] not binging to all LISTEN port

2014-09-23 Thread Mohit Anchlia
I understand the basic part of performance testing and all other related things that need to happen. I was really looking from troubleshooting perspective. Say load increased more than anticipated or tested numbers, when that happens are there any metrics available that can point to router/dealer

Re: [zeromq-dev] not binging to all LISTEN port

2014-09-23 Thread Pieter Hintjens
In general you can do everything through a single socket, and then allocate 1 I/O thread per gigabit of traffic in or out. Do measure CPU and network load. On Tue, Sep 23, 2014 at 7:35 PM, Mohit Anchlia mohitanch...@gmail.com wrote: I understand the basic part of performance testing and all

Re: [zeromq-dev] not binging to all LISTEN port

2014-09-23 Thread Charles Remes
Mohit, Your application should have end-to-end latency and throughput measurements. I build this functionality into any project that uses zeromq so that I can track the latency between any two endpoints (and any intermediate points too). This data is printed to a log in a format that is easily

Re: [zeromq-dev] not binging to all LISTEN port

2014-09-23 Thread Robin Scher
Is there anyone putting this kind of reusable performance testing system into ZeroMQ or maybe into czmq? Robin Scher ro...@uberware.net +1 (213) 448-0443 On Sep 23, 2014, at 10:43 AM, Charles Remes li...@chuckremes.com wrote: Mohit, Your application should have end-to-end latency and

Re: [zeromq-dev] not binging to all LISTEN port

2014-09-23 Thread Pieter Hintjens
This would be cool to have in CZMQ, indeed. On Tue, Sep 23, 2014 at 8:03 PM, Robin Scher ro...@uberware.net wrote: Is there anyone putting this kind of reusable performance testing system into ZeroMQ or maybe into czmq? Robin Scher ro...@uberware.net +1 (213) 448-0443 On Sep 23, 2014,

Re: [zeromq-dev] not binging to all LISTEN port

2014-09-23 Thread Gregg Irwin
RS Is there anyone putting this kind of reusable performance testing RS system into ZeroMQ or maybe into czmq? I was going to ask the same thing. Or if CR has suggestions and guidelines for others who think it's a good idea. -- Gregg ___ zeromq-dev

Re: [zeromq-dev] not binging to all LISTEN port

2014-09-23 Thread Matthew Hawn
, September 23, 2014 11:44 AM To: ZeroMQ development list Subject: Re: [zeromq-dev] not binging to all LISTEN port Mohit, Your application should have end-to-end latency and throughput measurements. I build this functionality into any project that uses zeromq so that I can track the latency between any

Re: [zeromq-dev] not binging to all LISTEN port

2014-09-23 Thread Charles Remes
...@lists.zeromq.org [zeromq-dev-boun...@lists.zeromq.org] on behalf of Charles Remes [li...@chuckremes.com] Sent: Tuesday, September 23, 2014 11:44 AM To: ZeroMQ development list Subject: Re: [zeromq-dev] not binging to all LISTEN port Mohit, Your application should have end-to-end latency and throughput

Re: [zeromq-dev] not binging to all LISTEN port

2014-09-23 Thread Pieter Hintjens
] Sent: Tuesday, September 23, 2014 11:44 AM To: ZeroMQ development list Subject: Re: [zeromq-dev] not binging to all LISTEN port Mohit, Your application should have end-to-end latency and throughput measurements. I build this functionality into any project that uses zeromq so that I can

[zeromq-dev] not binging to all LISTEN port

2014-09-22 Thread Mohit Anchlia
I have a code that binds zeromq socket to 20-22 sockets, however when I look at netstat it is only binding to 5 sockets. The log message is being printed 22 times with 22 unique port numbers and there doesn't seem to be any error logged or exception throws either. I am trying to understand why I