stress-ng mit Homebrew, apk, apt, dnf, MacPorts, Nix, pacman, zypper installieren

Projektlinks

• Homepage
• Repository
• Upstream-Dokumentation
• Paketmanager-Seite

Befehle und Aliase

• stress-ng

Projektgeschichte

The in-tree Debian changelog records stress-ng 0.01.00 on 2013-10-15 as the initial version by Colin King. The upstream README describes stress-ng as the upstream project repository and says it was designed to exercise physical subsystems and operating-system kernel interfaces.

The project name means stress next generation, and the README now describes a large test surface: hundreds of stress tests, CPU-specific tests, virtual-memory tests, filesystem tests, and memory/cache tests. That growth changed it from a simple load generator into a toolkit for provoking kernel, platform, and hardware edge cases.

Adoptionsgeschichte

stress-ng is distributed across many Unix-like package managers in the supplied package facts, including apk, Homebrew, Debian, Fedora/dnf, MacPorts, Nix, pacman, Ubuntu, and zypper. Its README also points Ubuntu users to a project PPA for recent versions.

Its official Ubuntu wiki page is maintained as a kernel reference and quick-start guide, which reflects how the tool moved from a standalone utility into common kernel, distro, and hardware validation workflows.

Wie es verwendet wird

Common package-manager usage is installing `stress-ng` and running one or more named stressors with a timeout, such as CPU matrix work, scheduler classes, memory pressure, filesystem operations, or perf/metrics reporting. The Ubuntu guide emphasizes caution because the tests can heat hardware and cause heavy thrashing.

The README warns that stress-ng can measure throughput rates but is not intended as a precise benchmark suite. In package culture, that distinction matters: it is for reproducing stress and finding failures, not for publishing synthetic leaderboard numbers.

Warum Paket-Nerds sich dafür interessieren

stress-ng is beloved by system-package people because it is small to install, scriptable, broad in coverage, and useful immediately after a kernel, libc, compiler, VM, or hardware change.

For maintainers, it is also a packaging canary: if a platform port, sandbox, container, scheduler, filesystem, or architecture behaves oddly under stress-ng, there is probably a real bug worth chasing.

Zeitleiste

• 2013-10-15: In-tree Debian changelog records stress-ng 0.01.00 as the initial version.
• 2015-06-05: GitHub repository metadata records public repository creation.
• 2019: Ubuntu wiki reference guide documents typical stress-ng use cases for kernel and system testing.
• 2026: README describes more than 380 stress tests and broad portability across Unix-like systems and related environments.

Related projects

• `stress` is the older load-generation tool that stress-ng effectively supersedes for broader kernel and subsystem coverage.
• Ubuntu kernel testing, Linux perf, containers, and distro build farms are natural neighboring workflows.

Quellen

• https://github.com/ColinIanKing/stress-ng
• https://raw.githubusercontent.com/ColinIanKing/stress-ng/master/debian/changelog
• https://wiki.ubuntu.com/Kernel/Reference/stress-ng
• source_facts.package-manager