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 features:
300+ stress tests
80+ CPU specific stress tests that exercise floating point, integer, bit manipulation and control flow
20+ virtual memory stress tests
40+ file system stress tests
30+ memory/CPU cache stress tests
portable: builds on Linux (Debian, Devuan, RHEL, Fedora, Centos, Slackware OpenSUSE, Ubuntu, etc..), Solaris, FreeBSD, NetBSD, OpenBSD, DragonFlyBSD, Minix, Android, MacOS X, Serenity OS, GNU/Hurd, Haiku, Windows Subsystem for Linux and SunOs/Dilos/Solaris. with gcc, musl-gcc, clang, icc, icx, tcc and pcc.
tested on alpha, armel, armhf, arm64, hppa, i386, m68k, mips32, mips64, power32, ppc64el, risc-v, sh4, s390x, sparc64, x86-64
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.
===> The following configuration options are available for stress-ng-0.20.00:
GPU=off: Enable support for GPU stressor (add GL)
INTELIPSEC=on: Enable support for Intel's IPsec library
JUDY=on: Enable support for (lib)Judy
LIBINOTIFY=on: Enable support for libinotify
XXHASH=on: Enable support for libxxhash
===> Use 'make config' to modify these settings
benchmarks/stress-ng: disable crypt.h
In case it's detected, it causes a conflict with a struct
defined in unistd.h
PR: 275958
Reported by: John Hein <jcfyecrayz@liamekaens.com>
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
benchmarks/stress-ng: Bump PORTREVISION
Bump PORTVERSION due to version bump of security/intel-ipsec-mb
Commit: 5d2007b1ed1c42a8c28b7016f1d6cc6a4a608f79
benchmarks/stress-ng: several improvements and fixes
Enable on aarch64
Connect a few libs
Fix build on CURRENT
PR: 260893
Reported by: Daniel Engberg <diizzy@FreeBSD.org>
benchmarks/stress-ng: fix build on -CURRENT
The CPU_SET macros in -CURRENT have been made compatible with GLIBC.
A simple test for the new signature of CPU_AND, CPU_OR, ... is the
existence of a CPU_ALLOC macro.
Approved by: portmgr (implicit)
MFH: 2022Q1
benchmarks/stress-ng: fix build on CURRENT,
In CURRENT, the initial configuration detects now support for the
scheduler affinity, enabling the build of an additional stressor.
In this stressor, the CPU_OR macro has 3 arguments (Linux implementation),
while on FreeBSD it has only 2 arguments.
This patch provides the fix
No bumprevision is provided, because it's only fixing CURRENT where the
build was failing.
benchmarks/stress-ng: Update to 0.13.04
Changes available at:
https://github.com/ColinIanKing/stress-ng/blob/master/debian/changelog
While updating, import a fix for the man page kindly provided by 0mp
Co-authored-by: Mateusz Piotrowski <0mp@FreeBSD.org>
PR: PR258105
Reported by: Graham Perrin <grahamperrin@gmail.com>
benchmarks/stress-ng: add option to disable inotify support
The option LIBINOTIFY, on by default, can be used to not build inotify
stressor and install its dependency.
No portrevision bump needed, inotify support was already enable.
benchmarks/stress-ng: Add and fix libinotify support
stress-ng supports libinotify. A kevent based implementation can be used
to provide support, fixing a build issue reported in PR 252661
PR: 252661
Reported by: dewayne@heuristicsystems.com.au
Bump PORTREVISION for ports depending on the canonical version of GCC
as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3
to GCC 9.1 under most circumstances now after revision 507371.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.
PR: 238330
Bump PORTREVISION for ports depending on the canonical version of GCC
defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t
GCC 8.2 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, as a double check, everything INDEX-11 showed depending on lang/gcc7.
PR: 231590
Bump PORTREVISION for ports depending on the canonical version of GCC
in the ports tree (via Mk/bsd.default-versions.mk and lang/gcc) which
has now moved from GCC 6 to GCC 7 by default.
This includes ports
- featuring USE_GCC=yes or USE_GCC=any,
- featuring USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and those
- with USES=compiler specifying one of openmp, nestedfct, c11, c++0x,
c++11-lib, c++11-lang, c++14-lang, c++17-lang, or gcc-c++11-lib.
PR: 222542
benchmarks/stress-ng: Update to 0.09.35
While I'm upgrading, I fix the atomic 64 bit detection on clang6
The current solution is to for the noinline attribute to the
atomic detection code
PR: 229885
Number of commits found: 175 (showing only 100 on this page)
