Urgent.News

What's breaking now, across thousands of outlets.

Tech

Why Running the yes Command Didn't Max Out CPU Usage

Introduction I needed to generate CPU load on a Linux server for testing purposes. Looking for a quick solution, I executed the yes command like this: yes > /dev/null The yes command continuously outputs "y" infinitely. I assumed that "since it's an infinite loop, CPU usage should reach 100%," but when I checked the results, something unexpected happened. Info: The test environment I used was a…

The author needed to generate CPU load on a Linux server for testing purposes. They executed the yes command, which continuously outputs "y" infinitely, assuming it would max out CPU usage. However, the results were unexpected. When they checked with the top command, they saw that while the yes process was using 100% of one CPU core, overall CPU usage was only around 50%.

This was because the yes command operates as a single-threaded process, meaning it can only run on one CPU core at a time. The overall CPU usage was split between the two cores, with one core at 100% and the other at around 50%. To load all CPU cores, multiple processes proportional to the number of CPU cores are needed. The speed of yes doesn't improve with more cores because it's single-threaded.

The article emphasizes the importance of understanding the underlying processes to gain insights into how Linux and operating systems function.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Papra document sharing crosses organization and instance boundaries

Papra document sharing crosses organization and instance boundaries Papra is a self-hosted document archiving platform organized around users, organizations, documents, custom properties, API keys…

  • Papra is a self-hosted document archiving platform for private or organization-wide use.
  • November 21, 2026 search returned 26 index matches for Papra instances.
  • Security measures include TLS deployment, private networks, and tested deletion/recovery process.

Kyverno CLI and conftest in CI vs Kyverno at admission

Kapitan compiles an inventory into plain YAML under compiled/ . The registry's compile diff action shows a reviewer what a pull request changes in that YAML.

  • Kyverno CLI and conftest used in CI pipelines to check policies
  • Kyverno CLI checks policy compliance on compiled YAML files
  • conftest runs Rego rules against objects, noncompliant target fails

React and CSS: An Accessible Email Frontier

An email field may seem small, but it is often the frontier between a friendly interface and a difficult-to-understand flow.

  • React component defines email status states: idle, checking, accepted, invalid, expired
  • Separates format validation from backend verification, prevents CSS from guessing logic
  • Uses aria attributes for accessibility, min-height for layout protection

More from Friday 20 November →