#jemalloc
Live, measured metrics for the hashtag #jemalloc from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #jemalloc
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-07-27 13:26 UTC0 uses by 0 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-07-27 13:26 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 13:26 UTCEverything below is measured over the latest 40 public posts (spanning ~44439 hours).
Posting hours (UTC) — busiest: 17:00
Languages: English (34) · Russian (3) · Chinese (2) · Korean (1)
Avg boosts / post: 0.5
Top of the latest posts
At $dayjob, we have an embedded #Linux device that is periodically running low on memory. It's using the default (#glibc) allocator. No leaks, and lowering MALLOC_MMAP_THRESHOLD_ made the problem go away. So: memory fragmentation. With glib
Fun project: a #memory manager for multi-lang applications (#c, #cplusplus #assembly #fortran) in which workflow management is done by #Perl. Currently allocates using either #perl strings or #glibc malloc/calloc. Other allocators #jemalloc
Jemalloc seems to be back: jemalloc 5.3.1 Released With Many Improvements After Nearly Four Year Hiatus: https://www.phoronix.com/forums/forum/software/programming-compilers/1626721-jemalloc-5-3-1-released-with-many-improvements-after-nearl
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/jemalloc