# Introducing Zigrupt: a high-performance inter-thread event broadcasting library for Zig **URL:** \ **Category:** Showcase\ **Tags:** performance, llm, concurrency\ **Created:** [October 18, 2026, 2:22am UTC](https://ziggit.dev/t/introducing-zigrupt-a-high-performance-inter-thread-event-broadcasting-library-for-zig/18015 "2026-10-18T02:22:25Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![sarthakvk](https://ziggit.dev/user_avatar/ziggit.dev/sarthakvk/32/10019_2.png) [@sarthakvk](https://ziggit.dev/u/sarthakvk)\ **Post date:** [October 18, 2026, 2:22am UTC](https://ziggit.dev/t/introducing-zigrupt-a-high-performance-inter-thread-event-broadcasting-library-for-zig/18015/1 "2026-10-18T02:22:25Z")
# [Zigrupt](https://github.com/sarthakvk/zigrupt) * * * - Zigrupt is heavily inspired by the [LMAX Disruptor](https://github.com/LMAX-Exchange/disruptor). - It lets application threads publish events once and have multiple handlers process every event, in order, on their own threads. - It uses a ring buffer, atomics and memory barriers to make the even broadcasting lock-free, plus it uses cache-line optimizations to avoid false-sharing, adding all those up you get very low latency when compared to a simple mutex based queue. These optimizations were adapted from the LMAX design itself. - [Benchmarks](https://zigrupt.sarthakvk.com/performance/) with two similar tool in Java and Rust. Zigrupt outperforms them or give similar performance(there’s some cases where the Zigrupt lags behind which I am working on to resolve) ### Ongoing development and release: > Although I released an early version(v0.0.1), this is still a WIP as I did not yet implement all the features that the OG LMAX disruptor supports for example consumer dependencies etc. ### Supported Zig versions: 0.16 ### AI / LLM usage disclosure > The implementation of the zigrupt was done by me with my hands but I used the AI to write documentation, benchmarking tool and also have it write many of my application tests.