RZMQ, ZeroMQ

rzmq is the first io-uring, highest throughput, low latency, fastest ZeroMQ implementation out there

zeromq,rust,rzmq,zmq

10 posts in this saga
Updated at Aug 31 2026 at 05:00 UTC

  • rzmq 0.5.24: Another Performance LEAP, Doubled Throughput (17 GB/s) on io_uring with sharded workers

    1 of 10 |
    Updated at

    rzmq 0.5.24: crates.io | Github - Async, Pure Rust ZeroMQ with Leading Performance on Linux

    After some experimenting, I found that io uring was maxed out on a single thread meaning multiple connections could saturate it, so it's been a long time coming, io_uring sharded workers is here! Yes, rzmq's io_uring is no longer one single thread, it's multiple threads now and meets or beats Tokio in throughput.

    I knew there was always more throughput on the table because Tokio could do it and I always had a plan to h...

  • rzmq 0.5.19: MASSIVE Performance, delivering 16 GB/s Throughput, a 100% increase over 0.5.18, and Correctness Updates

    2 of 10 |
    Updated at

    rzmq 0.5.19: crates.io | Github - Async, Pure Rust ZeroMQ with Leading Performance on Linux


    In my earlier post about what was coming in rzmq 0.5.19, I said it would be an 8GB/s update to 11GB/s update, ha I was wrong and it went up to an INSANE 16.2 GB/s! After much optimization and much pain coming from bugs from both rzmq and fibre, I deliver the highest throughput ZeroMQ library in the world.

    Also in this update are more socket options like enabling ZMTP 2.0 for old devices. Someone had it implemented in t...

  • rzmq Update: Continuing Tokio and io-uring Restructure for Performance and Correctness

    3 of 10 |
    Updated at

    I've been dedicating time to make rzmq much faster more cpu/memory efficient across the board and more correct. 0.5.17 was step up and 0.5.18 was a minor but good performance update

    Upcoming version 0.5.19 is shaping up to be a huge performance and correctness update due to fibre bug fixes and efficiency and performance updates (batching) and general rzmq restructuring. Many bugs were found and squashed. Data flows are being simplified and less generalized. io-uring was substantially improved. There's more c...

  • rzmq 0.5.17 is out with Massive Performance Updates to IO-uring Path

    4 of 10 |
    Updated at

    Crates.io

    Performance Highlight

    TCP Loopback (tcp://127.0.0.1), 10-second window, release build on an AMD Ryzen 5 7640U

    • 2.2 M msg/s — PushPull · 64 B · Linux · io_uring + cork · 4 workers
    • 6.6 GB/s — PushPull · 32 KB · Linux · io_uring + cork + multishot + zerocopy · 8 workers

    This, I imagine, is near saturation levels on a TCP Loopback pretty much limited by CPU/Memory Bandwidth. No other ZeroMQ library achieves this insane level of throughput. None.

    The IO-uring path was simplified, write paths using far more e...

  • RZMQ with IO-Uring is Extremely Fast and It's the Only ZeroMQ Implementation with IO-URing.

    5 of 10 |
    Updated at

    rzmq is now on 0.5.13 available on crates.io. This release adds an option to disable automatic delimiter for dealer/router sockets for interoperability purposes, it was a request.

    0.5.12 migrated the io-uring implementation to use a "framer" pattern to encapsulate common operations and share code between the regular socket actor and io-uring. It's faster and more efficient.

    rzmq's throughput is quite amazing really. I tested, with io-uring and TCP CORK enabled, 200k/responses per second on my Framework Laptop...

  • From Solid to Supercharged: The XSMB V2 Evolution and Why RZMQ Rocks

    6 of 10 |
    Updated at

    I'm still buzzing from a recent overhaul on a project that’s near and dear to my heart – my internal messaging backbone, XSMB. What started as a solid performer (V1) has just undergone a transformation into what I can only describe as a communications beast (V2), and I wanted to share a bit about the journey and the sheer power that has been unlocked.

    V1 Was Great, But I Dreamt Bigger

    XSMB V1 has been a workhorse for my server-to-server communication for ages (7 years?). Think reliable RPCs, straightforward ...

  • RZMQ: World's First XTREME High Performance ZeroMQ with Rust and io_uring!

    7 of 10 |
    Updated at

    I'm freakin elated to share something I've been hammering away at: rzmq – a pure Rust, async ZeroMQ that's aiming for (and achieving!) a new level of performance on Linux!

    If you've been in the distributed systems or messaging game, ZeroMQ (ØMQ) is legendary. It's the swiss-army knife, powerful and flexible. But what if we could take that solid foundation and supercharge it with modern Rust and the raw power of Linux's io_uring? That's rzmq.

    The "Why": Rust, Raw Speed, and a Modern Take

    So, what's the bi...

  • ZeroMQ RPC Extreme High Performance or 280k Requests/Response Per Second.

    8 of 10 |
    Updated at

    When I say RPC request and response, that means the request and response were serialized/deserialized with messagepack. It's just message passing in the end.

    ZeroMQ is fast I mean really really fast. ZeroMQ is a networking library and should be part of any toolkit where you need extreme high performance and reliability between applications.

    Let's do some math

    140k requests per second + 140k responses per second = 280k req/response total. That's 2.8 million in a 10 second span. This measly server can handle m...

  • Spotify used ZeroMQ at One Point for Internal Server Communications

    9 of 10 |
    Updated at

    I was curious about use of ZeroMQ since I use it extensively with my own RPC, PubSub system.

    Spotify's Hermes

    Hermes is a network messaging stack created at Spotify, on top of existing open source stack such as ZeroMQ, protobuf and gevent. We are migrating backend service from legacy stack to Hermes and this session explains the rationale behind some of the choices. It also gives a brief introduction of some typical network topology for backend messaging at Spotify. Finally we discuss some lessons lear...

  • Building a ZeroMQ based Service Discovery application

    10 of 10 |
    Updated at

    Introduction

    Service Discovery, the phonebook of applications, is a foundation for services oriented architecture. It answers the question of how does one service dynamically discover the endpoints of another service.

    It is not a new thing that came with microservices. Zookeeper is a famous application for implementing service discovery on regardless of requirements. I give it good praise for the things you can do with it. If you don't have a lot of time to spend I recommend it.

    Use Case

    Building on top of ...