#kworker

Live, measured metrics for the hashtag #kworker from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.

hashtag.org network · sponsored

Own #kworker

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.

$240.06/ year · 7-character #name
Claim #kworker$240.06/yrBuy on hashtag.space (web3)
card via hashtag.org · tokens via hashtag.space
0
Uses / 7 days
Mastodon
0
Accounts / 7 days
Mastodon
7
Recent posts
Mastodon
~0/hr
Recent pace
Mastodon · last 7
0.1
Avg reactions / post
Mastodon · last 7

Day-by-day usage

measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-27 20:36 UTC
0
07-21
0
07-22
0
07-23
0
07-24
0
07-25
0
07-26
0
07-27

0 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 20:36 UTC

Live pulse

measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 20:36 UTC

Everything below is measured over the latest 7 public posts (spanning ~40681 hours).

Posting hours (UTC)

00:0012:0023:00

Languages: Italian (4) · English (2) · German (1)

Avg boosts / post: 0.4

Top of the latest posts

  • Could some full time kernel head tell me: how does a #kworker get towards to the busy end of top in state Idle? If its Idle why does it have >0.1% CPU ? My CPUs are recent enough & desktop power #linuxkernel uname == "Linux hiss 5.19.0-43-g

    Owen Beresford@channelOwen102023-06-22 19:58 UTCView post →
  • Endurance test on a 2009 Atom N450 netbook! 🛠️ ​This Acer Aspire One always failed on standard Linux due to a frustrating #kworker CPU spike, making it unusable. We're challenging that with #BashCoreZ_RT for 48 hours. ​Goal: Prove our extr

    nickbearded@[email protected]012025-11-10 18:24 UTCView post →
  • [Post-mortem: BashCore Stress Test Investigation] Test ended on Day 5. The system didn’t crash, but I noticed the fan was working overtime. The main suspect? kworker/0:3+kacpid turns out it was busy with ACPI tasks (power management). So te

    nickbearded@[email protected]002025-04-12 12:08 UTCView post →

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/kworker