#zswap
Live, measured metrics for the hashtag #zswap from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #zswap
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 · fosstodon.org (Mastodon public tags API) · fetched 2026-09-26 04:23 UTC1 uses by 1 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-09-26 04:23 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-09-26 04:23 UTCEverything below is measured over the latest 37 public posts (spanning ~63501 hours).
Posting hours (UTC) — busiest: 15:00
Languages: English (27) · Spanish (2) · Chinese (1) · German (1) · Russian (1) · zhTw (1)
Avg boosts / post: 0.2
Top of the latest posts
According to LWN kernel source DB, the number of my Linux mainline commits exceeded 1,000 with 6.19-rc1. It feels like a moment to me. Most commits were made for DAMON, but the 1,000-th commit was for zswap ;) $ git log --oneline --author "
Some various performance improvements for Debian 12 Bookworm Here some various improvements I implemented on some of my Debian 12 Bookworm servers in order to improve performance. zswap: use zsmalloc allocator with newer kernel If your syst
Zswap - I'm slightly saddened by the reality, that #zswap compresses data only in the memory page pool and when it writes data out to #disk, the data is decompressed. Oh why?! Why it doesn't write the compressed data to disk, and then only
What “zswap” means
Wikipediazswap is a Linux kernel feature that provides a compressed write-back cache for swapped pages, as a form of virtual memory compression. Instead of moving memory pages to a swap device when they are to be swapped out, zswap compresses them and then stores them in a memory pool dynamically allocated in the system RAM. This way, writeback to the actual swap device is deferred or even completely avoided, resulting in a significantly reduced I/O load for systems that require swapping; the tradeoff is
“Zswap” on Wikipedia (CC BY-SA) →#zswap across platforms
every network with a public tag surfaceFollow #zswap 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/zswap