#flamegraph
Live, measured metrics for the hashtag #flamegraph from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #flamegraph
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 10:18 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 10:18 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 10:18 UTCEverything below is measured over the latest 25 public posts (spanning ~31049 hours).
Posting hours (UTC) — busiest: 08:00
Languages: English (19) · French (3) · Russian (3)
Avg boosts / post: 2.4
Top of the latest posts
Inspecting flamegraphs is a pain - dealing with SVG files, opening a browser… ugh. Not anymore! 🔎 **flamelens** — An interactive flamegraph viewer for the terminal. 🔥 Works with perf, py-spy and cargo-flamegraph. 🦀 Written in Rust & buil
Here is how you can add CPU profiling to your Rust project! 🦀 ⏱️ **pprof**: A Rust CPU profiler — supports generating flame graphs! 🔥 📚 Docs: https://docs.rs/pprof ⛰️ Example implementation from @git_cliff → https://github.com/orhun/git-
Morning ☕ with the #flamegraph 🔥 taken on #FreeBSD 15.0-STABLE
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/flamegraph