#vectorengine
Live, measured metrics for the hashtag #vectorengine from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #vectorengine
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-31 11:43 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-31 11:43 UTCNo related tags with measured usage found for #vectorengine.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-31 11:43 UTCEverything below is measured over the latest 37 public posts (spanning ~24471 hours).
Posting hours (UTC) — busiest: 22:00
Languages: English (31) · German (6)
Avg boosts / post: 0.8
Top of the latest posts
A #NEC #VectorEngine card crunches double precision (FP64) numbers for breakfast. I measured ~2TerraFLOPs on a 2 slot card made on TSMC 12nm is competitive with combined theoretical Float64 output of an NVIDIA 4090 and an NVIDIA 4080 made o
The fortran compiler for the #VectorEngine is in the public packages now. I ran my first Fortran program for it. Sadly the system update i did broke the driver. So i was greated by this instead.😅 Luckily the kernel dependent part of the dr
@fclc I attended a programming course for the NEC #VectorEngine last week. @[email protected] hosted it and gave access to their cards. So i already had a flavor and it was addictingly sweet.
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/vectorengine