[zeromq-dev] ZeroMQ on AIX

gonzalo diethelm gdiethelm at dcv.cl
Sun Aug 7 04:36:55 CEST 2011

Hi Martin,

I don't have a "public" AIX box; I will have to see about building and testing my own version of 0MQ.

The strategy is that the clients will generate all the relevant data in separate files, each identified by a UUID (to provide unique identities without depending on a central resource). It is this UUID that is sent to the server, to notify it about the need to process a file. The server will wake up periodically anyway and will process any pending files, so the messages could be skipped altogether; they will be used to lower latency. Based on what you say, I think it makes more sense going with a high HWM on the server. This is also the reason why I think I will stick with version 2.1.x.

Thanks for the direct pointer to the UUID code; it will come in handy.

Best regards.
From: Martin Sustrik [sustrik at 250bpm.com]
Sent: Saturday, August 06, 2011 3:27 AM
To: ZeroMQ development list
Cc: gonzalo diethelm
Subject: Re: [zeromq-dev] ZeroMQ on AIX

Hi Gonzalo,

> 1. Anybody has experience with 0MQ on AIX? Any hints, pointers or
> caveats? I am assuming 0MQ has been ported to AIX, to begin with!!!

It's been done, however, the builds are not done automatically, so you
have to check whether latest version haven't broken AIX compatibility
since it was last checked. In case you have an Internet-facing AIX box
available, we can add it to the build cluster, thus assuring 0MQ always
works on AIX.

> 2. The requirements are very simple and the model looks sound, but I
> just wanted to run it by the list. Any thoughts? In particular, I would
> like to set an HWM on the daemon’s incoming Sub socket to a high value,
> in the hopes that I will not miss any notifications from the client(s).
> What is a good number for this high value? What impact does that number
> have on resource usage on the daemon?

The incoming messages have to be stored till they are processed, if you
set high HWM on server, they'll be stored at server. If you set low HWM
on server, they'll be stored at the clients. High HWM has no impact on
memory usage when there are no messages to store.

> 3. What version of the 0MQ library should I use? I would rather stick to
> the latest, which I understand is 3.x, but I am not sure if there are
> any instabilities that could impact this (admittedly simple) use case.

Depends on what you need. If all you need is passing all the messages to
the server, 2.1.x would be good. If the server can ask only for a subset
of messages and you want clients to filter the messages and avoid
passing unneeded messages over the network you'll need 3.0.x (there's
subscription forwarding feature there).

> 4. I will need to generate UUIDs in the client program. This is not very
> portable and is rather a pain in the ass (never done it before on AIX).
> Does 0MQ export its UUID generation function? It would come in really handy…

No it does not. The dependency on libuuid is removed in post-3.0.x
versions so it's not a good idea to expose it now just to remove it later.

Here's the code that generates UUIDs on AIX:



Declaración de confidencialidad: Este Mensaje esta destinado para
el uso de la o las personas o entidades a quien ha sido dirigido y
puede contener información reservada y confidencial que no puede
ser divulgada, difundida, ni aprovechada en forma alguna. El uso no
autorizado de la información contenida en este correo podrá ser
sancionado de conformidad con la ley chilena. 
Si usted ha recibido este correo electrónico por error, le pedimos
eliminarlo junto con los archivos adjuntos y avisar inmediatamente
al remitente, respondiendo este mensaje. 

"Before printing this e-mail think if is really necesary".
Disclosure: This Message is to be used by the individual,
individuals or entities that it is addressed to and may include
private and confidential information that may not be disclosed,
made public nor used in any way at all. Unauthorized use of the
information in this electronic mail message may be subject to the
penalties set forth by Chilean law. 
If you have received this electronic mail message in error, we ask
you to destroy the message and its attached file(s) and to
immediately notify the sender by answering this message. 

More information about the zeromq-dev mailing list