#1brc
Live, measured metrics for the hashtag #1brc from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #1brc
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 07:14 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 07:14 UTCNo related tags with measured usage found for #1brc.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 07:14 UTCEverything below is measured over the latest 40 public posts (spanning ~20907 hours).
Posting hours (UTC) — busiest: 10:00
Languages: English (37) · Polish (2) · Japanese (1)
Avg boosts / post: 0.6
Top of the latest posts
Somebody did a pretty decent run at 1-billion-row-challenge with node. The author got it down to ~11 seconds (on their machine). Considering how fancy-pants rust etc people are doing it in perhaps 3-4 seconds, I'd say pretty decent. https:/
Thank you @gunnarmorling for the awesome #1brc prize. This was the hardest earned coffee mug in my life! #GraalVM
How much faster can #Java get before the code becomes unmaintainable? Using the One Billion Row Challenge as a benchmark, @ReneSchwietzke explores the trade-offs between clean code, profiling insights & real-world performance tuning: https:
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/1brc