#performancetesting
Live, measured metrics for the hashtag #performancetesting from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #performancetesting
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-09-27 22:38 UTC0 uses by 0 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-09-27 22:38 UTCNo related tags with measured usage found for #performancetesting.
Live pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-09-27 22:38 UTCEverything below is measured over the latest 38 public posts (spanning ~123524 hours).
Posting hours (UTC) — busiest: 15:00
Languages: English (32) · Dutch (3) · Portuguese (1) · Basque (1)
Avg boosts / post: 0.8
Top of the latest posts
#PostgreSQL 18 just landed—and I built a benchmark dashboard comparing PG versions 12–18 using pgbench mix tests: https://pgbench.github.io/mix/ PG18 leads in every metric: - 3,057 TPS - 5.232 ms latency - 183,431 transactions Have you test
🚀 Thanks to everyone who checked out DNS Benchmark Tool here on Mastodon! I shared the release across networks, but it was the Hacker News community that really pushed adoption forward — stars jumped from 7 → 110+ and downloads rebounded t
At Gibe, we started using Grafana's k6 for performance testing. It was so easy to get going with that I wrote a beginner's guide to help you get started. Tired of clunky, XML-heavy load testing tools? k6 lets you write tests in modern JS, k
#performancetesting across platforms
every network with a public tag surfaceFollow #performancetesting straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
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/performancetesting