[zeromq-dev] not binging to all LISTEN port

Pieter Hintjens ph at imatix.com
Tue Sep 23 19:43:04 CEST 2014


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 <mohitanchlia at gmail.com> wrote:
> 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 being a bottleneck. How can I really tell if I need to scale?
>
> On Tue, Sep 23, 2014 at 10:30 AM, Gregg Irwin <gregg at pointillistic.com>
> wrote:
>>
>> 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
>> outline, and the number and size of messages you need to support, you
>> may get one of three answers borne of experience by users here.
>>
>> 1) No problem. You are well within a single socket's capabilities.
>>
>> 2) One socket will not support that load. You might need N sockets.
>>
>> 3) It could be close. You should test in your environment.
>>
>> -- Gregg
>>
>> _______________________________________________
>> zeromq-dev mailing list
>> zeromq-dev at lists.zeromq.org
>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>
>
>
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>



More information about the zeromq-dev mailing list