tool to load and stress a computer
stress-ng will stress test a computer system in various selectable ways. It was designed to exercise various physical subsystems of a computer as well as the various operating system kernel interfaces
stress-ng was originally intended to make a machine work hard and trip hardware issues such as thermal overruns as well as operating system bugs that only occur when a system is being thrashed hard. Use stress-ng with caution as some of the tests can make a system run hot on poorly designed hardware and also can cause excessive system thrashing which may be difficult to stop.
stress-ng can also measure test throughput rates; this can be useful to observe performance changes across different operating system releases or types of hardware. However, it has never been intended to be used as a precise benchmark test suite, so do NOT use it in this manner.
Running stress-ng with root privileges will adjust out of memory settings on Linux systems to make the stressors unkillable in low memory situations, so use this judiciously. With the appropriate privilege, stress-ng can allow the ionice class and ionice levels to be adjusted, again, this should be used with care.
View full history Series and milestones
trunk series is the current focus of development.
All code Code
- Version control system:
- Git
- Programming languages:
- C, assembler
All questions Latest questions
-
using --job
Posted
All packages Packages in Distributions
-
stress-ng source package in Xenial
Version 0.05.23-1ubuntu2 uploaded -
stress-ng source package in Sid
Version 0.18.07-1 uploaded -
stress-ng source package in Plucky
Version 0.18.07-1build1 uploaded -
stress-ng source package in Oracular
Version 0.18.04-1 uploaded -
stress-ng source package in Noble
Version 0.17.06-1build1 uploaded
All bugs Latest bugs reported
-
Bug #2082743: Memory Stress-ng Test Failing on a System with 881.46GB of RAM
Reported -
Bug #2069674: Stress Tests failed during Server Certification test
Reported -
Bug #2059167: stress-ng: fail: [1379606] vm: detected 1694364648734976 bit errors while stressing memory
Reported -
Bug #2028281: sockpair stress test hangs on a low-performance arm64 device
Reported -
Bug #2016966: flock stress test exits with code 7
Reported
More contributors Top contributors
- Michael Reed 40 points
- Colin Ian King 18 points
- Robby Pocase 9 points
- dann frazier 6 points
- Mitchell Dzurick 4 points