ZeroMQ 4.3.4-GCCcore-11.2.0

ZeroMQ looks like an embeddable networking library but acts like a concurrency framework. It gives you sockets that carry atomic messages across various transports like in-process, inter-process, TCP, and multicast. You can connect sockets N-to-N with patterns like fanout, pub-sub, task distribution, and request-reply. It's fast enough to be the fabric for clustered products. Its asynchronous I/O model gives you scalable multicore applications, built as asynchronous message-processing tasks. It has a score of language APIs and runs on most operating systems.

Accessing ZeroMQ 4.3.4-GCCcore-11.2.0

To load the module for ZeroMQ 4.3.4-GCCcore-11.2.0 please use this command on the BEAR systems (BlueBEAR, BEARCloud VMs, and CaStLeS VMs):

module load bear-apps/2021b
module load ZeroMQ/4.3.4-GCCcore-11.2.0

BEAR Apps Version

2021b

Architectures

EL8-cascadelakeEL8-haswellEL8-icelake

The listed architectures consist of two part: OS-CPU.

  • BlueBEAR: The OS used on BlueBEAR is represented by EL and there are several different processor (CPU) types available on BlueBEAR. More information about the processor types on BlueBEAR is available on the BlueBEAR Job Submission page.
  • BEAR and CaStLeS Cloud VMs: These VMs can have one of two OSes. Those with access to a BEAR Cloud or CaStLeS VM should check that the listed architectures for an application include the OS of VM being used. The VMs, irrespective of OS, will use the haswell CPU type.

More Information

For more information visit the ZeroMQ website.

Dependencies

This version of ZeroMQ has a direct dependency on: GCCcore/11.2.0 libsodium/1.0.18-GCCcore-11.2.0 OpenPGM/5.2.122-GCCcore-11.2.0 util-linux/2.37-GCCcore-11.2.0

Required By

This version of ZeroMQ is a direct dependent of: IPython/7.26.0-GCCcore-11.2.0 IRkernel/1.3-foss-2021b-R-4.2.0

Other Versions

These versions of ZeroMQ are available on the BEAR systems (BlueBEAR, BEARCloud VMs, and CaStLeS VMs). These will be retained in accordance with our Applications Support and Retention Policy.

Last modified on 6th July 2022