#avx512
Live, measured metrics for the hashtag #avx512 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #avx512
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-29 19: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-29 19:26 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 19:26 UTCEverything below is measured over the latest 40 public posts (spanning ~17593 hours).
Posting hours (UTC) — busiest: 12:00
Languages: English (30) · Russian (7) · German (1)
Avg boosts / post: 0.7
Top of the latest posts
So here's an idea i had that i'm almost certainly not going to do anything with (so you should). With AVX-512 we have 16 x 32-bit registers. Let's pretend that's a 16-deep stack. The permute instruction let us do a DROP and DUP (except, you
New blog post "Sep 0.10.0 - 21 GB/s CSV Parsing Using SIMD on AMD 9950X 🚀" 📈 Sep #performance from 7 GB/s to 21 GB/s over last two years 🧑💻 #csharp #SIMD and #x64 assembly on #dotnet 9.0 🛠️ Tweaks and new #AVX512-to-256 parser 🔢 Lots
FWIW, the code uses #AVX512 at other places in the code. That could be related (i.e. some alignment issue?). But I'm lost as how to find the right spot as the code the debuggers point to has no AVX512.
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/avx512