TGViewer
//devdigest //devdigest @devdigest · 376 subscribers
Post #2538 71
⚡️ Fixing High CPU Burn on GitHub Actions Runners

Self-hosted GitHub Actions runners can chew through CPU even when idle — one core locked at 100%, by design. The culprit is a busy-wait loop in the runner’s sleep logic, not your workflows. Digging into the code reveals a simple but costly tradeoff between responsiveness and efficiency.

♻️ Subscribe for free now!
Meziantou's blog Reduce GitHub Actions runner CPU usage In this post, I'll show you how to reduce the CPU usage of your self-hosted GitHub Actions runners by replacing the default busy-waiting sleep implementation with a more efficient one.
Open in Telegram All posts from @devdigest
More from @devdigest
  1. Oct 1, 2026⚡️ Transformers can now load llama.cpp GGUF quants directly via from_pretrained Hugging Fa…
  2. Sep 30, 2026⚡️ Azure Container Apps Sandboxes: an isolated microVM for an agent in seconds Hardware-is…
  3. Sep 25, 2026⚡️ Microsoft's live series builds a production AI agent in C# from scratch A four-part liv…
  4. Sep 23, 2026⚡️ Rider and ReSharper 2026.2.2 add an AI Agent Setup widget and sharper coding-agent hook…
  5. Sep 22, 2026⚡️ Environment.ProcessorCount reports process limits, not host cores, since .NET 6 Andrew…
  6. Sep 22, 2026⚡️ Workflow1111 rebuilds the AUTOMATIC1111 feature set on a single gr.Workflow canvas Elev…
Threads Profile ViewerView any public Threads profile without an account.Open ThreadLook →Writing with AI? Make it sound human.Metric37 rewrites AI drafts so they read naturally. Free AI detector, 1,500 words free.Try Metric37 →