#liburing
Live, measured metrics for the hashtag #liburing from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #liburing
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · mas.to (Mastodon public tags API) · fetched 2026-09-26 17:43 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mas.to (Mastodon public search API) · fetched 2026-09-26 17:43 UTCNo related tags with measured usage found for #liburing.
Live pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-09-26 17:43 UTCEverything below is measured over the latest 2 public posts (spanning ~29375 hours).
Posting hours (UTC)
Languages: Russian (1) · English (1)
Avg boosts / post: 2.5
Top of the latest posts
io_uring без розовых очков: 5 граблей, которые сожгли мне неделю, и где он реально быстрее epoll io_uring продавали как убийцу epoll. На деле на HTTP keep-alive разница 0-15%, иногда не в его пользу. Но на NVMe с queue depth 128 - в 3 раза
```ublk-nbd[1] is available now. Basically it is one #nbd client, but totally implemented in userspace […] io handling is based on #liburing[3] […] ublk-nbd supports both tcp and unix socket, and allows to enable #io_uring send zero copy vi
What “liburing” means
Wikipediaio_uring is a Linux kernel system call interface for storage device asynchronous I/O operations. It addresses performance issues with similar interfaces provided by functions like read /write or aio_read /aio_write for operations on data accessed by file descriptors.
“Io uring” on Wikipedia (CC BY-SA) →#liburing across platforms
every network with a public tag surfaceFollow #liburing straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/liburing