[zeromq-dev] Device CPU Utilization

[Jason Sia]

Had you experienced cpu usage going up to 100% for this kind of a setup
even though there are no incoming transactions to the device?

On Mon, Aug 17, 2015 at 11:50 AM, Kenneth Adam Miller <
kennethadammiller at gmail.com> wrote:

> Whoops, I spoke too soon. Yeah um, ignore that, I missed a part of that.
> On Aug 16, 2015 11:48 PM, "Kenneth Adam Miller" <
> kennethadammiller at gmail.com> wrote:
>
>> I'm pretty sure that bind_out_sock should be set up with a connect call,
>> and the bind_ prefixes might be left off.
>> On Aug 14, 2015 10:38 AM, "Jason Sia" <jsia18 at gmail.com> wrote:
>>
>>> Hi,
>>>
>>> I'm using zeromq 2.2.0 version due to some library dependency, I created
>>> a streamer device push pull , for some reason and its intermittent.  The
>>> cpu usage of the device grows to 100% even if the pusher is only inputting
>>> at a slow rate.  I used pyzmq and then also created a version in C++.
>>>
>>> Here is my code:
>>>
>>> #include <iostream>
>>>
>>> #include <stdlib.h>
>>>
>>> #include <zmq.hpp>
>>>
>>> using namespace std;
>>>
>>> zmq::context_t ctx(1);
>>>
>>> zmq::socket_t bind_in_sock(ctx, ZMQ_PULL);
>>>
>>> zmq::socket_t bind_out_sock(ctx, ZMQ_PUSH);
>>>
>>> int main(int argc, const char *argv[]) {
>>>
>>>     bind_in_sock.bind("tcp://0.0.0.0:12000");
>>>
>>>     bind_out_sock.bind("tcp://0.0.0.0:11001");
>>>
>>>     zmq::device(ZMQ_STREAMER, bind_in_sock, bind_out_sock);
>>>
>>>     return 0;
>>>
>>> }
>>> Is there a known issue about this?
>>>
>>> Thanks,
>>> Jason
>>>
>>> _______________________________________________
>>> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20150818/d6e81ac7/attachment.htm>