#jit
Live, measured metrics for the hashtag #jit from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #jit
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 · mastodon.social (Mastodon public tags API) · fetched 2026-07-27 08:55 UTC3 uses by 3 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.social (Mastodon public search API) · fetched 2026-07-27 08:55 UTCLive pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-07-27 08:55 UTCEverything below is measured over the latest 40 public posts (spanning ~8315 hours).
Posting hours (UTC) — busiest: 07:00
Languages: English (17) · Russian (7) · Chinese (Taiwan) (2) · Japanese (2) · Korean (2) · French (1)
Avg boosts / post: 0.3
Top of the latest posts
People of the past, I have chosen the next emulator to add an #arm #jit to. #next #previous #retrocomputing
step 1: do an experimental JIT step 2: do a website called https://www.doesjitgobrrr.com to track performance step 3: write a PEP called "JIT Go Brrr" step 4: non-experimental JIT gone brrr? step 5: CPython gone brr? step 6: brrr? https://p
@schenklklopfer Huh, interesting. cPython 3.12.3: 9475.86 MB/s PyPy (nightly, default settings): 4378.93 MB/s PyPy (nightly, --jit off): 3676.98 MB/s My guess: Most of the time is spent in bytes.find(), which is a highly optimized C functio
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/jit