Attachment #243854 for bug #269602

View | Details | Raw Unified | Return to bug 269602 | Differences between
Collapse All | Expand All




PORTNAME=	stress-ng
DISTVERSIONPREFIX=	V
DISTVERSION=	0.16.02
PORTREVISION=	2
CATEGORIES=	benchmarks

MAINTAINER=	pizzamig@FreeBSD.org
COMMENT=	Stress test benchmarks
WWW=		https://github.com/ColinIanKing/stress-ng/

LICENSE=	GPLv2+
LICENSE_FILE=	${WRKSRC}/COPYING




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.
- 

Return to bug 269602

Lines 1-12 Link Here

(-)b/benchmarks/stress-ng/Makefile (-2 / +2 lines)
1	PORTNAME= stress-ng	1	PORTNAME= stress-ng
2	DISTVERSIONPREFIX= V	2	DISTVERSIONPREFIX= V
3	DISTVERSION= 0.16.02	3	DISTVERSION= 0.16.02
4	PORTREVISION= 1	4	PORTREVISION= 2
5	CATEGORIES= benchmarks	5	CATEGORIES= benchmarks
6		6
7	MAINTAINER= pizzamig@FreeBSD.org	7	MAINTAINER= pizzamig@FreeBSD.org
8	COMMENT= Stress test benchmarks	8	COMMENT= Stress test benchmarks
9	WWW= http://kernel.ubuntu.com/~cking/stress-ng/	9	WWW= https://github.com/ColinIanKing/stress-ng/
10		10
11	LICENSE= GPLv2+	11	LICENSE= GPLv2+
12	LICENSE_FILE= ${WRKSRC}/COPYING	12	LICENSE_FILE= ${WRKSRC}/COPYING

Lines 1-4 Link Here

(-)b/benchmarks/stress-ng/pkg-descr (-5 / +15 lines)
1	This stress test suite will stress a computer system in various	1	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:
2	selectable ways It was designed to exercise various physical	2
3	subsystems of a computer as well as various operating system kernel	3	300+ stress tests
4	interfaces.	4	80+ CPU specific stress tests that exercise floating point, integer, bit manipulation and control flow
		5	20+ virtual memory stress tests
		6	40+ file system stress tests
		7	30+ memory/CPU cache stress tests
		8	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.
		9	tested on alpha, armel, armhf, arm64, hppa, i386, m68k, mips32, mips64, power32, ppc64el, risc-v, sh4, s390x, sparc64, x86-64
		10
		11	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.
		12
		13	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.
		14
		15	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.
5	-