[erlang-questions] 0MQ libraries

[Mahesh Paolini-Subramanya]

The main thing I used to see was VM memory exhaustion due to 0MQ being just
too damn fast.
But that was more of a "No AQM in my code" issue :-)

Sent via smoke signals...
Mahesh Paolini-Subramanya
That tall bald Indian guy...
On Jan 30, 2014 5:46 PM, "Michael Truog" <mjtruog@REDACTED> wrote:

> On 01/30/2014 02:22 PM, Garrett Smith wrote:
>
>> On Thu, Jan 30, 2014 at 4:20 PM, Benoit Chesneau <bchesneau@REDACTED>
>> wrote:
>>
>>  On Thu, Jan 30, 2014 at 10:58 PM, Garrett Smith <g@REDACTED> wrote:
>>>
>>>  Speed kills.
>>>>
>>> What do you mean? I like better to have a stable solution? How did you
>>> benchmarked it?
>>>
>> We are in agreement on stability :)
>>
>> There's a benchmark tool in the library.
>>
>> Garrett
>> _______________________________________________
>> erlang-questions mailing list
>> erlang-questions@REDACTED
>> http://erlang.org/mailman/listinfo/erlang-questions
>>
>>  I guess your concerns about stability are confusing.  The main issues
> are bugs within the ZeroMQ source code:
> https://zeromq.jira.com/browse/LIBZMQ-478
> https://zeromq.jira.com/browse/LIBZMQ-496
>
> The LIBZMQ-496 was fixed in 3.2.3 while LIBZMQ-478 remains unresolved.  I
> see no reason to doubt the stability of erlzmq2, since these errors are
> handled in a way that causes no instability within the Erlang VM.  The
> erlzmq2 is using a separate thread, so it doesn't have the Erlang scheduler
> lock-up issue that remains a problem for all long-running NIF/BIF functions.
>
> So, what instability are you referring to?
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20140130/0bed4a4a/attachment.htm>