5 ms·
libxev: A cross-platform, high-performance event loop
- asveikau 3y ago[flagged]
- CharlesW 3y agoYep, macOS leverages a bunch of technologies and tools that originated in FreeBSD.
- mitchellh 3y agoHi, this is my project. The README only states that I use kqueue on macOS, but I don't claim it is specific or originated from macOS. I've read the README over a few times and can't find where you'd get the feeling that it's a macOS-only thing. If I can edit it in any way to make that clearer let me know. libxev is not compatible with BSD currently because macOS's kqueue API is very slightly different from BSDs to make it incompatible (i.e. I use mach ports a lot on macOS, but other parts of the syscall interface also vary slightly).
- asveikau 3y agoIf you depend heavily on Mach ports I don't think "kqueue (macOS)" is an accurate description. That makes it sound like it has more of a chance to work on BSD than it does.
- mitchellh 3y agoIt is an accurate description. The mach ports are waited on through kqueue, and I use kqueue for all other waiters with "standard" fds (i.e. files). But my usage of mach ports (even for a partial use case) make it incompatible with BSD, and even if I didn't use mach ports the kqueue structures used by macOS are slightly different and incompatible anyways, and I don't claim BSD support anywhere. It's splitting hairs and being a bit pedantic, but you also reordered my descriptions: in the README I always say "macOS (kqueue)" and not the reverse which you incorrectly quoted. I think that makes a small but tangible difference.
- asveikau 3y agoI did misread and misquote that. But when a remark is parenthetical I guess I consider them equivalent. macOS and kqueue is not equivalent. Maybe macOS (using kqueue and Mach ports) would make it clearer?
- cornstalks 3y agoNo one but you is saying macOS and kqueue are equivalent. OP’s phrasing is perfectly fine.
- jpgvm 3y agoCompletion based cross-platform I/O? Sign me up.
- dsp_person 3y agoCan this be used to make something that feels like Qt's signals and slots?
- jcelerier 3y agoMany signal/slot implementations are done synchronously without any event loop involved, the two are somewhat orthogonal. Even Qt will call the signals synchronously most of the time without the event loop involved, it's just an additional feature of it to queue the event in the event loop.
- gigatexal 3y agoon MacOS are kqueue and libdispatch/grand central dispatch doing different things?
- mitchellh 3y agoThis is my project. I use it as the core cross-platform event loop layer for my terminal (https://mitchellh.com/ghostty https://mitchellh.com/ghostty). I still consider libxev an early, unstable project but the terminal has been in use by hundreds to now over a thousand beta testers daily for over a year now so at least for that use case its very stable. :) I know of others using it in production shipped software, but use it at your own risk. As background, my terminal previously used libuv (the Node.js core event loop library), and I think libuv is a great project! I still have those Zig bindings available (archived) if anyone is interested: https://github.com/mitchellh/zig-libuv https://github.com/mitchellh/zig-libuv The main issue I had personally with libuv was that I was noticing performance jitter due to heap allocations. libxev's main design goal was to be allocation-free, and it is. The caller is responsible for allocating all the memory libxev needs (however it decides to do that!) and passing it to libxev. There were some additional things I wanted: more direct access to mach ports on macOS, io_uring on Linux (although I think libuv can use io_uring now), etc. But more carefully controlling memory allocation was the big one. And it worked! Under heavy IO load in my terminal project, p90 performance roughly matched libuv but my p99 performance was much, much better. Like, 10x or more better. I don't have those numbers in front of me anymore to back that up and my terminal project hasn't built with libuv in a very long time. But I consider the project a success for my use case. You're probably better off using libuv (i.e. the Node loop, not my project) for your own project. But, the main takeaway I'd give people is: don't be afraid to reimplement this kind of stuff for you. A purpose-built event loop isn't that complicated, and if your software isn't even cross-platform, it's really not complicated.
- ajoseps 3y agoI saw ghostty and thought, “isn’t that the terminal written by the guy who cofounded hashicorp?”. I really enjoy your ghostty blog posts and will be checking out libxev!
- samsquire 3y agoThank for you for sharing. What do you think are the next steps for a next generation event loop? I've been experimenting with barriers/phasers, LMAX Disruptors and my own lock free algorithms. I think some form of multithreaded structured concurrency with coroutines and io_uring. I've been experimenting with decoupling the making sending and recv independently parallel with multiple io_urings "split parallel io" - so you can process incoming traffic separately from the stream that generates data to send. Generating sends is unblocked by receive parsing and vice versa. Interested in seastar and reactors.
- jauntywundrkind 3y agoio_uring support is obviously great & excellent, fulfills the "high performance" part well. brought an immediately smile to my face. i was not expecting "Wasm + WASI" support at all. that's very cool. implementation is wasi_poll.zig (https://github.com/mitchellh/libxev/blob/main/src/backend/wasi_poll.zig https://github.com/mitchellh/libxev/blob/main/src/backend/wa...). not to be unkind, but this makes me wonder very much if WASI is already missing the mark, if polling is the solution offered. gotta say, this is some very understandable clean code. further enhancing my sense that i really ought be playing with zig.
- Jarred 3y agoWe copied libxev's code for the timer heap implementation in Bun for setTimeout & setInterval, and it was a ~6x throughput improvement[0] on Linux compared to our previous implementation. [0]: https://twitter.com/jarredsumner/status/1736741811039899871 https://twitter.com/jarredsumner/status/1736741811039899871
- hinkley 3y agoWhy do you suppose node is still 50% faster on this benchmark? v8 trickery or something in the library differences?
- Jarred 3y agoThe timer heap currently lives on a different thread instead of the main thread, which means timers have to be allocated and scheduled separately for each one. Scheduling things to other threads is expensive. The reason it works this way isn't good and we will fix it but haven't prioritized it yet
- hinkley 3y agoI was going to say, "I wonder if Bun.js would/could use this" but it looks like Jarred Sumner has been cherry-picking bits of libxev for at least six months.
- eqvinox 3y agoAs someone maintaining a project with its own event loop: don't do it in larger projects. The problem is that you'll start having dependencies on external libraries. And when those then need event loop integration, things get messy. We've introduced bugs before, caused by subtle differences in semantics. (Like: does write imply read? Are events disarmed while running? What about errors?) If the lib and event loop are reasonably popular, someone else probably has integrated them before. Or the lib supports the event loop natively (or uses libverto.) Either saves you some trouble. Also: please add libverto support for your event loop :) https://github.com/latchset/libverto https://github.com/latchset/libverto
- GoblinSlayer 3y agoThe interface looks like verto is linux first design, like git. But what's the point? Just implement epoll like Illumos did. Also allocation heavy and apparently can't use deno-style loop.